Hi Marco, The FCGI spawning functionality was added to the project before the dynamic configuration change support. I think the issue may be that the FCGI socket is not getting cleaned up during the reload. Unless someone else jumps on it, I plan to investigate this bug in the next week or two when I can get a little time.
Roger On Sun, Aug 9, 2009 at 9:03 AM, Marco Vittorini Orgeas <[email protected]>wrote: > Marco Vittorini Orgeas <ma...@...> writes: > > > > > As in subject, > > I am using the latest stable version of supervisord: > > if I comment out my php-cgi fcgi program section,supervisord will restart > > without problems after sending a SIGHUP. > > > > If the section is commented-out, supervisord just stops itself. > > > > Is that behavior normal, or I left something in the documentation ? > > > > thank you > > > > Some more details: > > If from supervctl shell I enter the reload command,supervisord just shuts > off as > well. > > The fcgi section is as simple as: > [fcgi-program:php_cgi] > socket=tcp://127.0.0.1:10005 > command=/usr/bin/php-cgi > > and the relevant log section seems to contain no related data: > > 2009-08-09 16:31:12,928 INFO success: nginx entered RUNNING state, process > has > stayed up for > than 1 seconds (startsecs) > 2009-08-09 16:31:12,928 INFO success: p5httpd entered RUNNING state, > process has > stayed up for > than 1 seconds (startsecs) > 2009-08-09 16:31:12,928 INFO success: php_cgi_2 entered RUNNING state, > process > has stayed up for > than 1 seconds (startsecs) > 2009-08-09 16:31:12,929 INFO success: php_cgi_3 entered RUNNING state, > process > has stayed up for > than 1 seconds (startsecs) > 2009-08-09 16:31:12,929 INFO success: php_cgi_0 entered RUNNING state, > process > has stayed up for > than 1 seconds (startsecs) > 2009-08-09 16:31:12,929 INFO success: php_cgi_1 entered RUNNING state, > process > has stayed up for > than 1 seconds (startsecs) > 2009-08-09 16:31:28,036 WARN received SIGHUP indicating restart request > 2009-08-09 16:31:28,036 DEBG fd 35 closed, stopped monitoring > <POutputDispatcher > at 47813206286064 for <Subprocess at 47813195236992 with name php_cgi_1 in > state > RUNNING> (stderr)> > 2009-08-09 16:31:28,036 DEBG fd 31 closed, stopped monitoring > <POutputDispatcher > at 47813206285776 for <Subprocess at 47813195236992 with name php_cgi_1 in > state > RUNNING> (stdout)> > 2009-08-09 16:31:28,037 DEBG killing php_cgi_1 (pid 845) with signal > SIGTERM > 2009-08-09 16:31:28,037 DEBG fd 26 closed, stopped monitoring > <POutputDispatcher > at 47813206285200 for <Subprocess at 47813195236920 with name php_cgi_0 in > state > RUNNING> (stdout)> > 2009-08-09 16:31:28,037 DEBG fd 30 closed, stopped monitoring > <POutputDispatcher > at 47813206285488 for <Subprocess at 47813195236920 with name php_cgi_0 in > state > RUNNING> (stderr)> > 2009-08-09 16:31:28,037 DEBG killing php_cgi_0 (pid 844) with signal > SIGTERM > 2009-08-09 16:31:28,037 DEBG fd 25 closed, stopped monitoring > <POutputDispatcher > at 47813206284912 for <Subprocess at 47813195237136 with name php_cgi_3 in > state > RUNNING> (stderr)> > 2009-08-09 16:31:28,037 DEBG fd 21 closed, stopped monitoring > <POutputDispatcher > at 47813206284624 for <Subprocess at 47813195237136 with name php_cgi_3 in > state > RUNNING> (stdout)> > 2009-08-09 16:31:28,037 DEBG killing php_cgi_3 (pid 843) with signal > SIGTERM > 2009-08-09 16:31:28,037 DEBG fd 16 closed, stopped monitoring > <POutputDispatcher > at 47813206282968 for <Subprocess at 47813195237064 with name php_cgi_2 in > state > RUNNING> (stdout)> > 2009-08-09 16:31:28,037 DEBG fd 20 closed, stopped monitoring > <POutputDispatcher > at 47813206284336 for <Subprocess at 47813195237064 with name php_cgi_2 in > state > RUNNING> (stderr)> > 2009-08-09 16:31:28,037 DEBG killing php_cgi_2 (pid 841) with signal > SIGTERM > 2009-08-09 16:31:28,037 INFO waiting for nginx, p5httpd, php_cgi_2, > php_cgi_3, > php_cgi_0, php_cgi_1 to die > 2009-08-09 16:31:28,041 INFO stopped: php_cgi_1 (exit status 0) > 2009-08-09 16:31:28,041 DEBG received SIGCLD indicating a child quit > 2009-08-09 16:31:28,044 INFO stopped: php_cgi_0 (exit status 0) > 2009-08-09 16:31:28,045 DEBG received SIGCLD indicating a child quit > 2009-08-09 16:31:28,048 INFO stopped: php_cgi_3 (exit status 0) > 2009-08-09 16:31:28,048 DEBG received SIGCLD indicating a child quit > 2009-08-09 16:31:28,052 INFO stopped: php_cgi_2 (exit status 0) > 2009-08-09 16:31:28,052 DEBG received SIGCLD indicating a child quit > 2009-08-09 16:31:28,052 DEBG fd 11 closed, stopped monitoring > <POutputDispatcher > at 47813206283256 for <Subprocess at 47813195236632 with name p5httpd in > state > RUNNING> (stdout)> > 2009-08-09 16:31:28,052 DEBG fd 15 closed, stopped monitoring > <POutputDispatcher > at 47813206283832 for <Subprocess at 47813195236632 with name p5httpd in > state > RUNNING> (stderr)> > 2009-08-09 16:31:28,052 DEBG killing p5httpd (pid 840) with signal SIGTERM > 2009-08-09 16:31:28,053 INFO stopped: p5httpd (terminated by SIGTERM) > 2009-08-09 16:31:28,053 DEBG received SIGCLD indicating a child quit > 2009-08-09 16:31:28,053 DEBG fd 8 closed, stopped monitoring > <POutputDispatcher > at 47813206269248 for <Subprocess at 47813195236416 with name nginx in > state > RUNNING> (stdout)> > 2009-08-09 16:31:28,053 DEBG killing nginx (pid 839) with signal SIGTERM > 2009-08-09 16:31:28,056 INFO stopped: nginx (exit status 0) > 2009-08-09 16:31:28,056 DEBG received SIGCLD indicating a child quit > 2009-08-09 16:31:28,064 CRIT Supervisor running as root (no user in config > file) > > For restart I have to SIGHUP or KILL (it's the same at the moment) and then > manually relaunch supervisord form command line. > > again thank you > > > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
