I ran into the same issue with supervisor-wildcards and put in fix that seems to work. The pull request is here.
https://github.com/aleszoulek/supervisor-wildcards/pull/2 Cheers, Roger Bar Ziony <bartzy@...> writes: > > Hi Mike, > Thanks, I just verified that this is the issue - stdout/stderr is not logged to file after stopping the child via supervisorctl. > I'm running 3.0a8, but this is fine by me (debian packaged release) if the TERM actually happens but no logging occurs (I don't do any logging from the processes on TERM anyway). > > Ales - I have an issue though with supervisor-wildcards. I installed it and can see and use mstart/mstop/mrestart, but look what happens when I do this: > > supervisor> mstart s3_upload* > s3_upload_00: ERROR (no such process) > s3_upload_01: ERROR (no such process) > s3_upload_04: ERROR (no such process) > s3_upload_03: ERROR (no such process) > s3_upload_02: ERROR (no such process) > supervisor> > > supervisor> mstart s3_upload:* > No process matched given expression. > supervisor> > > > It seems like it works only for a single-process 'program' configuration? Can that be fixed somehow? > > Thanks Mike & Ales! > > On Wed, Feb 22, 2012 at 9:27 PM, Mike Naberezny <mike <at> maintainable.com> wrote:Hi Bar, > > On 2/22/12 10:47 AM, Bar Ziony wrote: > With this supervisor config (below), however, I can't see the "SIGTERM!" > output in the log specified in the config when I stop the processes via > supervisorctl stop s3_upload:* > > > > In Supervisor 3.0a10, a bug was fixed that caused some log output to be missed when stopping a subprocess. Please upgrade if you are running an earlier version. > An easy way to verify that your test script is receiving the signal without depending on log output is to replace echo() with touch() and then check that the file is touched. > Regards, > Mike
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
