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

[v912485]

I get the same error as woeper, but unfortunately neither a reboot nor clearing the cache helps. I also run the 4.5 RC1 but on CentOS.
On the advanced client I get the message (INVALID_PDU) and on the basic client I get "A network service error has occurred (zclient/io)".
The source of the advanced client does not show a stacktrace but the basic on does:

com.zimbra.cs.zclient.ZClientException: invoke Connection refused
	at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZClientException.java:54)
	at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:269)
	at com.zimbra.cs.zclient.ZMailbox.auth(ZMailbox.java:244)
	at com.zimbra.cs.zclient.ZMailbox.<init>(ZMailbox.java:198)
	at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox.java:183)
	at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.java:73)
	at org.apache.jsp.h.login._jspx_meth_zm_login_0(org.apache.jsp.h.login:666)
	at org.apache.jsp.h.login._jspx_meth_c_catch_0(org.apache.jsp.h.login:631)
	at org.apache.jsp.h.login._jspService(org.apache.jsp.h.login:129)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
	at com.zimbra.webClient.filters.CharEncodingFilter.doFilter(CharEncodingFilter.java:21)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
	at com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:323)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
	at org.apache.catalina.core.StandardContextValve.invoke(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.invoke(StandardEngineValve.java:107)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
	at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
	at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
	at java.lang.Thread.run(Thread.java:595)
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:516)
	at java.net.Socket.connect(Socket.java:466)
	at java.net.Socket.<init>(Socket.java:366)
	at java.net.Socket.<init>(Socket.java:239)
	at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:79)
	at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:121)
	at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
	at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
	at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
	at com.zimbra.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:192)
	at com.zimbra.soap.SoapTransport.invoke(SoapTransport.java:231)
	at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:265)
	... 34 more

The logs on the server don't show any sign of errors and zimbra.soap.url seems to be contain the correct url.

Any suggestions would be much appreciated,
Allan

[schemers]

Did you read the part about updating this file?

/opt/zimbra/tomcat/webapps/zimbra/WEB-INF/web.xml

You need to change the value of zimbra.soap.url to match your deployment:

 zimbra.soap.url
           http://localhost:7070/service/soap

This value is commented out in RC2 and determined automatically via the other settings.

[v912485]

Thanks for the quick reply, it's much appreciated.

Yep, zimbra.soap.url is pointing to http://localhost:7070/service/soap.

Also on the admin side I just get a blank (brownish) page.

[woeper]

Originally Posted by v912485

I get the same error as woeper, but unfortunately neither a reboot nor clearing the cache helps. I also run the 4.5 RC1 but on CentOS.
On the advanced client I get the message (INVALID_PDU) and on the basic client I get "A network service error has occurred (zclient/io)".
The source of the advanced client does not show a stacktrace but the basic on does:

Allan

With 4.5 RC2 i have no problems anymore !

[v912485]

With 4.5 RC2 i have no problems anymore !

Great, I'm now eagerly awaiting for the RHEL version to be made available.

[v912485]

OK. just downloaded RC2, but that did not solve the problem. During installation I get the following error:

Initializing Documents...
Getting ldap default cos attribute zimbraFeatureNotebookEnabled from ldap.

Getting global config attribute zimbraNotebookAccount from ldap.

*** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled TRUE

ERROR: zclient.IO_ERROR (invoke unable to parse response:

HTTP Status 404 - Servlet AdminServlet i
s not available

---

type Status report

message Servlet AdminServlet is not available

de
scription The requested resource (Servlet AdminServlet is not available) is not available.

---

Apache Tomcat/5.5
.15

, server: localhost) (cause: com.zimbra.soap.SoapParseException unable to parse response: ead>

HTTP Status 404 - Servlet AdminServlet is not available

---

type Status report

message >Servlet AdminServlet is not available

description The requested resource (Servlet AdminServlet is not available) is not available. p>

---

Apache Tomcat/5.5.15

)

Anyone any ideas what could be the problem?

Allan

[v912485]

OK, I managed to solve the problem. Somehow during the initialisation of the soap servlet Zimbra ran out of Java Heap Space. So I had to increase the memory (a lot). But now everything seems to be fine.

One side note: the log file zimbra.log has been renamed to mailbox.log. It took me a while before I found this out.

Anyway, I'm a happy camper again.
Allan

[davidswanson1]

I encountered the same problem. I found that my system time was rest back to 2006. I sync with my NTP server and everything worked.