Hi Neil, On 11/7/12 2:10 PM, Neil Hooey wrote:
Can anyone confirm that this is actually working in the latest version of Supervisor?
The fix was noted in the 3.0a10 changelog and this is the related issue: https://github.com/Supervisor/supervisor/issues/11
Supervisor 3.0a10 definitely *does not* print log output after a process has been sent the "stop" command.
Another possibility is that Supervisor is not receiving the output. This can happen if the process is buffering its output and the buffer is not written out when the process is terminated. If it is a Python program, try running it with "python -u".
Regards, Mike
On Mon, Oct 22, 2012 at 2:50 PM, Neil Hooey <[email protected] <mailto:[email protected]>> wrote: I finally upgraded to Supervisor 3.0a10, and it's still not printing logs after a "stop" command is issued. The stopsignal for my Supervisor program is "INT". Has this been actually fixed in a more recent version of Supervisor? On Thu, May 17, 2012 at 10:37 PM, Mike Naberezny <[email protected] <mailto:[email protected]>> wrote: Hi Neil, On 5/17/12 11:21 AM, Neil Hooey wrote: There are no log lines printed after the process is stopped. Is there any way to get Supervisor to continue capturing logs after the signal has been sent? In Supervisor 3.0a10, a bug was fixed that caused some log output to be missed. Please upgrade if you are running an earlier version. Regards, Mike -- Mike Naberezny Maintainable Software http://maintainable.com _________________________________________________ Supervisor-users mailing list Supervisor-users@lists.__supervisord.org <mailto:[email protected]> http://lists.supervisord.org/__mailman/listinfo/supervisor-__users <http://lists.supervisord.org/mailman/listinfo/supervisor-users>
-- Mike Naberezny Maintainable Software http://maintainable.com _______________________________________________ Supervisor-users mailing list [email protected] https://lists.supervisord.org/mailman/listinfo/supervisor-users
