Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Administrators
Reload this Page [SOLVED] What does it mean this Warn!

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
Page 1 of 3 1 23
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 10-21-2009, 08:16 AM
Intermediate Member
  
Posts: 19
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
  #2 (permalink)  
Old 10-21-2009, 03:53 PM
Moderator
  
Posts: 778
Default
The error that you have posted above is saying that it can't connect to the LDAP server. What is the output of `zmcontrol status`?
Reply With Quote
  #3 (permalink)  
Old 10-22-2009, 12:57 AM
Intermediate Member
  
Posts: 19
Default
All services was running, It is one of the first things that looks. I forget to tell previosly.

This is a trace of http client when the first error succeed ("A network service error has occurred")

Code:
 <!-- com.zimbra.common.soap.SoapFaultException: system failure: getDirectContext
ExceptionId:btpool0-29:1255085575095:14cec69e5fdd0327
Code:service.FAILURE
	at com.zimbra.common.soap.SoapJSProtocol.soapFault(SoapJSProtocol.java:65)
	at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:245)
	at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:221)
	at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:251)
	at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:297)
	at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:543)
	at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:537)
	at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMailbox.java:482)
	at com.zimbra.cs.zclient.ZMailbox.&lt;init&gt;(ZMailbox.java:393)
	at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox.java:342)
	at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.java:122)
	at org.apache.jsp.public_.login_jsp._jspService(login_jsp.java:259)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:477)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:371)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at com.zimbra.webClient.servlet.JspServlet.service(JspServlet.java:50)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:268)
	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
	at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:465)
	at org.mortbay.jetty.servlet.DefaultServlet.doPost(DefaultServlet.java:496)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
	at com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:283)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(HandlerWrapper.java:139)
	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:315)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
	at org.mortbay.jetty.Server.handle(Server.java:313)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
 -->
It's a fail of soap server?? jetty?
If i update Zimbra, i will solve both mistakes?
Thanks ArcaneMagus
Last edited by samesisa : 10-22-2009 at 01:23 AM.
Reply With Quote
  #4 (permalink)  
Old 10-22-2009, 05:40 AM
Moderator
  
Posts: 701
Default
Did the error start to happen unprompted or was a change made that may have lead to it?
Reply With Quote
  #5 (permalink)  
Old 10-22-2009, 11:42 AM
Moderator
  
Posts: 778
Default
What is the output of the following commands?
Code:
ps -ef | grep slapd
lsof -i :389
cat /etc/hosts
zmhostname
Reply With Quote
  #6 (permalink)  
Old 10-23-2009, 04:58 AM
Intermediate Member
  
Posts: 19
Default
ArcaneMagus

