View Single Post
  #1 (permalink)  
Old 10-21-2009, 08:16 AM
samesisa samesisa is offline
Active Member
 
Posts: 26
Default [SOLVED] What does it mean this Warn!

Hi,

Recently we have temporary mistake. We can't login on Zimbra's server. Our clients insert the correct username and password and Zimbra ask this fields again. I found this warn in /opt/zimbra/log/mailbox.log while this error happens.

Code:
2009-10-21 14:56:39,843 INFO  [MailboxPurge] [name=itt038@domain.com;mid=160;] purge - Purging messages.
2009-10-21 14:56:39,908 WARN  [MailboxPurge] [name=itt038@domain.com;mid=160;] purge - Unable to purge mailbox 160
com.zimbra.common.service.ServiceException: system failure: getDirectContext
ExceptionId:MailboxPurge:1256129799908:c305594497400103
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
        at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:253)
        at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:238)
        at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrsInternal(LdapProvisioning.java:279)
        at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:263)
        at com.zimbra.cs.account.ldap.LdapProvisioning.modifyAttrs(LdapProvisioning.java:244)
        at com.zimbra.cs.account.Provisioning.modifyAttrs(Provisioning.java:1543)
        at com.zimbra.cs.mailbox.PurgeThread.saveLastPurgedId(PurgeThread.java:204)
        at com.zimbra.cs.mailbox.PurgeThread.run(PurgeThread.java:135)
Caused by: javax.naming.CommunicationException: my.domain.com:389 [Root exception is java.net.ConnectException: Connection refused]
        at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
        at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
        at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
        at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2616)
        at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
        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:288)
        at javax.naming.InitialContext.init(InitialContext.java:223)
        at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
        at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:246)
        ... 7 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(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.jndi.ldap.Connection.createSocket(Connection.java:336)
        at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
        ... 20 more


Previously had another problem. When we can try to log-in see this message: "A network service error has occurred"
I did not found any error into the logfiles. After reboot service, with zmcontrol command, it worked fine. But the mistake repeats itself from time to time. And found this warn/info messages on mailbox.log:
2009-10-08 11:01:19,429 INFO [btpool0-40] [ua=zclient/5.0.5_GA_2201.SLES10_64;oip=80.36.225.46;] SoapEngine - handler exception
2009-10-08 10:24:29,700 WARN [btpool0-59] [] soap - Unable to look up zimbraSoapRequestMaxSize. Not limiting the request size.

I read this thread
4.5.°_RC1 --> A network service error has occurred (zclient/io).

For solve this i increased the "-Xmx" JVM option value on /opt/zimbra/bin/zmmailboxdctl to 4096 MB. The original value of mailboxd_java_heap_memory_percen was 40%. Now is 68'5%. We have 6 GB RAM on our server. (Zimbra recommend against increasing the heap size to more than 30% of system memory).

These errors can be connected?

We have -> Release 5.0.5_GA_2201.SLES10_64_20080417011732 SLES10_64 FOSS edition

Thanks for your help.

Last edited by samesisa; 10-29-2009 at 09:15 AM..
Reply With Quote