Graham Dumpleton wrote: >> using mod_wsgi in apache2. >> > > But what version of mod_wsgi. Make sure you are using version 2.3 if > using older version. >
2.3 exact debian version is: 2.3-1~bpo40+1 >> 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. > I have a problem apache workers running out due to trac misbehavior. if anything, I will reduce this number to something that will not take down the entire apache server whenever trac is acting up. > 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. > Added this, thanks. will this incident be logged anywhere? it can be useful to get the stuck urls when this happens. > 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_Crashes_With_GDB > > for pointers on how to do that. > This link is about debugging apache crashes. my apache does not crash, instead if stop responding to any requests because all the workers are busy with trac. so I don't think this will be helpful. > 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. > osimons mentioned this to me on the irc channel, but I am not using the [[TOC]] macro so it's not the cause for my problem. Omry. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
