|Subject:||Re: checking ntpd|
|Date:||Sun, 17 Apr 2011 11:49:22 +0200|
please can you send the monit log? It will show the reason why ntpd was restarted - whether the process died or the protocol test failed.
The reason for repeated restarts could be the ntpd behavior when the time difference is large (which may happen if the system was booted and time was not set) - if the ntpd is started and the time difference is bigger then 1000s, then ntpd usually exits - if monit is set to restart it, the ntpd will be started again, but will also exit again. In such case it is necessary to step the time for example using ntpdate.
It will be better to modify the configuration this way:
check process date-time with pidfile /var/run/ntpd.pid
start program = "/bin/bash -c '/usr/sbin/ntpdate -s pool.ntp.org && /sbin/service ntpd start'"
stop program = "/sbin/service ntpd stop"
if failed host 127.0.0.1 port 123 type udp protocol ntp3 for 2 times within 3 cycles then restart
if 2 restarts within 3 cycles then timeout
check host ntp_peer with address pool.ntp.org
if failed port 123 type udp protocol ntp3 for 2 times within 3 cycles then alert
=> the start program is modified to set the time using ntpdate before ntpd is started.
The "protocol ntp3" is added - this is highly recommended especially for the UDP tests because of the connection-less nature of UDP. It allows to speedup the test because monit knows what the server should return - generic UDP test (without protocol specification) is tricky, as the only way to check that the packet arrived to the destination is, that no network error was indicated by ICMP.
On Apr 16, 2011, at 8:21 PM, Mike Schmidt wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|