|
From: | Spencer, Mike |
Subject: | Monit daemon starting child monit process |
Date: | Fri, 13 Feb 2015 15:49:41 +0000 |
I’ve recently upgraded monit from version 5.1.1 to to 5.4 and now I sometimes see two instances of the monit daemon running. The second instance was started by the first: $ ps -eaf | fgrep monit UID PID PPID C STIME TTY TIME CMD s_gr 6389 1 0 Feb07 ? 00:12:25 monit/5.4/bin/monit -c control_file -p pid_file -s state_file s_gr 13919 6389 0 00:30 ? 00:00:00 monit/5.4/bin/monit -c control_file -p pid_file -s state_file At the time the second instance started, 00:30, we are starting several services using the ‘monit start’ command (using a named group).
Is there circumstance in which monit will start a child process of itself? Could this be a bug in version 5.4? Never had this problem with 5.1.1. Is it best to upgrade to the latest version? Thanks a lot. Mike CONFIDENTIALITY AND SECURITY NOTICE The contents of this message and any attachments may be confidential and proprietary. If you are not an intended recipient, please inform the sender of the transmission error and delete this message immediately without reading, distributing or copying the contents. |
[Prev in Thread] | Current Thread | [Next in Thread] |