Quote:
Originally Posted 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: 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 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...