I think the program's configuration needs to include: stopsignal = INT
The default stop signal is TERM. See also the stopsignal description within http://supervisord.org/configuration.html#program-x-section-settings - C On Tue, 2010-08-24 at 10:47 -0700, Roger Hoover wrote: > Hmm...you also mind get more information by running strace on > supervisord and see what signal is getting sent. > > On Tue, Aug 24, 2010 at 10:17 AM, Dean Banks <[email protected]> > wrote: > I am running supervisor in a terminal using the following in > my supervisord.conf: > > loglevel=debug > nodaemon=true > > so it should be equivalent to the command line that you > suggest. The logfile excerpt that I included in my initial > post was developed using these options. > > Cheers. > > > > > > On 8/24/2010 9:37 AM, Roger Hoover wrote: > > Try running supervisor on the command line in debug mode: > > > > > > supervisord -n -e debug > > > > On Tue, Aug 24, 2010 at 8:47 AM, Dean Banks > > <[email protected]> wrote: > > I am using supervisord v3.0a9 to spawn and manage a > > FastCGI application that I am writing in C for a > > linux target. I have a signal handler that > > gracefully exits my application when SIGINT is > > received. I have verified that the signal handler > > works as desired by running the app in a terminal > > window and issuing Ctrl-C to exit. > > When issuing a "shutdown" command to supervisord > > (via supervisorctl), it appears that supervisord is > > unable to force the app to exit without invoking > > SIGKILL: > > > > 2010-08-20 10:02:49,661 INFO waiting for cse to die > > 2010-08-20 10:02:52,665 INFO waiting for cse to die > > 2010-08-20 10:02:55,669 INFO waiting for cse to die > > 2010-08-20 10:02:58,672 INFO waiting for cse to die > > 2010-08-20 10:02:59,673 WARN killing 'cse' (2031) with > SIGKILL > > 2010-08-20 10:02:59,674 INFO stopped: cse (terminated by > SIGKILL) > > > > I have the following in my supervisord.conf file > > > > stopsignal=INT > > > > It seems that my app is not responding to or not > > receiving the SIGINT issued by supervisord. > > > > How do I go about debugging the signal passing > > between supervisord and my app? > > > > > > > > > > > > > > > > _______________________________________________ > > 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 _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
