Janusz Krzysztofik said: > Package: monit > Version: 1:4.5-1 > Severity: normal > Tags: patch > > > I use monit to monitor a pool of my real ntp servers in an lvs cluster. >>From time to time a server or two start answering with leap indicator set >> to +1. > Monit counts this as an error and, using my config file settings, > removes the server from the lvs pool. > I can check the server by other means (ntpdate, ntpdc) and see it is ok > and still can serve clients. > > If my understanding of ntp leap indicator meaning and usage is correct, > fully functional ntp servers can set leap indicator bits to 01 or 10, > and more, this warning is propagated downstream, so every ntp server > synchronized to a pool.ntp.org, for example, can and will be affected > form time to time.
I have no experience from NTP, but it seems reasonable not to warn for non-faulty events. I forward your report to upstream, which is usually very responsive so if the patch has merit, it will probably be included in the next upstream version, and hence in the following debian packaging. Thanks, Stefan > > Included patch limits error condition to 11, that I believe means > "not synchronized". (patch not forwarded but is included in the debian BTS, http://bugs.debian.org/352065 or http://bugs.debian.org/cgi-bin/bugreport.cgi/monit-4.5-ntp3.patch?bug=352065;msg=5;att=1 )
