Results 1 to 2 of 2

Thread: A network service error has occurred

Hybrid View

  1. #1
    Join Date
    Jul 2008
    Posts
    26
    Rep Power
    7

    Exclamation A network service error has occurred

    Hi,

    Recently i change the public ip of our mail server (Release 5.0.5_GA_2201.SLES10_64_20080417011732 SLES10_64 FOSS edition). I changed the ip of nameservers that this server uses too.

    Some times, when i try to login i got following error
    :
    A network service error has occurred.
    In the top of the login screen. 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.

    I read this thread

    http://www.zimbra.com/forums/install...client-io.html

    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.


    Where i can get the correct zimbra.soap.url ??
    I should increase the Heap Space?? How i can do this?? Editing zmmailboxdctl??


    #
    # Memory for use by JVM
    #
    memkb=$(zmsysmemkb)
    jm=`expr $memkb '*' ${mailboxd_java_heap_memory_percent} / 100 / 1024`


    PD: I found this with zmlocalconfig command

    zimbra_zmprov_default_soap_server = localhost

    How i can try to test localhost/service/soap, for example

    We have the same error, some hours later. I see this WARN in mailbox.log while the network services crash down:


    2009-10-08 15:54:33,470 WARN [MailboxPurge] [name=sit062@gruposame.com;mid=171;] purge - Unable to purge mailbox 171
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1255010073470:0052860034c d3b7c
    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.modify AttrsInternal(LdapProvisioning.java:279)
    at com.zimbra.cs.account.ldap.LdapProvisioning.modify Attrs(LdapProvisioning.java:263)
    at com.zimbra.cs.account.ldap.LdapProvisioning.modify Attrs(LdapProvisioning.java:244)
    at com.zimbra.cs.account.Provisioning.modifyAttrs(Pro visioning.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: mail.gruposame.com:389 [Root exception is java.net.ConnectException: Connection refused]
    at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:197)
    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1580)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:261 6)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
    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:288)
    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: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(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:519)
    at sun.reflect.GeneratedMethodAccessor10.invoke(Unkno wn Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:336)
    at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:184)
    ... 20 more
    [hr]

    I increase the -Xmx JVM option value on /opt/zimbra/bin/zmmailboxdctl to 4096 MB. The default of mailboxd_java_heap_memory_percen value was 40&#37;. 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.

    Performance Tuning Guidelines for Large Deployments - Zimbra :: Wiki

    I read this errors from firefox during error:
    <!-- com.zimbra.common.soap.SoapFaultException: system failure: getDirectContext
    ExceptionId:btpool0-29:1255085575095:14cec69e5fdd0327
    Code:service.FAILURE
    at com.zimbra.common.soap.SoapJSProtocol.soapFault(So apJSProtocol.java:65)
    at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:245)
    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:221)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:251)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:297)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:543)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:537)
    at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMai lbox.java:482)
    at com.zimbra.cs.zclient.ZMailbox.&lt;init&gt;(ZMailb ox.java:393)
    at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox .java:342)
    at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.j ava:122)
    at org.apache.jsp.public_.login_jsp._jspService(login _jsp.java:259)
    at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:93)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:373)
    at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:477)
    at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:371)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:50)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:362)
    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.servlet.Dispatcher.forward(Dispa tcher.java:268)
    at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:126)
    at org.mortbay.jetty.servlet.DefaultServlet.doGet(Def aultServlet.java:465)
    at org.mortbay.jetty.servlet.DefaultServlet.doPost(De faultServlet.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(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
    at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:283)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
    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:315)
    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.co ntent(HttpConnection.java:844)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
    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)
    -->
    Last edited by samesisa; 10-09-2009 at 04:44 AM. Reason: new information

  2. #2
    Join Date
    Jul 2008
    Posts
    26
    Rep Power
    7

    Unhappy more.....

    I increase the -Xmx JVM option value on /opt/zimbra/bin/zmmailboxdctl to 4096 MB. The default of mailboxd_java_heap_memory_percen value 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.

    Performance Tuning Guidelines for Large Deployments - Zimbra :: Wiki

    I read this errors from firefox during error:
    <!-- com.zimbra.common.soap.SoapFaultException: system failure: getDirectContext
    ExceptionId:btpool0-29:1255085575095:14cec69e5fdd0327
    Code:service.FAILURE
    at com.zimbra.common.soap.SoapJSProtocol.soapFault(So apJSProtocol.java:65)
    at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:245)
    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:221)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:251)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:297)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:543)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:537)
    at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMai lbox.java:482)
    at com.zimbra.cs.zclient.ZMailbox.&lt;init&gt;(ZMailb ox.java:393)
    at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox .java:342)
    at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.j ava:122)
    at org.apache.jsp.public_.login_jsp._jspService(login _jsp.java:259)
    at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:93)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:373)
    at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:477)
    at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:371)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:50)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:362)
    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.servlet.Dispatcher.forward(Dispa tcher.java:268)
    at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:126)
    at org.mortbay.jetty.servlet.DefaultServlet.doGet(Def aultServlet.java:465)
    at org.mortbay.jetty.servlet.DefaultServlet.doPost(De faultServlet.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(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
    at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:283)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
    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:315)
    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.co ntent(HttpConnection.java:844)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
    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)
    -->

Similar Threads

  1. Replies: 14
    Last Post: 09-26-2011, 11:50 PM
  2. A network service error has occurred (zclient/io).
    By kersfeeshaas in forum Administrators
    Replies: 1
    Last Post: 03-18-2009, 09:24 AM
  3. A network service error has occurred (zclient/io)
    By djcovey in forum Installation
    Replies: 4
    Last Post: 10-17-2008, 12:50 AM
  4. Replies: 17
    Last Post: 04-19-2008, 09:27 AM
  5. A network service error has occurred
    By bjared in forum Administrators
    Replies: 4
    Last Post: 10-12-2006, 11:12 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
  •