[Zope] Erratic HTTP 500

[sean.upton@uniontrib.com]

Thanks, I was able to figure out what it was.

I'm seeing it in Z2.log on the badly behaving node; looks like a failed ZSQL
Method due to a closed database connection or non-functional DA can cause
Zope to return an HTTP 500; an accidental change to MySQL permissions caused
the connection to die... I did everything in trying to investigate what was
going on except the obvious, which was check the connectivity of the
database that I use in my automated procedure... I know better next time...

Sean

-----Original Message-----
From: Dieter Maurer [mailto:dieter@handshake.de]
Sent: Tuesday, November 06, 2001 2:27 PM
To: sean.upton@uniontrib.com
Cc: zope@zope.org
Subject: Re: [Zope] Erratic HTTP 500


sean.upton@uniontrib.com writes:
 > Anybody have any thoughts on what problems might trigger an HTTP 500 in
 > Zope?
Provided that the 500 response is generated by Zope and not
the SQUID in front, it means that there has been an exception
that ZPublisher is unable to map to a different response
code (such as 'Unauthorized' and 'redirect').

Catch exceptions in your process and print them.
Then you get a better feeling what goes wrong.

If the response is generated by SQUID, then Zope died (or timed out).
In this case, use the "-M" option (-> mailing list archives),
to analyse the circumstances of the deaths.


Dieter