Results 1 to 10 of 10

Thread: ???remote.CONNECT_FAILURE???

  1. #1
    holger is offline Beginner Member
    Join Date
    Sep 2010
    Posts
    1
    Rep Power
    4

    Default ???remote.CONNECT_FAILURE???

    Hi there,

    yesterday I installed Zimbra FOSS in its latest version on a Ubuntu 10.04 server.

    It's the third time this day that I try to login via webinterface (as a normal user) and get the message: ???remote.CONNECT_FAILURE???

    Because I'm not so familiar with the Zimbra-Ecosystem yet, I restart Zimbra via "/etc/init.d/zimbra" restart or "zmcontrol restart" everytime the error occurs. After that everything works fine, until the next "crash".

    I'm not sure, which logmessage I should post here, so maybe this message from mailbox.log helps a little bit:

    Code:
    2010-09-29 22:20:04,245 INFO  [btpool0-10://localhost:7071/service/admin/soap/AuthRequest] [name=zimbra;ip=127.0.0.1;] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:btpool0-10://localhost:7071/service/admin/soap/AuthRequest:1285791604243:4fe5599f46658a9e
    Code:service.FAILURE
    	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
    	at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:416)
    	at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:373)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.reload(LdapProvisioning.java:374)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.checkAccountStatus(LdapProvisioning.java:3304)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.authAccount(LdapProvisioning.java:3433)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.authAccount(LdapProvisioning.java:3415)
    	at com.zimbra.cs.service.admin.Auth.handle(Auth.java:145)
    	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
    	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
    	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
    	at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
    	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:155)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:326)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:413)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
    	at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3213)
    	at javax.naming.ldap.InitialLdapContext.extendedOperation(InitialLdapContext.java:164)
    	at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:406)
    	... 41 more
    Caused by: java.net.SocketException: Bad file descriptor
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
    	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
    	at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:396)
    	at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1172)
    	at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3160)
    	... 43 more
    Please let me know, if I can give you further informations from other logfiles.

    Thanks for your help,
    Holger

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,492
    Rep Power
    56

    Default

    The likelihood is you have a configuration issue, if you're behinf a NAT router then you should have a valid /etc/hosts file (check the Quick Start Configuration Guide for details) and a Split DNS set-up - do you have both of those set correctly? Go to to the article in the wiki for Split DNS and set it up (f you don't have it already) then go to the 'Verify ...' section of that article and post the output of the commands here for verification.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    pge's Avatar
    pge
    pge is offline Intermediate Member
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    16
    Rep Power
    8

    Default

    Im experiencing the same error.

    (Soap Exceptions on 6.0.8_GA_2661.UBUNTU10_64)

    Although im not in need of a NAT Setup.

  4. #4
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,492
    Rep Power
    56

    Default

    Quote Originally Posted by pge View Post
    Im experiencing the same error.

    (Soap Exceptions on 6.0.8_GA_2661.UBUNTU10_64)

    Although im not in need of a NAT Setup.
    Then for confirmation you should post the information I asked for in my previous post, the details required are in the 'Verify...' section of the Split DNS article.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    pge's Avatar
    pge
    pge is offline Intermediate Member
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    16
    Rep Power
    8

    Default

    I've sent the info via PM.

  6. #6
    imx
    imx is offline Special Member
    Join Date
    Jun 2009
    Posts
    131
    Rep Power
    6

    Default

    Im seeing this as well, Zimbra FOSS on 10.04, it works for the majority of the time - note ive already fixed the ulimit problems previously seen. Im not using NAT, or split DNS, jus a standard set up.

    A config problem would for me happen more often, unless im hitting some other kind of limit, but please note this does not happen when the server is at its busiest.

  7. #7
    maxxer's Avatar
    maxxer is offline Trained Alumni
    Join Date
    Feb 2009
    Location
    Lecco, Italy
    Posts
    552
    Rep Power
    7

    Default

    could be this:
    Bug 51328 &ndash; LDAP connection leak
    seems it's included in a "to-be-released" patch
    YetOpen S.r.l. ~ Your open source partner
    Lecco (LC) - ITALY
    http://www.yetopen.it

  8. #8
    imx
    imx is offline Special Member
    Join Date
    Jun 2009
    Posts
    131
    Rep Power
    6

    Default

    This is what my mailbox.log sees during:


    2010-10-18 18:14:30,876 INFO [btpool0-183://e.mail.net/] [] HttpMethodDirector - I/O exception (java.net.SocketException) caught when processing request: Socket closed
    2010-10-18 18:14:30,876 INFO [btpool0-183://e.mail.net/] [] HttpMethodDirector - Retrying request
    2010-10-18 18:14:30,879 INFO [btpool0-183://e.mail.net/] [] HttpMethodDirector - I/O exception (java.net.SocketException) caught when processing request: Socket closed
    2010-10-18 18:14:30,879 INFO [btpool0-183://e.mail.net/] [] HttpMethodDirector - Retrying request

  9. #9
    imx
    imx is offline Special Member
    Join Date
    Jun 2009
    Posts
    131
    Rep Power
    6

    Default

    Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]


    @holger, i have a different issue to you - apologies for hijacking this thread. Youre suffering from the ulimit issue, your fix is here:

    zimbra 6.0.8 FOSS - Ubuntu 10.04 LTS - LDAP errors

  10. #10
    pge's Avatar
    pge
    pge is offline Intermediate Member
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    16
    Rep Power
    8

    Default

    Affirmative. The raise of roots ulimit fixed the problems for me also.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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