ps -ef | grep slapd
Code:
mail:~ # ps -ef | grep slapd
zimbra    7609     1  0 02:11 ?        00:00:19 /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://mydomain:389 -f /opt/zimbra/conf/slapd.conf
root     22964 22638  0 12:46 pts/0    00:00:00 grep slapd
lsof -i :389
Code:
mail:~ # lsof -i :389
COMMAND     PID    USER   FD   TYPE   DEVICE SIZE NODE NAME
amavisd    4521  zimbra   11u  IPv4 18761442       TCP mydomain:6260->mydomain:ldap (ESTABLISHED)
cleanup    6545 postfix   14u  IPv4 18758817       TCP mydomain:10376->mydomain:ldap (ESTABLISHED)
smtpd      6634 postfix   22u  IPv4 18759200       TCP mydomain:10398->mydomain:ldap (ESTABLISHED)
slapd      7609  zimbra    7u  IPv4 18000789       TCP mydomain:ldap (LISTEN)
slapd      7609  zimbra   12u  IPv4 18782753       TCP mydomain:ldap->mydomain:7207 (ESTABLISHED)
slapd      7609  zimbra   14u  IPv4 18720441       TCP mydomain:ldap->mydomain:dj-ice (ESTABLISHED)
slapd      7609  zimbra   17u  IPv4 18719497       TCP mydomain:ldap->mydomain:5386 (ESTABLISHED)
slapd      7609  zimbra   18u  IPv4 18683853       TCP mydomain:ldap->mydomain:10809 (ESTABLISHED)
slapd      7609  zimbra   21u  IPv4 18535482       TCP mydomain:ldap->mydomain:27154 (ESTABLISHED)
slapd      7609  zimbra   24u  IPv4 18785237       TCP mydomain:ldap->mydomain:13251 (ESTABLISHED)
slapd      7609  zimbra   25u  IPv4 18692809       TCP mydomain:ldap->mydomain:28433 (ESTABLISHED)
slapd      7609  zimbra   26u  IPv4 18785504       TCP mydomain:ldap->mydomain:13268 (ESTABLISHED)
slapd      7609  zimbra   27u  IPv4 18792191       TCP mydomain:ldap->mydomain:28985 (ESTABLISHED)
slapd      7609  zimbra   28u  IPv4 18774413       TCP mydomain:ldap->mydomain:23046 (ESTABLISHED)
slapd      7609  zimbra   30u  IPv4 18609663       TCP mydomain:ldap->mydomain:12307 (ESTABLISHED)
slapd      7609  zimbra   31u  IPv4 18794937       TCP mydomain:ldap->mydomain:ms-sql-s (ESTABLISHED)
slapd      7609  zimbra   33u  IPv4 18761414       TCP mydomain:ldap->mydomain:6258 (ESTABLISHED)
slapd      7609  zimbra   34u  IPv4 18770206       TCP mydomain:ldap->mydomain:28611 (ESTABLISHED)
slapd      7609  zimbra   35u  IPv4 18708430       TCP mydomain:ldap->mydomain:12025 (ESTABLISHED)
slapd      7609  zimbra   36u  IPv4 18688889       TCP mydomain:ldap->mydomain:cgi-starapi (ESTABLISHED)
slapd      7609  zimbra   38u  IPv4 18758818       TCP mydomain:ldap->mydomain:10376 (ESTABLISHED)
slapd      7609  zimbra   39u  IPv4 18759201       TCP mydomain:ldap->mydomain:10398 (ESTABLISHED)
slapd      7609  zimbra   40u  IPv4 18525499       TCP mydomain:ldap->mydomain:10136 (ESTABLISHED)
slapd      7609  zimbra   41u  IPv4 18761343       TCP mydomain:ldap->mydomain:6257 (ESTABLISHED)
slapd      7609  zimbra   42u  IPv4 18675618       TCP mydomain:ldap->mydomain:24532 (ESTABLISHED)
slapd      7609  zimbra   46u  IPv4 18761443       TCP mydomain:ldap->mydomain:6260 (ESTABLISHED)
slapd      7609  zimbra   47u  IPv4 18794939       TCP mydomain:ldap->mydomain:ms-sql-m (ESTABLISHED)
smtpd      8126 postfix   22u  IPv4 18761342       TCP mydomain:6257->mydomain:ldap (ESTABLISHED)
smtpd      8411 postfix   22u  IPv4 18761413       TCP mydomain:6258->mydomain:ldap (ESTABLISHED)
amavisd    9162  zimbra   11u  IPv4 18708429       TCP mydomain:12025->mydomain:ldap (ESTABLISHED)
java       9557  zimbra  166u  IPv6 18535481       TCP mydomain:27154->mydomain:ldap (ESTABLISHED)
java       9557  zimbra  204u  IPv6 18525498       TCP mydomain:10136->mydomain:ldap (ESTABLISHED)
cleanup   11947 postfix   14u  IPv4 18770205       TCP mydomain:28611->mydomain:ldap (ESTABLISHED)
cleanup   13523 postfix   14u  IPv4 18774412       TCP mydomain:23046->mydomain:ldap (ESTABLISHED)
amavisd   14491  zimbra   11u  IPv4 18785236       TCP mydomain:13251->mydomain:ldap (ESTABLISHED)
amavisd   15100  zimbra   11u  IPv4 18719496       TCP mydomain:5386->mydomain:ldap (ESTABLISHED)
amavisd   16499  zimbra   11u  IPv4 18785503       TCP mydomain:13268->mydomain:ldap (ESTABLISHED)
amavisd   17246  zimbra   11u  IPv4 18782752       TCP mydomain:7207->mydomain:ldap (ESTABLISHED)
trivial-r 18963 postfix    8u  IPv4 18720440       TCP mydomain:dj-ice->mydomain:ldap (ESTABLISHED)
amavisd   20570  zimbra   11u  IPv4 18609662       TCP mydomain:12307->mydomain:ldap (ESTABLISHED)
amavisd   21120  zimbra   11u  IPv4 18792190       TCP mydomain:28985->mydomain:ldap (ESTABLISHED)
smtpd     22573 postfix   21u  IPv4 18675617       TCP mydomain:24532->mydomain:ldap (ESTABLISHED)
java      23475  zimbra   56u  IPv6 18794936       TCP mydomain:ms-sql-s->mydomain:ldap (ESTABLISHED)
java      23475  zimbra   58u  IPv6 18794938       TCP mydomain:ms-sql-m->mydomain:ldap (ESTABLISHED)
amavisd   26247  zimbra   11u  IPv4 18683852       TCP mydomain:10809->mydomain:ldap (ESTABLISHED)
amavisd   30800  zimbra   11u  IPv4 18688888       TCP mydomain:cgi-starapi->mydomain:ldap (ESTABLISHED)
smtpd     32467 postfix   19u  IPv4 18692808       TCP mydomain:28433->mydomain:ldap (ESTABLISHED)
cat /etc/hosts
Code:
mail:~ # cat /etc/hosts
127.0.0.1       localhost.Mydomain localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
@IP.Public.v4    mail.Mydomain
@IP.Private.v4  mail.Mydomain mail
zmhostname
Code:
zimbra@mail:/root> zmhostname
mail.Mydomain


