For reference, also see: https://www.coderesort.com/about/blog/sporadic_hang_solved
This was mention on #trac. Not sure if that was by you or you were part of conversation. Graham On Oct 2, 5:49 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Oct 2, 5:25 pm, Omry Yadan <[EMAIL PROTECTED]> wrote: > > > > Please clarify your hosting configuration. What do you mean by WSGI? > > > > Do you mean, running Trac under Apache/mod_wsgi? > > > > Or do you mean, running tracd and proxying Apache through to tracd? > > > > Or do you mean, running Trac under some other WSGI server and proxying > > > Apache through to that WSGI server instance? > > > > The link you give for mod_status doesn't work, at least via Google > > > groups. > > > using mod_wsgi in apache2. > > But what version of mod_wsgi. Make sure you are using version 2.3 if > using older version. > > > this is my vhost file : > > > IWSGIDaemonProcess firestats.cc user=omry group=omry threads=25 > > maximum-requests=100 > > I would use more than 100 requests for maximum-requests unless the > memory leaks in your application are quite bad. Value of 1000 would be > more reasonable. > > If you are use mod_wsgi 2.X, there is a deadlock timeout of 300 > seconds and so if the whole process was being deadlocked by problem > code, it should automatically kill of process and restart it. Although > this will not help if Python code had released GIL and were hung on > access to back end database. > > For this latter situation, you can add to WSGIDaemonProcess the > option: > > inactivity-timeout=120 > > If all threads get hung and nothing happens for 120 seconds, the > process should be automatically be killed off and restarted. This at > least may get you out of situation where manual intervention required. > > Other than that, looks perhaps that database requests may be hanging. > You possibly need to attach gdb to stuck process and look at stack > traces to see if stuck in third party C extension module such as a > database module. See: > > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Debugging_C... > > for pointers on how to do that. > > Graham > > > <VirtualHost *:80> > > WSGIProcessGroup firestats.cc > > WSGIApplicationGroup %{GLOBAL} > > > ServerName firestats.cc > > ServerAliaswww.firestats.cc > > ServerAdmin omry > > ErrorLog /home/omry/logs/firestats.cc/error.log > > > WSGIScriptAlias / /home/omry/www/trac/trac.wsgi > > SetEnv trac.env_path /home/omry/www/trac/firestats.cc > > </VirtualHost> > > > Attached a zip with the html file, hopefully this will work better. > > > Thanks. > > > status.zip > > 7KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
