soap error

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
skinfax
Posts: 2
Joined: Fri Sep 12, 2014 10:07 pm

soap error

Post by skinfax »

Hello,

i cannot login to my server neither with web interface nor admin interface, no pop or imap services seem to function also. Though zmcontrol starts ok all services.
in the error log i see:

ERROR: zclient.IO_ERROR (invoke cannot determine soap protocol in reply:



Error 503 SERVICE_UNAVAILABLEHTTP ERROR: 503SERVICE_UNAVAILABLE

RequestURI=/service/admin/soap/, server: localhost)

(cause: com.zimbra.common.soap.SoapParseException cannot determine soap protocol in reply:



Error 503 SERVICE_UNAVAILABLEHTTP ERROR: 503SERVICE_UNAVAILABLE

RequestURI=/service/admin/soap/)
I have searched the forum for this kind of errors but havent found a solution.
Does anyone knows what it may be?

How could i extract just the mailboxes and move them to a new server?
Thanks a lot for any help, i really need it.
jwilling
Posts: 14
Joined: Fri Sep 12, 2014 11:20 pm

soap error

Post by jwilling »

Did anyone ever hit on the answer to this? I've just had the same thing hit two of my servers, and I'm clueless. (no real JAVA/SOAP experience)
Thanks;
ArcaneMagus
Elite member
Elite member
Posts: 1138
Joined: Fri Sep 12, 2014 10:25 pm

soap error

Post by ArcaneMagus »

Well the problem is that when the command asks for the SOAP response it is getting back an HTML document along the lines of:





Error 503 SERVICE_UNAVAILABLE



HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/service/admin/soap/


Is the mailbox service starting properly? Does something like this work at all (run as zimbra user of course)

zmsoap -z GetServiceStatusRequest
jwilling
Posts: 14
Joined: Fri Sep 12, 2014 11:20 pm

soap error

Post by jwilling »

[quote user="ArcaneMagus"]Well the problem is that when the command asks for the SOAP response it is getting back an HTML document along the lines of:





Error 503 SERVICE_UNAVAILABLE



HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/service/admin/soap/

[/QUOTE]
Yes; kinda got that part... The underlying question would be why the service has suddenly gone unavailable? These servers had been running happily for well over a year, then both went South almost simultaneously...


[quote user="ArcaneMagus"]

Is the mailbox service starting properly? Does something like this work at all (run as zimbra user of course)

zmsoap -z GetServiceStatusRequest[/QUOTE]
Mailbox service running? It appears to per the following:
[zimbra@mail3 ~]$ zmcontrol status

Host mail3.xxxxxxxxxx.com

mailbox Running

snmp Running

spell Running

stats Running
But...
[zimbra@mail3 ~]$ zmsoap -z GetServiceStatusRequest

com.zimbra.common.soap.SoapParseException: cannot determine soap protocol in reply: Error 503 SERVICE_UNAVAILABLEHTTP ERROR: 503SERVICE_UNAVAILABLERequestURI=/service/admin/soap

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:246)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:224)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:277)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:226)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:315)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:279)

at com.zimbra.common.soap.SoapCommandUtil.adminAuth(SoapCommandUtil.java:281)

at com.zimbra.common.soap.SoapCommandUtil.run(SoapCommandUtil.java:347)

at com.zimbra.common.soap.SoapCommandUtil.main(SoapCommandUtil.java:451)


Ergo, I'm still baffled...
ArcaneMagus
Elite member
Elite member
Posts: 1138
Joined: Fri Sep 12, 2014 10:25 pm

soap error

Post by ArcaneMagus »

Are you seeing any errors in /opt/zimbra/log/mailbox.log or /var/log/zimbra.log?

How about when you restart the services?

Are these servers part of a multi-server install? (looks like it from what you are saying)
Are your certificates still valid?
jwilling
Posts: 14
Joined: Fri Sep 12, 2014 11:20 pm

soap error

Post by jwilling »

It is a multi-server configuration. The affected servers are the admin/logger servce and one of the two store servers. The MTA/LDAP server and the other store server continue to run happily...
The certificates should have been valid thru June of 2010 unless something odd happened to them all of a sudden. I could regenerate them if that has a chance of resolving anything?
Nothing unusual in /var/log/zimbra.log, there are however a number of entries in /opt/zimbra/log/mailbox, all of which appear to refer back to the "service unavailable" error. One example:
2009-11-20 16:53:02,965 WARN [btpool0-7] [] webclient - local exception

com.zimbra.cs.zclient.ZClientException: cannot determine soap protocol in reply: Error 503 SERVICE_UNAVAILABLEHTTP ERROR: 503SERVICE_UNAVAILABLERequestURI=/service/soap

ExceptionId:btpool0-7:1258757582964:72e2516567f0dc4f

Code:zclient.IO_ERROR

at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZClientException.java:47)

at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:522)

at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:508)

at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMailbox.java:453)

at com.zimbra.cs.zclient.ZMailbox.(ZMailbox.java:365)

at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox.java:314)

at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.java:124)

at org.apache.jsp.public_.login_jsp._jspService(login_jsp.java:284)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">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">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">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">HttpServlet.service(HttpServlet.java:820">HttpServlet.service(HttpServlet.java:820">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:305)

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:350)

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)

Caused by: com.zimbra.common.soap.SoapParseException: cannot determine soap protocol in reply: Error 503 SERVICE_UNAVAILABLEHTTP ERROR: 503SERVICE_UNAVAILABLERequestURI=/service/soap

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:246)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:224)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:277)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:226)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:315)

at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.java:514)

... 50 more
ArcaneMagus
Elite member
Elite member
Posts: 1138
Joined: Fri Sep 12, 2014 10:25 pm

soap error

Post by ArcaneMagus »

Have you tried restarting the mailbox service on the servers experiencing this problem?
jwilling
Posts: 14
Joined: Fri Sep 12, 2014 11:20 pm

soap error

Post by jwilling »

Services have been restarted, servers have been rebooted (multiple times)
Pretty much gone through all of the 'easy/common' ideas...
As an aside, zmprov ralphs in the same manner as everything else if left to it's own devices (trying to go thru SOAP), but if invoked to poll directly thru LDAP (example: zmprov -l gas) it runs...
Maybe no bearing, but a data point...
jwilling
Posts: 14
Joined: Fri Sep 12, 2014 11:20 pm

soap error

Post by jwilling »

Another note... Regenerating the certificates did not help...
adamf663
Posts: 29
Joined: Sat Sep 13, 2014 1:05 am

Re: soap error

Post by adamf663 »

3 years later... exact same issue after trying to restore system that only had /opt/zimbra backed up.
Post Reply