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

Thread: Creating email error and server crash

  1. #1
    Join Date
    Nov 2005
    Posts
    96
    Rep Power
    9

    Default Creating email error and server crash

    Hi,

    I am using network edition 3.1.1.

    I have a server daemons restarted like 3 times since launch last friday. This is because I am getting a system failure error and users cannot login.

    The first time I don't know what happened. The second and third time is due to creating an email, clicking onto the to: button and trying to search names that are found in the global address list and trying to put them in the bcc. I managed to add 25 users before it hung. I added one by one thru searching and not doing a group select. Imagine the pain!

    I am using external authentication and I thought it will be the cause but thought that it will not since i created all the users and they reside in the local ldap server. I have a dual 3.2Ghz Xeon with 4GB RAM and lots of storage.

    THe error is as follows:-
    --------------------------------------------------------------------
    SoapEngine - handler exception
    com.zimbra.cs.service.ServiceException: system failure: getDirectContext
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:131)
    at com.zimbra.cs.account.ldap.LdapUtil.getDirContext( LdapUtil.java:179)
    at com.zimbra.cs.account.ldap.LdapEntry.modifyAttrsIn ternal(LdapEntry.java:159)
    at com.zimbra.cs.account.ldap.LdapEntry.modifyAttrs(L dapEntry.java:137)
    at com.zimbra.cs.service.account.ModifyPrefs.handle(M odifyPrefs.java:69)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:255)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:228)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:154)
    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: javax.naming.CommunicationException: Timeout exceeded while waiting for a connection: 10000ms
    at com.sun.jndi.ldap.pool.Connections.get(Connections .java:128)
    at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:129)
    at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:259 6)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(Ldap CtxFactory.java:193)
    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:136)
    at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext (LdapCtxFactory.java:66)
    at javax.naming.spi.NamingManager.getInitialContext(N amingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(Init ialContext.java:247)
    at javax.naming.InitialContext.init(InitialContext.ja va:223)
    at javax.naming.ldap.InitialLdapContext.<init>(Initia lLdapContext.java:134)
    at com.zimbra.cs.account.ldap.LdapUtil.getDirContext( LdapUtil.java:174)

    ----------------------------------------------------------------

    Any reason why? Thanks.

    adrian

  2. #2
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    "Timeout exceeded while waiting for a connection: 10000ms "

    Seems like your external LDAP is timing out. Any load issues on that server?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  3. #3
    Join Date
    Nov 2005
    Posts
    96
    Rep Power
    9

    Default

    From the looks of it, no. It is a web server as well. The slapd did not break at any time since its last reboot.

    At the top, the memory usage is fine. Do you think a dedicated ldap server will help? Is there any settings of the slapd that I must set? I have most at defaults.

    adrian

  4. #4
    Join Date
    Nov 2005
    Posts
    96
    Rep Power
    9

    Default

    Hi,

    Wait a minute. It cannot be the external ldap that is causing the problem. The reason was that I was searching thru the global address list. And the global address list gets the list from the local ldap. I only have an EXTERNAL AUTHENTICATION server. The zimbra ldap is local.

    The server got problems when I was doing a GAL search which should not involved the external authentication server.

    What do you think?

  5. #5
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Ahh ok so ext auth only. Interesting that your seeing this timeout connecting to the local Zimbra LDAP. Seem memory usage is ok, what about CPU usage still ok?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  6. #6
    Join Date
    Nov 2005
    Posts
    96
    Rep Power
    9

    Default

    hi,

    Any hints to check that?

    adrian

  7. #7
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    top command is a good start.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  8. #8
    Join Date
    Nov 2005
    Posts
    96
    Rep Power
    9

    Default

    top - 09:25:39 up 6 days, 16:32, 1 user, load average: 0.17, 0.32, 0.32
    Tasks: 147 total, 1 running, 146 sleeping, 0 stopped, 0 zombie
    Cpu(s): 20.8% us, 2.2% sy, 0.0% ni, 76.9% id, 0.0% wa, 0.0% hi, 0.0% si
    Mem: 4086484k total, 3581836k used, 504648k free, 86700k buffers
    Swap: 2031608k total, 160k used, 2031448k free, 778060k cached

    --------------------------------------------------------------------

    Is the above ok?

  9. #9
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    yes looks fine.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  10. #10
    Join Date
    Nov 2005
    Posts
    96
    Rep Power
    9

    Default

    Hi,

    If that is so, is there any other reason why search a local GAL is crashing my zimbra?

    I have reported it but no response so far......

    adrian

Posting Permissions

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