New Queue Monitoring Feature
New Queue Monitoring Feature
Hello All
I upgraded from V3.0 and the new feature in Admin panel that enable to monitor the mail queues doesn't work. It gives me following error. Any ideas? Does this have any relation from the fact that I moved SSH port 22 daemon from 22 to 81?
Message: system failure: exception during auth {RemoteManager: zimbra.test.com->zimbra@zimbra.test.com:22}
com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: zimbra.test.com->zimbra@zimbra.test.com:22}
at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:131)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:192)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteManager.java:129)
at com.zimbra.cs.service.admin.GetMailQueueInfo.handle(GetMailQueueInfo.java:55)
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)
Caused by: java.io.IOException: There was a problem while talking to zimbra.test.com:22
at ch.ethz.ssh2.Connection.connect(Connection.java:642)
at ch.ethz.ssh2.Connection.connect(Connection.java:460)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:183)
... 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(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at ch.ethz.ssh2.transport.TransportManager.initialize(TransportManager.java:299)
at ch.ethz.ssh2.Connection.connect(Connection.java:591)
... 26 more
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Cheers
I upgraded from V3.0 and the new feature in Admin panel that enable to monitor the mail queues doesn't work. It gives me following error. Any ideas? Does this have any relation from the fact that I moved SSH port 22 daemon from 22 to 81?
Message: system failure: exception during auth {RemoteManager: zimbra.test.com->zimbra@zimbra.test.com:22}
com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: zimbra.test.com->zimbra@zimbra.test.com:22}
at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:131)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:192)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteManager.java:129)
at com.zimbra.cs.service.admin.GetMailQueueInfo.handle(GetMailQueueInfo.java:55)
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)
Caused by: java.io.IOException: There was a problem while talking to zimbra.test.com:22
at ch.ethz.ssh2.Connection.connect(Connection.java:642)
at ch.ethz.ssh2.Connection.connect(Connection.java:460)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:183)
... 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(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at ch.ethz.ssh2.transport.TransportManager.initialize(TransportManager.java:299)
at ch.ethz.ssh2.Connection.connect(Connection.java:591)
... 26 more
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
Cheers
New Queue Monitoring Feature
[quote user="kibo"]Does this have any relation from the fact that I moved SSH port 22 daemon from 22 to 81?[/QUOTE]
Yes, it does.
Is there any reason you've changed the SSH port? Can you change it back to 22 and try the admin panel again to confirm that's the problem?
Yes, it does.
Is there any reason you've changed the SSH port? Can you change it back to 22 and try the admin panel again to confirm that's the problem?
New Queue Monitoring Feature
Yes Bill. I changed it back it works OK now. I usually change SSHD port to secure myself from usuall dictionary attacks which put unneccessary load on system and generate huge log files!
New Queue Monitoring Feature
Just a quick note that I changed the RemoteManagementPort attribute in "zmprov gas -v" to 81 and now it works OK even on 81.
New Queue Monitoring Feature
[quote user="kibo"]Just a quick note that I changed the RemoteManagementPort attribute in "zmprov gas -v" to 81 and now it works OK even on 81.[/QUOTE]
Ah, I was coming to that. Just out of interest, how did you change the port first time or was it just SSH that you'd changed?
Ah, I was coming to that. Just out of interest, how did you change the port first time or was it just SSH that you'd changed?
-
- Posts: 9
- Joined: Fri Sep 12, 2014 10:03 pm
New Queue Monitoring Feature
I changed my ssh port to 2222. I dont want to change it back based on the fact that I run multiple ssh servers and combine their remote use with a dynamic ip and a nat lan that requires port forwarding.
How exactly does the zmprov gas -v command work -- how do I use it to specify zimbraRemoteManagmentPort ?
How exactly does the zmprov gas -v command work -- how do I use it to specify zimbraRemoteManagmentPort ?
New Queue Monitoring Feature
zmprov gas -v just outputs all the info for all the servers
you want something like this:
zmprov ms REPLACE-WITH-YOUR-ZIMBRA-SERVERNAME RemoteManagementPort 2222
you want something like this:
zmprov ms REPLACE-WITH-YOUR-ZIMBRA-SERVERNAME RemoteManagementPort 2222
-
- Posts: 9
- Joined: Fri Sep 12, 2014 10:03 pm
New Queue Monitoring Feature
I changed ssh port to 22 by editing /etc/ssh/sshd_config
I checked that the zimbraRemoteManagementPort was 22
I logged onto the admin panel and went to mail queue ---> same error.
I put ssh on 2222 (what I originally had)
I changed the zimbraRemoteManagementPort to 2222
I restarted the machine
I logged ontto the admin panel and went to mail queue --> same error with :2222 in errors instead of :22
Any idea why I keep getting this? From the above it seems that its not a factor of my ssh or zimbraRemoteManagementPort
Message: system failure: exception during auth {RemoteManager: efs24.dnsalias.org->zimbra@efs24.dnsalias.org:2222}
com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: efs24.dnsalias.org->zimbra@efs24.dnsalias.org:2222}
at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:131)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:192)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteManager.java:129)
at com.zimbra.cs.service.admin.GetMailQueueInfo.handle(GetMailQueueInfo.java:55)
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)
Caused by: java.io.IOException: auth failed
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:185)
... 24 more
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
I checked that the zimbraRemoteManagementPort was 22
I logged onto the admin panel and went to mail queue ---> same error.
I put ssh on 2222 (what I originally had)
I changed the zimbraRemoteManagementPort to 2222
I restarted the machine
I logged ontto the admin panel and went to mail queue --> same error with :2222 in errors instead of :22
Any idea why I keep getting this? From the above it seems that its not a factor of my ssh or zimbraRemoteManagementPort
Message: system failure: exception during auth {RemoteManager: efs24.dnsalias.org->zimbra@efs24.dnsalias.org:2222}
com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: efs24.dnsalias.org->zimbra@efs24.dnsalias.org:2222}
at com.zimbra.cs.service.ServiceException.FAILURE(ServiceException.java:131)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:192)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteManager.java:129)
at com.zimbra.cs.service.admin.GetMailQueueInfo.handle(GetMailQueueInfo.java:55)
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)
Caused by: java.io.IOException: auth failed
at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:185)
... 24 more
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver
New Queue Monitoring Feature
try resetting the ssh auth data:
zmsshkeygen
zmupdateauthkeys
tomcat restart
zmsshkeygen
zmupdateauthkeys
tomcat restart
New Queue Monitoring Feature
You may have to look into editing the /etc/ssh/ssh_config file.