So I spent the last few days debugging and was able to solve half the problem, i.e. the mails-not-getting-sent one: Turns out that the mail server I was told to use does swallow messages containing a stack trace, presumably due to spam filtering. The nice thing was that a) the sys admin told me that this was not happening and b) I first tested only by using mail_admins from the shell with a simple subject/body combination, which did work and fooled me into believing that there was indeed nothing wrong with the mail sever. That was a hard lesson learned.
But, the problem of the traceback not showing in the log files is still there and I have been unable to make anymore progress in tracking this one down. Can someone enlighten me where the traceback is supposed to get logged in django.core.handlers.WSGIHandler (which I understand to be the "root" of Django when running under WSGI)? I've tried to follow how that works, and it seems eventually an exception ends up in django.core.handlers.base.handle_uncaught_exception, which is where the mail is sent and the pretty http500 page gets returned. But I cannot figure out where the stack trace would be sent to the error log in this case? Does that even happen by default or do I need to customize something? In basehttp.py things are clear - there is log_exception which prints out the stack trace. Not clear at all for me in the case of WSGI. I'd very much appreciate if someone could point me to the right direction so I can poke around some more in the right place for what's going on. Thanks! Stefan On Dec 14, 5:50 am, Stefan Wallner <montodes...@googlemail.com> wrote: > Hi, > I am running Django 1.0 on Windows Server 2003, Python 2.5 with > mod_wsgi. I am having trouble capturing any exceptions in my code > either through Apache's error log or by having an email sent to me. > > As a simple test I added > a = [1,2,3] > b = a[4] > to the top of one of my views, which does generate an IndexError > exception, but is not being reported in the error log or by email > either. > > The mod_wsgi configuration is stricly as described on mod_wsgi's > website (http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango), > but even with LogLevel info in my Apache conf I do not see anything in > my error log (related to the exception in the Django code, a bunch of > other Apache messages do get printed). > > As for receiving the stack traces via email I have SERVER_EMAIL, etc. > setup and can confirm that it works when I am running it with the > development server and I can send email on this server (tested both on > the dev server and the production server by a different part of code > in my application). > > If DEBUG is set to True I can see the stack trace in the browser, but > with true production mode all errors are silently lost. > > Any ideas or pointers on what is going on or what else I should do? > > Thanks, > Stefan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
