Then it should notice the process died quickly.

Please run Monit in debug mode and send output:

        monit -vI

Regards,
Martin


> On 23 Dec 2014, at 15:33, Russell Simpkins <[email protected]> wrote:
> 
> Hi,
> 
> I have the daemon set to 10 seconds
> 
> set daemon  10
>    with start delay 240
> 
> 
> 
> On Tue, Dec 23, 2014 at 8:57 AM, Martin Pala <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi,
> 
> 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.
> 
> Regards,
> Martin
> 
> 
>> On 23 Dec 2014, at 14:45, Russell Simpkins <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi,
>> 
>> 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/recentnews-feed.pid      
>> 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.
>> 
>> Thanks,
>> 
>> Russ
>> 
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general 
>> <https://lists.nongnu.org/mailman/listinfo/monit-general>
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general 
> <https://lists.nongnu.org/mailman/listinfo/monit-general>
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general

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

Reply via email to