2009/6/30 mmcgrath <[email protected]>: > > We're using mod_wsgi to deploy a few apps, mostly TurboGears. We are > getting some mysterious 500's from time to time. The show up in our > access log, but not in the error logs. The 500 itself seems to be > coming from apache and not cherrypy. Also we cannot reproduce the > error manually with any success. It just randomly happens and we > aren't sure what is going on. Here is our config: > > WSGISocketPrefix run/wsgi > > # TG implements its own signal handler. > WSGIRestrictSignal Off > > # These are the real tunables > WSGIDaemonProcess fas processes=8 threads=2 maximum-requests=50000 > user=fas group=fas display-name=fas inactivity-timeout=300 shutdown- > timeout=10 > WSGIPythonOptimize 1 > > WSGIScriptAlias /accounts /usr/lib/python2.4/site-packages/fas/ > fas.wsgi/accounts
You also have: WSGIProcessGroup fas don't you? If not, you aren't using daemon mode as you think you are. > Does anything jump out as obviously wrong there? What version of mod_wsgi are you using? Have you set: LogLevel info to enable greater level of mod_wsgi messages in error logs? Do the 500 error correspond within when that additional logging says that daemon processes are being restarted? Do you handle any requests that can take more than 10 seconds? Is there any sort of error in error logs at about time 500 error occurs, even ones not from mod_wsgi or Python? 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 -~----------~----~----~----~------~----~------~--~---
