Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 01-15-2009, 12:52 AM
Active Member
 
Posts: 29
Default Zimbra stopped working - something to do with ldap?

After running for a long time with no problems my installation stopped.
The exception seems to boil down to: Root exception is java.net.ConnectException: Connection refused

What failed to connect to what and how can I stop this from happening again?

Below is the error.

Thanks in advance,


009-01-13 20:44:28,703 WARN [btpool0-10] [] log - Nested in javax.servlet.ServletException: com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-10:1231879468703:ac0814b0c7c2e632
Code:service.FAILURE:
com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-10:1231879468703:ac0814b0c7c2e632
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init >(ZimbraLdapContext.java:304)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init >(ZimbraLdapContext.java:275)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init >(ZimbraLdapContext.java:268)
at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByName(LdapProvisioning.java:2234)
at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByName(LdapProvisioning.java:2223)
at com.zimbra.cs.account.ldap.LdapProvisioning.getLoc alServer(LdapProvisioning.java:2607)
at com.zimbra.cs.servlet.ZimbraServlet.isAdminRequest (ZimbraServlet.java:337)
at com.zimbra.cs.service.UserServlet.getAccount(UserS ervlet.java:249)
at com.zimbra.cs.service.UserServlet.checkAuthenticat ion(UserServlet.java:372)
at com.zimbra.cs.service.UserServlet.doGet(UserServle t.java:326)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:707)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:188)
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:148)
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.rewrite.RewriteHandler.h andle(RewriteHandler.java:350)
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.he aderComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
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: javax.naming.CommunicationException: hvlmail.com:389 [Root exception is java.net.ConnectException: Connection refused]
at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:194)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1578)
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.ZimbraLdapContext.<init >(ZimbraLdapContext.java:290)
... 35 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:520)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:333)
at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:181)
... 48 more
Reply With Quote
  #2 (permalink)  
Old 01-15-2009, 09:37 AM
Partner (VAR/HSP)
 
Posts: 425
Default

Disk space? DNS set up correctly and pointing to your server?
Reply With Quote
  #3 (permalink)  
Old 02-17-2010, 06:42 PM
Starter Member
 
Posts: 2
Default

Geoff, did you ever figure out the cause of this? The LDAP component on our Zimbra server just died a few minutes ago and we've got basically the exact same error message in our mailbox.log file.

David
Reply With Quote
  #4 (permalink)  
Old 02-17-2010, 11:29 PM
Active Member
 
Posts: 29
Default

David - It was a problem with the dns server of our hosting company
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.