I think it was sufficient to unmonitor and monitor the service which
resets the error flag, like this:
monit unmonitor <servicename>
monit monitor <servicename>
Martin
On Sep 17, 2009, at 8:26 AM, Serge Emantayev wrote:
Hi Martin
Yes, I checked the PID file and it contains the correct process ID.
Unfortunately we cannot upgrade to 5.0.3 due to license limitations.
Have you any workaround to reset error flag?
Sergey
--- On Wed, 9/16/09, Martin Pala <[email protected]> wrote:
From: Martin Pala <[email protected]>
Subject: Re: [monit] Monit shows wrong process status
To: "This is the general mailing list for monit" <[email protected]
>
Date: Wednesday, September 16, 2009, 11:32 PM
Does the service's pidfile contain correct PID of the running process?
There were some issues where the error flag was not reset under some
circumstances in the past - the latest version is Monit 5.0.3 and
there are no known issues.
Martin
On Sep 16, 2009, at 2:25 PM, Serge Emantayev wrote:
Hi
I noticed that sometimes monit displays a wrong process status (Does
not exist) although the process is running. It happens after the
process was crashed. If monit is getting reloaded in the same second
when it detects the process failure and restarts it, the process
status is likely remaining wrong.
I have monit version 4.9 for Linux. Is this a known issue? Any
workaround or patch?
Thank you
Sergey Emantayev
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
-----Inline Attachment Follows-----
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
