Daemon mode problems when running in chroot environment.

[GoogleCodeExporter]

As first reported in:

  http://groups.google.com/group/modwsgi/browse_frm/thread/e1dd9bfa85d936fc

there may be issues with daemon mode when executing in chroot environment.

In particular, daemon mode starts up okay and requests handled, but when WSGI 
file is touched and 
process restart triggered, the daemon processes are crashing, most likely on 
startup of new 
process. This would probably cause a continuous cycle of restarts and crashes.

More details need to be collected at this point to identify cause.

Original issue reported on code.google.com by Graham.Dumpleton@gmail.com on 18 May 2008 at 5:08

[GoogleCodeExporter]

Understanding is that when Apache chroot option being used, that chroot only 
occurs in Apache child process 
after it has forked. Since not in Apache parent, can't be affecting daemon mode 
processes. Thus unlikely that 
choot was issue with daemon mode processes crashing, but likely some other 
issue.

Marking this as invalid and will only look at it again if someone else sees it 
and can provide some good 
information to help track problem down.

Original comment by Graham.Dumpleton@gmail.com on 29 Oct 2008 at 10:48

• Changed state: Invalid

[GoogleCodeExporter]

I have exactly the same issue except that I do not use chroot.

When I do apache2 restart to clear up zombies I often end up with this:
$ ps aux|grep apache
root      7883  0.0  0.3  18916  2928 ?        Ss   09:17   0:00 
/usr/sbin/apache2 -k
start
max       7905  0.0  0.0   3004   752 pts/0    R+   09:18   0:00 grep apache

IOW, apache doesn't serve requests at all. Strangely though that after 5-10 
minutes
it usually starts working as if nothing happened.

I'll provide you with extra info, let me know what's needed.

Original comment by ische...@gmail.com on 10 Nov 2008 at 10:29

[GoogleCodeExporter]

ischenko: would suggest your issue is probably different. Suggest you bring it 
up on:

  http://groups.google.com/group/modwsgi?hl=en

providing as much detail of what you can. Also suggest you use display-name 
option to WSGIDaemonProcess so 
it can be clearly seen in 'ps' output which are mod_wsgi daemon processes.

Using the list is a much better place than a ticket to initially investigate an 
issue like this.

Original comment by Graham.Dumpleton@gmail.com on 10 Nov 2008 at 11:42

[GoogleCodeExporter]

Posted,
http://groups.google.com/group/modwsgi/browse_thread/thread/a71386256bc45d45?hl=
en

Original comment by ische...@gmail.com on 11 Nov 2008 at 8:07