Today, I discovered the following for the ntp-test on our Xymon server:
Service ntp on xymon is OK (up)
Command: ntpdate -u -q -p 2 132.229.84.242 2>&1
!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!The ntpdate program is deprecated and should not be used any more. To
quote the upstream ntp developers:
"The functionality ntpdate offered is now provided by the ntpd daemon itself. If you call ntpd with the command line option -q it will retrieve the current time and set it accordingly."
Please check the Network Time Protocol (NTP) daemon man page and http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate for further information.
You can replace the ntpdate call with "rcntp ntptimeset" to achieve an inital poll of the servers specified in /etc/ntp.conf.
The program /usr/sbin/sntp offers comparable functionality to ntpdate.
Specifically sntp -P no -r pool.ntp.org is equivalent to ntpdate pool.ntp.org
For further details please refer to the man page of sntp.
sntp: unable to write PID to /etc/sntp.pid sntp: Permission denied
http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate#Set_the_time_before_r...
I always thought I needed to run this ntp-test to make sure the time is correct on the central monitor server, to make sure that the time on other monitored hosts is checked correctly.
Should I
change the NTPDATE="ntpdate"-location in /etc/hobbit/hobbitserver.cfg to NTPDATE="sntp -u" to make it work again?
disable the ntp-test since because it is useless for checking the correct time on monitored hosts.
Regards, Peter