Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-06-2006, 12:30 PM
Special Member
 
Posts: 100
Unhappy Post-Installation woes

-Messages between zimbra users are sent but never appear
(imap message import did work however)
-Zimbra says antivirus and spam are ofline
(prob due to the fact that this machines domain does not resolve in dns to this machine, it can't of course becuase there is a production server )
-I can manually smtp a message to a user, with no aparent errors, but it is never delivered
-Veiwing mail queues does not work (see stack trace below)

Quote:
Message: system failure: exception during auth {RemoteManager: badger->zimbra@badger:22}
com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: badger->zimbra@badger:22}
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(Remot eManager.java:195)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteMa nager.java:132)
at com.zimbra.cs.service.admin.GetMailQueueInfo.handl e(GetMailQueueInfo.java:56)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:261)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:173)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: There was a problem while talking to badger:22
at ch.ethz.ssh2.Connection.connect(Connection.java:64 2)
at ch.ethz.ssh2.Connection.connect(Connection.java:46 0)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(Remot eManager.java:186)
... 24 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:516)
at ch.ethz.ssh2.transport.TransportManager.initialize (TransportManager.java:299)
at ch.ethz.ssh2.Connection.connect(Connection.java:59 1)
... 26 more

Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Reply With Quote
  #2 (permalink)  
Old 10-06-2006, 12:40 PM
Former Zimbran
 
Posts: 5,606
Default

Quote:
Originally Posted by 3RiversTechAdmin
-Messages between zimbra users are sent but never appear
(imap message import did work however)
-Zimbra says antivirus and spam are ofline
(prob due to the fact that this machines domain does not resolve in dns to this machine, it can't of course becuase there is a production server )
-I can manually smtp a message to a user, with no aparent errors, but it is never delivered
-Veiwing mail queues does not work (see stack trace below)
Hi-
Let's see if I can help out a little.
If your machine isn't resolveable via DNS, you're going to have a lot of problems, as most of the services bind via dns and your hosts file.

When you manually send a message, what do your logs indicate? (var/log/zimbra.log & /opt/zimbra/log/zimbra.log)

Also, it looks like either you've turned off SSH on that machine, or changed the port? Is this right?

john
Reply With Quote
  #3 (permalink)  
Old 10-06-2006, 01:20 PM
Special Member
 
Posts: 100
Red face :)

Thanks for your prompt response , here is where I am at:

Quote:
If your machine isn't resolveable via DNS, you're going to have a lot of problems, as most of the services bind via dns and your hosts file.
I have made changes to the host file so the real mail server's hostname should now resolve to local host and I have "zmprov mcf zimbraMtaDnsLookupsEnabled FALSE"

Quote:
When you manually send a message, what do your logs indicate? (var/log/zimbra.log & /opt/zimbra/log/zimbra.log)
/var/log/zimbra.log states:

Quote:
Oct 6 14:40:11 localhost postfix/qmgr[20391]: 7840E6BCBA: from=, size=348, nrcpt=1 (queue active)
Oct 6 14:40:11 localhost postfix/smtp[26183]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
Oct 6 14:40:11 localhost postfix/smtp[26183]: 7840E6BCBA: to=, relay=none, delay=31, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
Oct 6 14:40:22 localhost postfix/smtpd[22511]: disconnect from localhost[127.0.0.1]
Oct 6 14:41:23 localhost zmtomcatmgr[27113]: threaddump requested
Oct 6 14:41:23 localhost zmtomcatmgr[20208]: sending SIQUIT to tomcat/JVM process 20209
Oct 6 14:41:25 localhost zmtomcatmgr[27148]: stop requested
Oct 6 14:41:25 localhost zmtomcatmgr[27148]: waiting for manager process 20208 to die
Oct 6 14:41:25 localhost zmtomcatmgr[20208]: shutdown requested, sending TERM signal to 20209
Oct 6 14:41:28 localhost zmtomcatmgr[20208]: tomcat/JVM process exited (waitpid expected 20209 got 20209)
Oct 6 14:41:28 localhost zmtomcatmgr[20208]: manager woke up from wait on tomcat/JVM with pid 20209
Oct 6 14:41:29 localhost zmtomcatmgr[27148]: manager process 20208 died, shutdown completed
Oct 6 14:41:52 localhost zmtomcatmgr[27634]: status requested
Oct 6 14:41:52 localhost zmtomcatmgr[27634]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Oct 6 14:41:52 localhost zmtomcatmgr[27634]: assuming no other instance is running
Oct 6 14:41:52 localhost zmtomcatmgr[27634]: no manager process is running
Oct 6 14:41:52 localhost zmtomcatmgr[27643]: start requested
Oct 6 14:41:52 localhost zmtomcatmgr[27643]: checking if another instance of manager is already running
Oct 6 14:41:52 localhost zmtomcatmgr[27643]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Oct 6 14:41:52 localhost zmtomcatmgr[27643]: assuming no other instance is running
Oct 6 14:41:52 localhost zmtomcatmgr[27644]: wrote manager pid 27644 to /opt/zimbra/log/zmtomcatmgr.pid
Oct 6 14:41:52 localhost zmtomcatmgr[27644]: manager started tomcat/JVM with pid 27645
Oct 6 14:42:05 localhost zmtomcatmgr[28024]: status requested
Oct 6 14:42:05 localhost zmtomcatmgr[28024]: status OK
Quote:
Also, it looks like either you've turned off SSH on that machine, or changed the port? Is this right?
Yikes, I just realized the new distribution I am using does not install the server portion of open ssh by default. I guess I assumed it was working becuase I could run "zmupdateauthkeys" etc. I can indeed view the mail queue now, it shows all messages and defered due to local host refusing them. This seems to consolidate what the log is saying. What would you recommend I do? Thanks
Reply With Quote
  #4 (permalink)  
Old 10-09-2006, 11:13 AM
Special Member
 
Posts: 100
Thumbs up fixed

it turns out that besides the changes made in my last post, adding the FQDN to the AV, spam and postfix config files (rather than just the host name), fixed the rest of the issues. Now I just have to figure out why zimbra rejects messages sent to it from the old (send)mail server (using .forward files) for the users who will be evaluating zimbra.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.