RE: Monit reload stopped the daemon

[Kirubakaran Kaliannan]

 

Hi Martin,

 

We start monit externally through a script  after the resources are online. Not started by upstart or systemd.

The “monit reload” happens every 5 min approximately when the monit config files change.

 

The below SIGTERM received exactly at the same second as the “monit reload” happened.

As I am the owner of the setup, I am fairly sure that no one have run the “monit quit” on it. (not finding anything in bash history as well)

 

Since the monit got killed exactly when the “reload” happened, I was thinking there is some timing/signal issue in the code to be aware off.

 

I have done enough code analysis as well. I will report back, in case if I hit this again.

 

Thanks for your reply,

-kiru

 

From: monit-general [mailto:monit-general-bounces+kirubak=address@hidden] On Behalf Of Martin Pala
Sent: Friday, May 20, 2016 1:32 PM
To: This is the general mailing list for monit
Subject: Re: Monit reload stopped the daemon

 

Hi,

 

monit reload just sends a SIGHUP signal. The log message and monit stop comes from SIGTERM, but it must have been triggered externally, not by monit.

 

How do you start Monit? If you use for example upstart or systemd, it is possible that the SIGTERM was sent by it or manually by administrator using "monit quit" after "monit reload".

 

Regards,

Martin

 

 

 

On 17 May 2016, at 13:55, Kirubakaran Kaliannan <address@hidden> wrote:

 

 

Hi,

 

I have the following log, happened only once and not able to recreate this.  Did the following 

1.       I have stopped set of resources, 

2.       removed the corresponding config files under /etc/monit/conf.d

3.       ran monit reload

 

The step 3, somehow exited the monit daemon from running. (This exactly looked like it received SIGINT or SIGTERM, we have not explicitly killed this at this time)

This timed exactl during the reload. 

 

Any help in here is much appreciated. 

 

The snippet of the log is

……….

[IDT May 16 18:46:25] info     : 'resource1’ stop on user request

[IDT May 16 18:46:25] info     : monit daemon with PID 2549 awakened

[IDT May 16 18:46:25] info     : Awakened by User defined signal 1

[IDT May 16 18:46:25] info     : 'resource2’ stop on user request

[IDT May 16 18:46:25] info     : monit daemon with PID 2549 awakened

[IDT May 16 18:46:25] info     : 'resource3’ stop on user request

[IDT May 16 18:46:25] info     : monit daemon with PID 2549 awakened

[IDT May 16 18:46:25] info     : ‘resource4’  stop on user request

[IDT May 16 18:46:25] info     : monit daemon with PID 2549 awakened

[IDT May 16 18:46:25] info     : ‘resource1’ stop: /sbin/start-stop-daemon

[IDT May 16 18:46:25] info     : 'resource1’ stop action done

[IDT May 16 18:46:25] info     : 'resource2’ stop: /sbin/start-stop-daemon

[IDT May 16 18:46:25] info     : ‘resource2’ stop action done

[IDT May 16 18:46:25] info     : ‘resource3’  stop: /sbin/start-stop-daemon

[IDT May 16 18:46:25] info     : resource3’ stop action done

[IDT May 16 18:46:25] info     : ‘resource4’ stop: /sbin/start-stop-daemon

[IDT May 16 18:46:25] error    : ‘resource4’ failed to stop

[IDT May 16 18:46:25] info     : ‘resource4’ stop action done

[IDT May 16 18:46:25] info     : Reinitializing monit daemon

[IDT May 16 18:46:25] info     : Awakened by User defined signal 1

[IDT May 16 18:46:25] info     : Shutting down monit HTTP server

[IDT May 16 18:46:25] info     : monit HTTP server stopped

[IDT May 16 18:46:25] info     : monit daemon with pid [2549] killed ß-------------------- No clue how ?

[IDT May 16 18:46:25] info     : 'test-server -2' Monit stopped

……..

 

The monit package I am using is 

 

ii  monit                                  1:5.6-2                               amd64        utility for monitoring and managing daemons or similar programs

 

Thanks

-kiru

 

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general