[SOLVED] Remote Manager, Port 22 issue

[mfehr]

I set up my Zimbra 5.0.2 on Ubuntu 7.10 (as a VMware image). I have 2 domains which both are currently successfully working on my new Zimbra server.

Going through the admin console, however, I get some error messages when I select my server in the "Servers" tab. The same happens when I select the server in the "Certificates" tab. The error message shows as follows

Message: system failure: exception during auth {RemoteManager: mail.mymailserver.com->zimbra@mail.mymailserver.com:22} Error code: service.FAILURE Details:soap:Receiver

A similar error occures when selecting the "mail queues" tab with the following message:

Message: system failure: exception during auth {RemoteManager: fehr.is-a-chef.com->zimbra@fehr.is-a-chef.com:22} Error code: service.FAILURE Method: GetMailQueueInfoRequest Details:soap:Receiver

I found some reference to a Remote Queue Manager using port 22 but I did not find any reference in the admin manual to find out how to check, configure, etc. Also the log files I found did provide me with a hint either. Any hints on how I can solve this issue?

[phoenix]

Welcome to the forums.

You shouldn't need to configure anything other than to make sure the sshd daemon is running and listening on port 22, is it?

[mfehr]

Thanks for the swift response - The ssh server was the missing piece. Ubuntu 7.10 server does not setup sshd by default. I recommend to add sshd as an installation prerequisite to the quick start manual.

[PenguinWrangler]

I've got the same problem on my test 5.0.4 server, however I have sshd running already. The host OS is Centos5-x86_64.

This shows up in /var/log/secure, not sure if it's related or not:

Mar 28 17:19:05 calculon sshd[25384]: Received disconnect from 10.11.0.22: 11: Closed due to user request.

[phoenix]

Originally Posted by PenguinWrangler

I've got the same problem on my test 5.0.4 server, however I have sshd running already.

Disable SElinux and any firewall on this server. What error messages do you see in the Zimbra log files?

[PenguinWrangler]

SELinux is disabled, and there are no iptables rules.

From mailbox.log:

2008-03-31 17:03:26,998 INFO [btpool0-9] [name=XXX@XXXXX.com;ip=10.11.6.14;ua=ZimbraWebClien t - FF2.0 (Linux);] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: exception during auth {RemoteManager: calculon.corp.XXXXX.com->zimbra@calculon.corp.XXXXX.com:22}
ExceptionId:btpool0-9:1207008206998:f01e27d42c3e41c8
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.rmgmt.RemoteManager.getSession(Remot eManager.java:192)
at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteMa nager.java:126)
at com.zimbra.cert.GetCert.handle(GetCert.java:90)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:391)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:250)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:156)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:266)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: java.io.IOException: auth failed
at com.zimbra.cs.rmgmt.RemoteManager.getSession(Remot eManager.java:185)
... 32 more

Originally Posted by phoenix

Disable SElinux and any firewall on this server. What error messages do you see in the Zimbra log files?

[mmorse]

Assuming you're using the standard ssh port:
1. Check /etc/sshd_config and be sure it's set to 22
2. stop/start/restart sshd

/etc/init.d/ssh restart

3. su - zimbra
4. Be sure zimbra's ssh port is set to 22

zmprov ms server.domain.com zimbraRemoteManagementPort 22

5. Generate new ssh keys

cd /opt/zimbra/bin/
./zmsshkeygen

6. Deploy the keys

./zmupdateauthkeys

To test this, you can run the following command:

ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@server.domain.com -p 22

-Shouldn't prompt you for a password at this point...then check the admin console mail queues area/servers/certificates.
If you continue to get that error please see this doc for some more ideas Mail Queue Monitoring - Zimbra :: Wiki

[PenguinWrangler]

Okay that's working a lot better now. Thanks.

[Atrispro]

I had this problem as well after upgrading from 5.04 to 5.05 on RHEL 5.1 x86-64. This resolved my problem.

[OneLoveAmaru]

Thanks, I created the new keys and pushed them out like you explained. I am running Debian Etch, seems I had to log out as zimbra and then back in, in order for me to be able to ssh in with your command. If I run all your stuff, then do the ssh, it asks for a password. Logged out and back in, ran it, let me in. Thanks guys!