Results 1 to 4 of 4

Thread: Mail queues cannot be viewed from ZimbraAdmin when SSH is not bound to port 22?

  1. #1
    Join Date
    Jun 2006
    Posts
    22
    Rep Power
    9

    Default Mail queues cannot be viewed from ZimbraAdmin when SSH is not bound to port 22?

    Ever since we switched our SSH port from the default port 22, I have not been able to view our mail queue stats in Zimbra Admin. Error message is:

    Message: system failure: exception during auth {RemoteManager: lespaul.imocha.com.my->zimbra@lespaul.imocha.com.my:22}
    com.zimbra.cs.service.ServiceException: system failure: exception during auth {RemoteManager: lespaul.imocha.com.my->zimbra@lespaul.imocha.com.my: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: There was a problem while talking to lespaul.imocha.com.my: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:188)
    ... 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

    We decided to move the SSH port due to the number of scans we were experiencing on port 22. Not that moving it to an alternative port makes it any more secure, but it was getting kinda irritating viewing all those attempts on logwatch.

    Is there any way of solving this?

    Thanks!

  2. #2
    Join Date
    Nov 2005
    Location
    London, ON
    Posts
    255
    Rep Power
    9

    Default

    You need to change a value in LDAP:

    zmprov mcf zimbraRemoteManagementPort 'NewPortNumber'

  3. #3
    Join Date
    Jun 2006
    Posts
    22
    Rep Power
    9

    Default

    Quote Originally Posted by rsharpe
    You need to change a value in LDAP:

    zmprov mcf zimbraRemoteManagementPort 'NewPortNumber'
    Thank you!

    May I also know if this change would be preserved after a zimbra restart or would I need to run it again after each restart?

  4. #4
    Join Date
    Oct 2005
    Location
    Madrid - Spain
    Posts
    59
    Rep Power
    9

    Red face

    >> May I also know if this change would be preserved after a zimbra restart or would I need to run it again after each restart?


    Yes, it is preserved after zimbra restart, but it isn't at zimbra Upgrade.
    - dgamez -

    Netnovation Vzla, S.A.
    Zimbra VAR

    Caracas - Venezuela

Similar Threads

  1. Problems with port 25
    By yogiman in forum Installation
    Replies: 57
    Last Post: 06-13-2011, 01:55 PM
  2. Replies: 7
    Last Post: 02-03-2011, 06:01 AM
  3. fresh install down may be due to tomcat
    By gon in forum Installation
    Replies: 10
    Last Post: 07-25-2007, 08:09 AM
  4. DynDNS and Zimbra
    By afterwego in forum Installation
    Replies: 30
    Last Post: 04-01-2007, 03:34 PM
  5. receiveing mail
    By maybethistime in forum Administrators
    Replies: 15
    Last Post: 12-09-2005, 03:55 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •