Results 1 to 3 of 3

Thread: ldap died

  1. #1
    Join Date
    Mar 2007
    Location
    Small village in the center of Italy
    Posts
    350
    Rep Power
    10

    Default ldap died

    Centos 4.6 with zcs NE 5.0.11
    suddenly and without any reason today ldap has died:
    Code:
    2008-12-17 18:17:49,044 WARN  [ImapServer-50181] [name=xxxxx@xxx.it;mid=13;ip=192.168.100.148;] imap - error checking account status; dropping connection
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:ImapServer-50181:1229534269043:e24bf7f153ae7690
    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.LdapProvisioning.getAccountByQuery(LdapProvisioning.java:457)
            at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountById(LdapProvisioning.java:489)
            at com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:513)
            at com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:502)
            at com.zimbra.cs.imap.ImapCredentials.getAccount(ImapCredentials.java:89)
            at com.zimbra.cs.imap.ImapHandler.checkAccountStatus(ImapHandler.java:215)
            at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:118)
            at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
            at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.naming.CommunicationException: mailz.fbs.it:389 [Root exception is java.net.ConnectException: Connection refused]
            at com.sun.jndi.ldap.Connection.<init>(Connection.java:194)
            at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
            at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578)
            at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596)
            at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
            at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
            at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
            at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
            at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
            at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
            at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
            at javax.naming.InitialContext.init(InitialContext.java:223)
            at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
            at com.zimbra.cs.account.ldap.ZimbraLdapContext.<init>(ZimbraLdapContext.java:290)
    it was enough to zmcontrol stop/start to resuscitate it.
    Last edited by maumar; 12-17-2008 at 08:05 PM.

  2. #2
    Join Date
    Dec 2007
    Location
    Ypsilanti, MI
    Posts
    145
    Rep Power
    9

    Default

    That stacktrace just says that mailboxd was having trouble because ldap was down, which you knew. Check out /var/log/zimbra.log for more info on why ldap really died.

  3. #3
    Join Date
    Mar 2007
    Location
    Small village in the center of Italy
    Posts
    350
    Rep Power
    10

    Default

    you are right, but sadly i set no ldap verbosity at all, in fact:
    Code:
    Dec 17 18:16:49 mailz postfix/smtpd[9926]: NOQUEUE: reject: RCPT from unknown[190.252.232.44]: 554 5.7.1 Service unavailable; Client host [190.252.232.44] blocked using cbl.abuseat
    .org; Blocked - see http://cbl.abuseat.org/lookup.cgi?ip=190.252.232.44; from=<biand@diplomatie.gouv.fr> to=<xxxx@xxx.it> proto=ESMTP helo=<[190.252.232.44]>
    Dec 17 18:16:50 mailz postfix/smtpd[9926]: lost connection after DATA from unknown[190.252.232.44]
    Dec 17 18:16:50 mailz postfix/smtpd[9926]: disconnect from unknown[190.252.232.44]
    Dec 17 18:16:54 mailz sshd(pam_unix)[11751]: session opened for user root by (uid=0)
    Dec 17 18:17:02 mailz sshd(pam_unix)[11751]: session closed for user root
    Dec 17 18:17:15 mailz postfix/smtpd[9396]: timeout after DATA from cp-out11.libero.it[212.52.84.111]
    Dec 17 18:17:15 mailz postfix/smtpd[9396]: disconnect from cp-out11.libero.it[212.52.84.111]
    Dec 17 18:17:26 mailz slapd[16754]: connection_read(34): no connection!
    Dec 17 18:17:41 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping Global system configuration update.
    Dec 17 18:17:41 mailz zimbramon[23561]: 23561:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException mailz.f
    bs.it:389)
    Dec 17 18:17:45 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping All Reverse Proxy URLs update.
    Dec 17 18:17:45 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.Com
    municationException mailz.fbs.it:389)
    Dec 17 18:17:48 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping All Reverse Proxy Backends update.
    Dec 17 18:17:48 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming
    .CommunicationException mailz.fbs.it:389)
    Dec 17 18:17:51 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping All Memcached Servers update.
    Dec 17 18:17:51 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.Com
    municationException mailz.fbs.it:389)
    Dec 17 18:17:54 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update.
    Dec 17 18:17:54 mailz zimbramon[23561]: 23561:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.Communic
    ationException mailz.fbs.it:389)
    not more than: Dec 17 18:17:26 mailz slapd[16754]: connection_read(34): no connection!

    without raising ldap log verbosity i fear nothing can be said
    isn't it?

    m

Similar Threads

  1. LDAP Cannot bind on migration to new server
    By neekster in forum Migration
    Replies: 23
    Last Post: 03-09-2009, 02:08 AM
  2. upgrading from 5.0.4 to 5.0.5 opensource
    By smoke in forum Installation
    Replies: 4
    Last Post: 10-19-2008, 10:38 AM
  3. Replies: 8
    Last Post: 08-07-2008, 05:18 AM
  4. 3 testing: LDAP: 389 Failed when restore zimbra
    By victorLeong in forum Administrators
    Replies: 15
    Last Post: 05-24-2007, 06:45 AM
  5. Replies: 4
    Last Post: 11-15-2006, 11:16 AM

Posting Permissions

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