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 soap error

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
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 08-06-2009, 09:45 PM
Starter Member
  
Posts: 2
Default soap error
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:
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>
Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre>
<p>RequestURI=/service/admin/soap/</p></body></html>, server: localhost)
(cause: com.zimbra.common.soap.SoapParseException cannot determine soap protocol in reply:
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>
RequestURI=/service/admin/soap/</p></body></html>)

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.
Reply With Quote
  #2 (permalink)  
Old 11-20-2009, 02:37 PM
Junior Member
  
Posts: 9
Default
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;
Reply With Quote
  #3 (permalink)  
Old 11-20-2009, 03:24 PM
Moderator
  
Posts: 1,147
Default
Well the problem is that when the command asks for the SOAP response it is getting back an HTML document along the lines of:
Code:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title>
</head>
<body><h2>HTTP ERROR: 503</h2>
<pre>SERVICE_UNAVAILABLE</pre>
<p>RequestURI=/service/admin/soap/</p>
</body></html>
Is the mailbox service starting properly? Does something like this work at all (run as zimbra user of course)
Code:
zmsoap -z GetServiceStatusRequest
Reply With Quote
  #4 (permalink)  
Old 11-20-2009, 04:12 PM
Junior Member
  
Posts: 9
Default
Quote:
Originally Posted by ArcaneMagus View Post
Well the problem is that when the command asks for the SOAP response it is getting back an HTML document along the lines of:
Code:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title>
</head>
<body><h2>HTTP ERROR: 503</h2>
<pre>SERVICE_UNAVAILABLE</pre>
<p>RequestURI=/service/admin/soap/</p>
</body></html>
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:
Originally Posted by ArcaneMagus View Post
Is the mailbox service starting properly? Does something like this work at all (run as zimbra user of course)
Code:
zmsoap -z GetServiceStatusRequest
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: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap</p></body></html>
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:246)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:224)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:277)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:226)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:315)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:279)
at com.zimbra.common.soap.SoapCommandUtil.adminAuth(S oapCommandUtil.java:281)
at com.zimbra.common.soap.SoapCommandUtil.run(SoapCom mandUtil.java:347)
at com.zimbra.common.soap.SoapCommandUtil.main(SoapCo mmandUtil.java:451)


Ergo, I'm still baffled...
Reply With Quote
  #5 (permalink)  
Old 11-20-2009, 04:17 PM
Moderator
  
Posts: 1,147
Default
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?
Reply With Quote
  #6 (permalink)  
Old 11-20-2009, 04:25 PM
Junior Member
  
Posts: 9
Default
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: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/soap</p></body></html>
ExceptionId:btpool0-7:1258757582964:72e2516567f0dc4f
Code:zclient.IO_ERROR
at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZC lientException.java:47)
at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:522)
at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:508)
at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMai lbox.java:453)
at com.zimbra.cs.zclient.ZMailbox.<init>(ZMailbox.jav a:365)
at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox .java:314)
at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.j ava:124)
at org.apache.jsp.public_.login_jsp._jspService(login _jsp.java:284)
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:305)
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:350)
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)
Caused by: com.zimbra.common.soap.SoapParseException: cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/soap</p></body></html>
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:246)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:224)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:277)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:226)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:315)
at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:514)
... 50 more
Reply With Quote
  #7 (permalink)  
Old 11-20-2009, 04:41 PM
Moderator
  
Posts: 1,147
Default
Have you tried restarting the mailbox service on the servers experiencing this problem?
Reply With Quote
  #8 (permalink)  
Old 11-20-2009, 05:34 PM
Junior Member
  
Posts: 9
Default
Services have been restarted, servers have been rebooted (multiple times)

Pretty much gone through all of the 'easy/common' ideas... <G>

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...
Reply With Quote
  #9 (permalink)  
Old 11-21-2009, 08:55 AM
Junior Member
  
Posts: 9
Default
Another note... Regenerating the certificates did not help...
Reply With Quote
Reply

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

Thread Tools Search this Thread
Search this Thread:

Advanced Search
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.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.