DIRK

I have one change, we change the IP Public of Zimbra server. Only IP, the hostname is the same. But i found this log on my gateway.


Code:
Oct 23 12:41:12 gateway kernel: martian source isp-gateway from my-gateway, on dev eth1
Oct 23 12:41:12 gateway kernel: ll header: ff:ff:ff:ff:ff:ff:00:50:56:7f:5a:4d:08:06
For every 20 minuts the msnservice break down, downloads crashes and connections outside of our lan fails when this succes.

Maybe i have bad configuration on our gateway.
Last edited by samesisa : 10-23-2009 at 05:04 AM.
Reply With Quote
  #7 (permalink)  
Old 10-23-2009, 05:57 AM
Zimbra Consultant & Moderator
  
Posts: 11,518
Default
Your hosts file is incorrect, it should contain only the following:
Code:
127.0.0.1       localhost.localdomain localhost
192.168.x.x  mail.yourdomain.com mail
__________________
Regards


Bill
Reply With Quote
  #8 (permalink)  
Old 10-23-2009, 06:03 AM
Intermediate Member
  
Posts: 19
Default
Ok I change it, but why the public address can be present in hosts file?

Thanks,
Reply With Quote
  #9 (permalink)  
Old 10-23-2009, 06:18 AM
Zimbra Consultant & Moderator
  
Posts: 11,518
Default
Quote:
Originally Posted by samesisa View Post
Ok I change it, but why the public address can be present in hosts file?
It should not be there because you're behind A NAT router, it's the private LAN IP that you use not the public IP.
__________________
Regards


Bill
Reply With Quote
  #10 (permalink)  
Old 10-23-2009, 06:32 AM
Intermediate Member
  
Posts: 19
Default
The server have two interfaces. One of them is private for users working in our office and the other is for the rest of employees that are working out of the office.

For the Zimbra server we do not have a Nat router. We have one transparent router (Encapsulation: RFC 1483)
Reply With Quote
Reply
Page 1 of 3 1 23

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

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

Zimbrablog.com


Home - Blog - Contact Us - Archive - Top


 

Search Engine Optimization by vBSEO 3.1.0