Hi, please can you add the configuration of "foo" and "bar" services?
There are for example these possible reasons: 1.) the "bar" service is a process and monit detected that the process is not running - in this case it gets a fast path and stop is skipped (the process is not running) 2.) there was a problem if you used "check program" in combination with the "every" statement ... fixed in monit 5.25.3: https://bitbucket.org/tildeslash/monit/issues/759 Best regards, Martin > On 5 Mar 2019, at 16:24, Marc Rossi <mross...@gmail.com> wrote: > > Looking through source right now but figured I'd throw it out to list to see > if this is something obvious I'm doing wrong. > > Long time monit user but on a few of our apps we have recently been having > problems with the shutdown action possibly not running. > > For the app that DOES shut down properly logs show the following: > > [CST Mar 4 17:00:02] info : 'foo' stop on user request > [CST Mar 4 17:00:02] info : Monit daemon with PID 17733 awakened > [CST Mar 4 17:00:02] info : Awakened by User defined signal 1 > [CST Mar 4 17:00:02] info : 'foo' stop: '/usr/bin/pkill -u nobody -f > /usr/local/bin/foo.py' > [CST Mar 4 17:00:02] info : 'foo' stop action done > > For the app that is not stopping properly logs show the following: > > [CST Mar 4 15:15:01] info : 'bar' stop on user request > [CST Mar 4 15:15:01] info : Monit daemon with PID 17733 awakened > [CST Mar 4 15:15:01] info : Awakened by User defined signal 1 > [CST Mar 4 15:15:01] info : 'bar' stop action done > > Could be a red herring but where is the stop action line in the second log > excerpt? Now the shutdown commands are indeed different between foo & bar but > still would expect to see the stop action listed. > > TIA > Marc > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
