On Mon, Dec 15, 2008 at 4:56 AM, Stefan Wallner
<[email protected]> wrote:
>
> Hi,
> let me first admit that this is a repost of my message to django-users
> since I am now beginning to wonder if this is more a mod_wsgi
> (configuration/etc) issue instead of Django related. Sorry for
> crossposting, but this problem is given me a major headache and I
> cannot seem to find anything wrong with the Django configuration.
>
> Thanks for any help, if you need more details let me know.
Are your development and production server configurations identical?
Maybe you are just doing some things differently on your production
server?
Do you have ADMINS set to a list of emails that will receive the error
messages? If you only have one email address in there remember to add
a trailing comma after that single email address:
ADMINS = (
('Admin Example', '[email protected]'),
)
Also, traceback info will usually go into a separate log file. Not
sure how you installed and configured Apache on Windows but there
should be a "errors" file where all the Traceback info gets logged.
You might also want to check Windows system event logs.
You can also try sending email from your production server using
Django's mail sending function. Use your SERVER_EMAIL as the From
address with the email addresses you have in ADMINS as the recipients
and see what happens. Set up a simple view to do just that, so that it
executes within the context of your Apache and mod_wsgi setup.
> Stefan
>
>
>
>
> Message from django-users (http://groups.google.com/group/django-users/
> browse_thread/thread/75102033de50ee06)
>
>
> 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
>
> >
>
--
Best Regards,
Nimrod A. Abing
W http://arsenic.ph/
W http://preownedcar.com/
W http://preownedbike.com/
W http://abing.gotdns.com/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
