[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Monit stopped noticing a pid died

From: Martin Pala
Subject: Re: Monit stopped noticing a pid died
Date: Tue, 23 Dec 2014 14:57:40 +0100


what's the poll cycle settings? ("set daemon <seconds>" statement)

Monit performs the checks and then sleep for given number of seconds. If you poll cycle is long, Monit will not notice the process died until next cycle.


On 23 Dec 2014, at 14:45, Russell Simpkins <address@hidden> wrote:


I have a check on a process via a pid file that monit reported as up, when the pid was dead and I was wondering if there were any good tips for figuring out why. We're running monit 5.9. When I run a status, I can see my process listed as running and monitored:

  Process 'recentnews-feed'
    status                            Running
    monitoring status                 Monitored
    pid                               9680
    parent pid                        1
    uid                               5005
    effective uid                     5005
    gid                               5006
    uptime                            1d 3h 20m 
    children                          0
    memory kilobytes                  1805064
    memory kilobytes total            1805064
    memory percent                    25.7%
    memory percent total              25.7%
    cpu percent                       0.1%
    cpu percent total                 0.1%
    data collected                    Fri, 19 Dec 2014 04:14:04

When I check to see if the pid is actually running, it's not there:

  $ ps -ef | grep -i 9680
  root     24520 24029  0 06:39 pts/0    00:00:00 grep -i 9680

My monit config:

check process recentnews-feed with pidfile /var/run/      start program = "/sbin/service recentnews-feed start"
  stop program = "/sbin/service recentnews-feed stop"
  if 50 restarts within 50 cycles then timeout

Again, just curious if this is a known issue in 5.9 or how to figure out why monit thought the pid was up when it was not.



To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]