[Top][All Lists]

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

Re: Monit uptime oddity

From: Martin Pala
Subject: Re: Monit uptime oddity
Date: Sat, 18 Nov 2006 00:00:33 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060809 Debian/1.7.13-0.3

Monit deduces the uptime from the timestamp of the process pidfile - the newer of mtime (Modify) or ctime (Change) values is used.

You can check the timestamps using the 'stat' utility (/usr/bin/stat).

Something is probably changing the mtime or ctime of the pidfiles (for example some backup management applications uses ctime to mark the file).


Joey Geiger wrote:
I'm running monit 4.8.2 on 3 different servers with the the same configuration file on each server. It's watching apache, memcached and nginx. It also will restart a group of mongrel servers running my rails application.

When I view the webserver information, the apache, memcached and nginx all report the proper uptime information on all servers. On ned (information below) the monit and mongrel processes also report the correct uptime. On rod and todd, the monit uptime will reset to 0min about every 4 minutes and at the same time will reset the uptime for all of the mongrel processes. Neither the monit or mongrel process has changed pids or the date/time on the pid files. This same oddness was happening on 4.8.1 as well before I updated yesterday. I was wondering if anyone has seen this before and has a possible solution. If you need any further information, please let me know. Thank you.

Linux ned 2.4.21 #1 SMP Fri Aug 8 09:18:02 CDT 2003 i686 GNU/Linux

Uptime resets:
Linux rod 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux
Linux todd 2.6.12-1-686-smp #1 SMP Tue Sep 27 13:10:31 JST 2005 i686 GNU/Linux

To unsubscribe:

reply via email to

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