On 2 March 2011 09:42, bc <[email protected]> wrote: > A few times I've had errors in the wsgi file, such that python would > barf on it. It doesn't get far enough to hit any debug logging code in > the script, or return anything via wsgi structures. And, I don't see > anything in the apache error log: no error report, and no indication > that anything happened. It just silently returns a 500. LogLevel is > set to warn. > > An example would be an "import" at the top of the file that doesn't > resolve correctly. > > Is there some way to get debug information at this level?
Details of exceptions at global scope in WSGI script file should be logged to Apache error log. What version of mod_wsgi are you using? Some older versions of mod_wsgi could see such logging go missing where HTTPS was used or other strange VirtualHost configurations. More details about your Apache configuration, use of VirtualHost, where setting ErrorLog directive etc would be helpful to understand the problem. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
