If Django is catching the error (ie. if DEBUG=True then you get a fancy formatted error page), then its a Django problem that its not being emailed to you. mod-wsgi doesn't get involved in that process at all. The only time you'd see an error/traceback in the apache logs should be if there's a syntax error and the Django app can't load/run at all, or if the exception occurs really high up in the Django WSGI handler (unlikely).
So maybe its a mail setting? I suspect (but haven't checked) that Django fails silently if it has problems trying to send error emails. Can your web server user send mail (console via mailx or in python as described earlier in the thread) -- "sudo su - www-data" (in Debian/Ubuntu) to become such a user. Just some ideas, Rob :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
