2008/11/11 Max Ischenko <[EMAIL PROTECTED]>: > > Hi, > > I recently switched to mod_wsgi from reverse proxy setup. I used to > reload apache config with force-reload (graceful) command. When I > attempt to use it now I get zombie processes. Log: > > (py)[EMAIL PROTECTED] ps aux|grep apache > root 5074 0.0 1.2 27476 10484 ? Ss Nov10 0:09 /usr/ > sbin/apache2 -k start > www-data 5308 0.0 0.7 27476 6444 ? S 10:03 0:00 /usr/ > sbin/apache2 -k start > www-data 5309 0.0 0.7 27476 6048 ? S 10:03 0:00 /usr/ > sbin/apache2 -k start > www-data 5310 0.0 0.7 27476 6048 ? S 10:03 0:00 /usr/ > sbin/apache2 -k start > www-data 5311 0.0 0.7 27476 6048 ? S 10:03 0:00 /usr/ > sbin/apache2 -k start > www-data 5312 0.0 0.7 27476 6048 ? S 10:03 0:00 /usr/ > sbin/apache2 -k start > max 5316 0.0 0.0 3004 748 pts/0 R+ 10:03 0:00 grep > apache > (py)[EMAIL PROTECTED] sudo /etc/init.d/apache2 force-reload > * Reloading web server config > apache2 apache2: > Could not reliably determine the server's fully qualified domain name, > using staging4.developers.org.ua for ServerName > > [ OK ] > (py)[EMAIL PROTECTED] ps aux|grep apache > root 5074 0.0 0.9 22112 7664 ? Ss Nov10 0:09 /usr/ > sbin/apache2 -k start > www-data 5308 0.2 0.0 0 0 ? Z 10:03 0:00 > [apache2] <defunct> > www-data 5309 0.2 0.0 0 0 ? Z 10:03 0:00 > [apache2] <defunct> > www-data 5310 0.2 0.0 0 0 ? Z 10:03 0:00 > [apache2] <defunct> > www-data 5311 0.2 0.0 0 0 ? Z 10:03 0:00 > [apache2] <defunct> > www-data 5312 0.2 0.0 0 0 ? Z 10:03 0:00 > [apache2] <defunct> > max 5340 0.0 0.0 3004 748 pts/0 R+ 10:03 0:00 grep > apache > > I'm using mod_wsgi 2.3.x on Ubuntu 8.04, Apache/2.2.8 > > And when I get to this unfortunate state I usually have to reboot the > machine to make apache working again. Doing killall apache2 and > apache2 restart do not help often.
Zombie process in themselves are not bad, but may be indicative of other issues. The issue here is why Apache parent process hasn't reaped the process properly by reading their exit status. What I need to know is whether these zombies correspond to normal Apache child worker processes or mod_wsgi daemon processes. If using daemon mode, set display-name option as described in configuration directives documentation. Doing that, when running 'ps' you should be able to distinguish mod_wsgi daemon mode processes from normal Apache child worker processes. The next thing is whether you see the same problem for a normal Apache 'restart', which possibly corresponds to a 'reload' with your startup scripts. I know of some issues with a graceful restart with mod_wsgi, but at this point wouldn't expect this as the result. FWIW, more information on zombie processes and why they exist can be found at: http://en.wikipedia.org/wiki/Zombie_process 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 -~----------~----~----~----~------~----~------~--~---
