Hello,

Having encoutered some problems with our iscsi storage, zimbra has been running without its partition for the mailstore.

Now that it's restored, I have restarted zimbra and it seemed OK, but it does'nt last long before it stops working.

Symptoms :
  • when I do "/etc/init.d/zimbra stop", it halts on "Stopping imapproxy" :
Code:
]# /etc/init.d/zimbra stop
Host azimbra.paris.iufm.fr
        Stopping mta...Done
        Stopping spell...Done
        Stopping snmp...Done
        Stopping antivirus...Done
        Stopping antispam...Done
        Stopping imapproxy...
I have to kill the processes by hand to end all this.
  • su - zimbra -c "zmcontrol status" doesn't return anything. It's blocked.
  • remaining processes look like :
Code:
zimbra   12657 12642  0 01:24 ?        00:00:00 sh -c /opt/zimbra/bin/zmprov -l gs azimbra.paris.iufm.fr 2>/dev/null
zimbra   12658 12657  0 01:24 ?        00:00:01 /opt/zimbra/java/bin/java -client -Xmx256m -Dzimbra.home=/opt/zimbra -Djava.library.path=/opt/zimbra/lib -Djav
zimbra   12678 12677  0 01:26 ?        00:00:00 /usr/bin/perl /opt/zimbra/libexec/zmstatuslog
zimbra   12687 12678  0 01:26 ?        00:00:00 /usr/bin/perl /opt/zimbra/bin/zmcontrol status
zimbra   12700 12687  0 01:26 ?        00:00:00 sh -c /opt/zimbra/bin/zmprov -l gs azimbra.paris.iufm.fr 2>/dev/null
zimbra   12701 12700  0 01:26 ?        00:00:01 /opt/zimbra/java/bin/java -client -Xmx256m -Dzimbra.home=/opt/zimbra -Djava.library.path=/opt/zimbra/lib -Djav
zimbra   12717 12716  0 01:28 ?        00:00:00 /usr/bin/perl /opt/zimbra/libexec/zmstatuslog
zimbra   12741 12717  0 01:28 ?        00:00:00 /usr/bin/perl /opt/zimbra/bin/zmcontrol status
zimbra   12755 12741  0 01:28 ?        00:00:00 sh -c /opt/zimbra/bin/zmprov -l gs azimbra.paris.iufm.fr 2>/dev/null
zimbra   12756 12755  0 01:28 ?        00:00:01 /opt/zimbra/java/bin/java -client -Xmx256m -Dzimbra.home=/opt/zimbra -Djava.library.path=/opt/zimbra/lib -Djav
zimbra   12799 12796  0 01:30 ?        00:00:00 /usr/bin/perl /opt/zimbra/libexec/zmstatuslog
zimbra   12837 12799  0 01:30 ?        00:00:00 /usr/bin/perl /opt/zimbra/bin/zmcontrol status
Here are some random logs :

# tail -200f /var/log/zimbra.log|more
Nov 4 10:36:29 azimbra postfix/master[8001]: warning: /opt/zimbra/postfix-2.2.9/libexec/trivial-rewrite: bad command startup -- throttling
Nov 4 10:36:35 azimbra postfix/smtpd[9209]: warning: timeout on private/rewrite socket while reading input attribute name
Nov 4 10:36:35 azimbra postfix/smtpd[9209]: warning: problem talking to service rewrite: Connection timed out
Nov 4 10:36:58 azimbra postfix/trivial-rewrite[13884]: warning: dict_ldap_lookup: Search error -5: Timed out
Nov 4 10:37:28 azimbra postfix/trivial-rewrite[13884]: warning: dict_ldap_lookup: Search error -5: Timed out
Nov 4 10:37:34 azimbra postfix/smtpd[9201]: warning: timeout on private/rewrite socket while reading input attribute name
Nov 4 10:37:34 azimbra postfix/smtpd[9201]: warning: problem talking to service rewrite: Connection timed out
Nov 4 10:37:58 azimbra postfix/trivial-rewrite[13884]: warning: dict_ldap_lookup: Search error -5: Timed out
Nov 4 10:37:58 azimbra postfix/trivial-rewrite[13884]: fatal: ldap:/opt/zimbra/conf/ldap-vad.cf(0,100): table lookup problem
Nov 4 10:37:59 azimbra postfix/master[8001]: warning: process /opt/zimbra/postfix-2.2.9/libexec/trivial-rewrite pid 13884 exit status 1
Nov 4 10:37:59 azimbra postfix/master[8001]: warning: /opt/zimbra/postfix-2.2.9/libexec/trivial-rewrite: bad command startup -- throttling
Nov 4 10:37:59 azimbra postfix/trivial-rewrite[13888]: warning: dict_ldap_lookup: Search error -5: Timed out
Nov 4 10:38:06 azimbra postfix/smtpd[9203]: warning: timeout on private/rewrite socket while reading input attribute name
Nov 4 10:38:06 azimbra postfix/smtpd[9203]: warning: problem talking to service rewrite: Connection timed out




# tail -2000f /opt/zimbra/log/mailbox.log|more
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:162)
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: 30000ms
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:192)
... 27 more
2007-11-04 10:28:19,061 INFO [http-443-Processor62] [ua=ZimbraWebClient - FF1.5 (Win)/undefined;ip=81.51.240.166;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: getDirectContext
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:175)
at com.zimbra.cs.account.ldap.LdapUtil.getDirContext( LdapUtil.java:197)
at com.zimbra.cs.account.ldap.LdapUtil.getDirContext( LdapUtil.java:181)
at com.zimbra.cs.account.ldap.LdapProvisioning.getDom ainByQuery(LdapProvisioning.java:1273)
at com.zimbra.cs.account.ldap.LdapProvisioning.getDom ainByVirtualHostname(LdapProvisioning.java:1347)
at com.zimbra.cs.account.ldap.LdapProvisioning.get(Ld apProvisioning.java:1301)
at com.zimbra.cs.service.account.Auth.handle(Auth.jav a:103)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:270)


I'm not sure but I think it could be a ldap related problem.
Do you know how I could gather more informations about that to resolve my problem ?

Thanks in advance,