Tom Barrett wrote: > Due to my issues with the current version of supervisord, I've built > another dev box to see if I can get things working in principle. > > Here is my php-cgi configuration block: > > ;[fcgi-program:php] > [fcgi-program:php-cgi] > command=/usr/bin/php-cgi > ;command=/usr/bin/php-cgi -c /etc/php.ini -b /tmp/php.socket > ;command=/path/to/php-cgi > ;socket=unix:///tmp/%program_name)s.sock > socket=tcp://127.0.0.1:57093 <http://127.0.0.1:57093> > process_name=%(program_name)s_%(process_num)02d > user=apache > numprocs=2 > priority=999 > autostart=true > autorestart=true > startsecs=1 > startretries=3 > exitcodes=0,2 > stopsignal=QUIT > stopwaitsecs=10 > > > python -V > Python 2.4.3 > > supervisorctl status > php-cgi:php-cgi_00 RUNNING pid 18020, uptime 16:20:49 > php-cgi:php-cgi_01 RUNNING pid 18019, uptime 16:20:49 > > It's running on tiny 256Mb slice, where the php-cgi processes die > unexpectedly (possibly due to lack of memory, but I don't know for sure). > The idea being that supervisord would auto restart them if this happens, > however it doesn't. They just end up in status 'EXITED' (to my > recollection). > > What is it I am missing to make supervisord restart them? Can I manually > trigger such an event (via kill, perhaps) to test that it works?
Please try running supervisor like so: supervisord -n -edebug This will run it in the foreground with the debug log printing to stdout, including child process output, which might give you a clue. - C _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
