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 <connexi...@gmail.com> 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 die2010-08-20 10:02:52,665 > INFO waiting for cse to die2010-08-20 10:02:55,669 INFO waiting for cse to > die2010-08-20 10:02:58,672 INFO waiting for cse to die2010-08-20 10:02:59,673 > WARN killing 'cse' (2031) with SIGKILL2010-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 > Supervisor-users@lists.supervisord.org > http://lists.supervisord.org/mailman/listinfo/supervisor-users > >
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org http://lists.supervisord.org/mailman/listinfo/supervisor-users
