Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Sometimes ???remote.CONNECT_FAILURE???

  1. #1
    Join Date
    Feb 2009
    Location
    Germany
    Posts
    32
    Rep Power
    6

    Default Sometimes ???remote.CONNECT_FAILURE???

    Hello Zimbra Team,

    sometimes i get the Error "???remote.CONNECT_FAILURE???".
    After restarting Zimbra everything is fine .. on a random of time, the Error show's again.
    What is ToDo ?
    If there some WikiEntry to Debug this situation ?


    Thanks a lot
    René

    ( sorry for my bad english for german runaways ) )

  2. #2
    Join Date
    Feb 2009
    Location
    Germany
    Posts
    32
    Rep Power
    6

    Default new info

    after installing new ZD 2.0 ... between the new syncronisation, the server get some times the error ???remote.CONNECT_FAILURE???, after restart the Services work's fine again.

    If there a Problem with LDAP ..
    I think it crash's on heavy load ...


    Greets
    René

  3. #3
    Join Date
    Feb 2009
    Location
    Lecco, Italy
    Posts
    554
    Rep Power
    7

    Default

    I'm having the same issue on a 6.0.8.
    When under heavy load, ldap crashes.
    Sometimes it's enough to make ldap stop & ldap start, sometimes not...
    YetOpen S.r.l. ~ Your open source partner
    Lecco (LC) - ITALY
    http://www.yetopen.it

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

    Default

    Quote Originally Posted by maxxer View Post
    I'm having the same issue on a 6.0.8.
    When under heavy load, ldap crashes.
    Sometimes it's enough to make ldap stop & ldap start, sometimes not...
    Define 'heavy load' and what are your server specifications? Do you have any logs for the failure of LDAP?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    Join Date
    Feb 2009
    Location
    Germany
    Posts
    32
    Rep Power
    6

    Default

    where can i find the ldap log ?

    'heavy load' is the initial sync of 2,2GB with a new installaed ZD 2.0 client.
    it can be many connections to ldap, i dont know the architectur of Zimbra .. sorry :-/

    Quote Originally Posted by phoenix View Post
    Define 'heavy load' and what are your server specifications? Do you have any logs for the failure of LDAP?

  6. #6
    Join Date
    Feb 2009
    Location
    Lecco, Italy
    Posts
    554
    Rep Power
    7

    Default

    Quote Originally Posted by MyLive View Post
    where can i find the ldap log ?
    /opt/zimbra/log/mailbox.log

    Quote Originally Posted by MyLive View Post
    'heavy load' is the initial sync of 2,2GB with a new installaed ZD 2.0 client.
    it can be many connections to ldap, i dont know the architectur of Zimbra .. sorry :-/
    yes, almost the same.
    I must say that I'm experiencing this issue on a system with not very fast storage...
    so I can get load up to 10, and sometimes LDAP drops
    YetOpen S.r.l. ~ Your open source partner
    Lecco (LC) - ITALY
    http://www.yetopen.it

  7. #7
    Join Date
    Feb 2009
    Location
    Germany
    Posts
    32
    Rep Power
    6

    Unhappy Error message

    This is the Error Message.
    The LDAP Server run´s and works .. i have test it.
    MySQL also run and Work ..

    What´s the next ?



    Fehler bei der Kommunikation mit dem Server. Bitte versuchen Sie es später erneut.

    Debugging-Nachricht: system failure: ZimbraLdapContext

    Ausnahme:

    com.zimbra.common.soap.SoapFaultException: system failure: ZimbraLdapContext
    ExceptionId:com.zimbra.common.service.ServiceExcep tion: system failure: ZimbraLdapContext
    ExceptionId:btpool0-23://mail.box.ug/service/soap/WaitSetRequest:1287769555248:0415f80b11d079ee
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(Zimb raLdapContext.java:416)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(Zimb raLdapContext.java:373)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getAcc ountByQuery(LdapProvisioning.java:608)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getAcc ountById(LdapProvisioning.java:640)
    at com.zimbra.cs.account.ldap.LdapProvisioning.get(Ld apProvisioning.java:664)
    at com.zimbra.cs.account.ldap.LdapProvisioning.get(Ld apProvisioning.java:653)
    at com.zimbra.cs.account.Provisioning.get(Provisionin g.java:692)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:368)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:274)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
    at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
    at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.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(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:399)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:413)
    at org.mortbay.jetty.nio.SelectChannelConnector$Retry Continuation.run(SelectChannelConnector.java:525)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(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(LdapCt x.java:3213)
    at javax.naming.ldap.InitialLdapContext.extendedOpera tion(InitialLdapContext.java:164)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(Zimb raLdapContext.java:406)
    ... 39 more
    Caused by: java.net.SocketException: Bad file descriptor
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
    at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
    ... 41 more

    Code:service.FAILURE
    at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88)
    at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:303)
    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:262)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:253)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:162)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:356)
    at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:342)
    at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMa ilbox.java:660)
    at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMa ilbox.java:622)
    at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMa ilbox.java:617)
    at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMa ilbox.java:610)
    at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMa ilbox.java:606)
    at com.zimbra.cs.mailbox.OfflinePoller.waitsetRequest (OfflinePoller.java:120)
    at com.zimbra.cs.mailbox.OfflinePoller.runPoll(Offlin ePoller.java:72)
    at com.zimbra.cs.mailbox.OfflinePoller.run(OfflinePol ler.java:64)
    at java.lang.Thread.run(Unknown Source)

    Wenn das Problem weiterhin besteht, melden Sie eine Fehlerbeschreibung und Debugging-Informationen bitte hier.

  8. #8
    Join Date
    Feb 2009
    Location
    Germany
    Posts
    32
    Rep Power
    6

    Default Log File Entrie

    2010-10-27 09:32:38,711 INFO [btpool0-9://localhost:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:btpool0-9://localhost:7071/service/admin/soap/GetDomainInfoRequest:1288164758711:fbc175237b38df8 d
    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:366)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getDom ainByQuery(LdapProvisioning.java:1829)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getDom ainByVirtualHostnameInternal(LdapProvisioning.java :1945)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getDom ain(LdapProvisioning.java:1869)
    at com.zimbra.cs.account.ldap.LdapProvisioning.get(Ld apProvisioning.java:1855)
    at com.zimbra.cs.service.admin.GetDomainInfo.handle(G etDomainInfo.java:45)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:420)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:274)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
    at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
    at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.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(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
    at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:413)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(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(LdapCt x.java:3213)
    at javax.naming.ldap.InitialLdapContext.extendedOpera tion(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(SocketOutp utStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
    at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
    ... 43 more
    2010-10-27 09:32:40,098 INFO [btpool0-9://mail.box.ug/service/soap/WaitSetRequest] [name=xxxxxx@yyyyyy.zzz;mid=44;ip=1.2.3.4;ua=Zimbra Desktop/2.0_10580_Windows;] so
    2010-10-27 09:32:41,101 INFO [btpool0-7://mail.box.ug/service/soap/WaitSetRequest] [name=xxxxxx@yyyy.zzz;mid=44;ip=1.2.3.4;ua=Zimbra Desktop/2.0_10580_Windows;] so
    2010-10-27 09:32:41,319 INFO [btpool0-16://localhost/service/soap/AuthRequest] [oip=80.145.62.105;ua=zclient/6.0.8_GA_2678;] soap - AuthRequest
    2010-10-27 09:32:41,320 INFO [btpool0-16://localhost/service/soap/AuthRequest] [oip=80.145.62.105;ua=zclient/6.0.8_GA_2678;] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext

  9. #9
    Join Date
    Feb 2009
    Location
    Lecco, Italy
    Posts
    554
    Rep Power
    7

    Default

    rising ulimits solved here...
    YetOpen S.r.l. ~ Your open source partner
    Lecco (LC) - ITALY
    http://www.yetopen.it

  10. #10
    Join Date
    Feb 2009
    Location
    Germany
    Posts
    32
    Rep Power
    6

    Question

    Thanks, but where can i see that's this the solution ?

    experience?

    regards
    René

    Quote Originally Posted by maxxer View Post
    rising ulimits solved here...

Posting Permissions

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