I get the following after upgrading to 3.1 from 3.0 when I try to view the mail queues. I have searched the forums and found similar issues, but not exactly the same. I have tried resetting the ssh auth data as suggested in another thread to no avail. Also, I can open the zimbra_identity file in nano and read it just fine, so I'm not sure why its saying it is 'not readable'.
Message: system failure: server zimbra.********.com zimbraRemoteManagementPrivateKeyPath (/opt/zimbra/.ssh/zimbra_identity) is not readable
com.zimbra.cs.service.ServiceException: system failure: server zimbra.*******.com zimbraRemoteManagementPrivateKeyPath (/opt/zimbra/.ssh/zimbra_identity) is not readable
at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:131)
at com.zimbra.cs.rmgmt.RemoteManager.(RemoteManager.java:79)
at com.zimbra.cs.rmgmt.RemoteManager.getRemoteManager(RemoteManager.java:197)
at com.zimbra.cs.service.admin.GetMailQueueInfo.handle(GetMailQueueInfo.java:54)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:255)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:163)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:228)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(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.invoke(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Another mail queue manager issue
Another mail queue manager issue
Boy I feel stupid. As soon as I posted that, I thought to check the permissions on zimbra_identity. Only root had access to it.
Its been a long week.
Its been a long week.