Wondering how to resolve Zimbra 500 server error? We can help you.
As part of our Server Management Services, we assist our customers with similar queries.
Today, let us see how our Support techs assist with this process.
How to resolve Zimbra 500 server error?
Zimbra Collaboration, formerly known as the Zimbra, is a collaborative software suite that includes an email server and a web client.
Typically, error will look as shown below:
500 Internal server errorOn each reload of the page, the following might written to /opt/zimbra/log/mailbox.log:
2019-12-04 17:47:35,364 WARN [qtp509886383-145:https://10.0.42.6:443/zimbra/] [] misc - Problem parsing XML - Fatal Error: Problem on line 10 of document : The element type "hr" must be terminated by the matching end-tag "</hr>".
2019-12-04 17:47:35,484 WARN [qtp509886383-145:https://10.0.42.6:443/zimbra/css/common,login,zhtml,skin.css?skin=&v=] [] misc - Problem parsing XML - Fatal Error: Problem on line 10 of document : The element type "hr" must be terminated by the matching end-tag "</hr>".
2019-12-04 17:47:35,557 WARN [qtp509886383-145:https://10.0.42.6:443/zimbra/img/dwt/Img parsing XML - Fatal Error: Problem on line 10 of document : The element type "hr" must be terminated by the matching end-tag "</hr>".Using zmprov resulted in the following output:
[] WARN: Problem parsing XML - Fatal Error: Problem on line 10 of document : The element type "hr" must be terminated by the matching end-tag "</hr>".
ERROR: zclient.IO_ERROR (invoke unable to parse response: <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 500 Server Error</title>
</head>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /service/admin/soap/AuthRequest. Reason:
<pre> Server Error</pre></p><hr><i><small>Powered by Jetty://</small></i><hr/></body>
</html>
, server: localhost) (cause: com.zimbra.common.soap.SoapParseException unable to parse response: <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 500 Server Error</title>
</head>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /service/admin/soap/AuthRequest. Reason:
<pre> Server Error</pre></p><hr><i><small>Powered by Jetty://</small></i><hr/>
</body>
</html>
)The reason for that was that SOAP had become completely unusable.
Then, using zmprov to talk directly to LDAP (as in, zmprov –ldap gacf) will work.
Usually, the problem might be a faulty entry: zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.42.163/32, which works in newer Zimbra versions, but makes all hell break loose in 8.6.0.
That release only supports putting in singular IP addresses – no CIDR.
Today, let us see the steps followed by our Support Techs to resolve it.
- Firstly, deleted that configuration entry directly from LDAP.
- Next, ldapmodify should do the trick just fine if you’re comfortable with it.
- Then, restart zmmailbox, and everything will be fine.
[Stuck in between? We’d be glad to assist you]
Conclusion
In short, today we saw steps followed by our Support Techs to resolve Zimbra server error.
0 Comments