Monitoring statistics and mail queues not working

[superboer12]

After some installations problems I got zimbra up and running.
Zimbra is really great!!

Only two things doesn't work (yet), 'server statistics' and 'mail queues' of the administration console.

When I go to the statistics I see the page with four broken image logos instead of the graph.

When I go to mail queues I get a popup with this error:

Message: system failure: exception during auth {RemoteManager: netserver.roma.dc->zimbra@netserver.roma.dc:22}
com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: netserver.roma.dc->zimbra@netserver.roma.dc:22}
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(Remot eManager.java:197)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteMa nager.java:134)
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: auth failed
at com.zimbra.cs.rmgmt.RemoteManager.getSession(Remot eManager.java:190)
... 24 more

Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver

This error also appears in zimbra.log.
This is also the only error that I can discover in zimbra.log.
'zmcontrol status' returns that all services are running.

Reading the first row of it made me think zimbra wants to connect with the zimbra user by ssh. This wasn't allowed by my sshd_config so I added 'zimbra' to the 'AllowUsers' line and restarted sshd after that. Unfortunately this didn't help.

Any ideas what goes wrong?

ps,
running zimbra 4.05 on debian
if additional info and/or log files are needed I will post it.

[phoenix]

Have you got the sshd daemon running? If not start it, if it is running have you changed the port? If you've changed the port then search the forums for details of a fix.

[superboer12]

Yes it's running on the default port number.
SSH is on this moment the only way to access my Zimbra server so I can say ssh is working fine.

[superboer12]

okay I just found something.
tailing /var/log/auth.log gave me the following error:

Jan 10 16:40:59 netserver sshd[31795]: Authentication refused: bad ownership or modes for file /opt/zimbra/.ssh/authorized_keys

The file was owned by an invalid uid and gid, so I chowned it to zimbra.zimbra.
Now auth.log doesn't show the error anymore, but it's still not working (same error message)

[phoenix]

Any firewall or selinux likely to be causing these problems?

[superboer12]

SElinux isn't installed on the server and disabling the firewall doesn't solve it.

[brian]

Originally Posted by superboer12

okay I just found something.
tailing /var/log/auth.log gave me the following error:

The file was owned by an invalid uid and gid, so I chowned it to zimbra.zimbra.
Now auth.log doesn't show the error anymore, but it's still not working (same error message)

make sure you mode is 600 as well.
chmod 600 /opt/zimbra/.ssh/authorized_keys

[superboer12]

Just did the chmod, but unfortunately no effect.

[jholder]

Try regenerating the ssh keys.

It's in the wiki.

[superboer12]

Tried it but didn't work.
I edited sshd_config and uncommended
"AuthorizedKeysFile %h/.ssh/authorized_key"

Shouldn't be needed (due to the -i in the ssh command used) but it did the trick

Thanks for the help!