Hey, I'm working with Mike on debugging these 500s. On 2009-06-30 08:40:52 AM, Graham Dumpleton wrote: > Any chance you can upgrade to mod_wsgi 2.5. Various issues have been > fixed between 2.1 and 2.5 and wouldn't rule out that problem has > already been fixed. Sure, we can try reproduce with with a mod_wsgi 2.5. As a side question, do you think the various bug fixes from 2.1 to 2.5 are significant enough that the mod_wsgi package in the EPEL repository should be updated? We usually try to only update EPEL packages for important bugfixes in order to keep those packages as stable as possible, but I'd be happy to talk to the maintainer about it if it should be updated.
> BTW, do you have TG setup so as to capture internal 500 error messages > and send an email or something when they occur. Often frameworks will > internally capture Python exceptions, generate a 500 error page but > not log anything. Instead you are expected to configure it to log it > or email details to someone when run in a production setting. For all other errors that we have faced so far, TurboGears does show the tracaback in the error log. We did try wrapping our application in error reporting middleware, but we never received any notifications when the 500s occured. We also attempted wrapping some simple middleware around our application which would run the application in between two print statements. When the 500s occured, the first print showed up in the logs, but the second didn't :-/ Can you think of any anything that could kill the application like that without mentiong in the error log? Thanks, Ricky
pgpgYV8nDrNLH.pgp
Description: PGP signature
