I have an NTP test running against a server. The ntpdate command that Hobbit issues comes back with this:
hobbit1:/etc # ntpdate -u -q -p 2 172.17.1.242 server 172.17.1.242, stratum 16, offset 0.150246, delay 0.02640 13 Sep 08:07:54 ntpdate[1055]: no server suitable for synchronization found
Which turns the icon red. BB used xntpc against the same machine, which works. I'm not familiar with ntpdate, what would be causing it to fail?
Thanks.
Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006
The "stratum 16" would seem to indicate that your NTP server is not properly syncing with a higher ranking (lower stratum) server. As a result ntpdate views this server as unsuitable for getting time from. The ntpd process is still responding, which is why bb would pass the test, but there's still something wrong with the configuration. Start with checking the NTP communication between your NTP server and the server it is getting time from.
Al
Rich Smrcina wrote:
I have an NTP test running against a server. The ntpdate command that Hobbit issues comes back with this:
hobbit1:/etc # ntpdate -u -q -p 2 172.17.1.242 server 172.17.1.242, stratum 16, offset 0.150246, delay 0.02640 13 Sep 08:07:54 ntpdate[1055]: no server suitable for synchronization found
Which turns the icon red. BB used xntpc against the same machine, which works. I'm not familiar with ntpdate, what would be causing it to fail?
Thanks.
OK, thanks.
Al Payne wrote:
The "stratum 16" would seem to indicate that your NTP server is not properly syncing with a higher ranking (lower stratum) server. As a result ntpdate views this server as unsuitable for getting time from. The ntpd process is still responding, which is why bb would pass the test, but there's still something wrong with the configuration. Start with checking the NTP communication between your NTP server and the server it is getting time from.
Al
Rich Smrcina wrote:
I have an NTP test running against a server. The ntpdate command that Hobbit issues comes back with this:
hobbit1:/etc # ntpdate -u -q -p 2 172.17.1.242 server 172.17.1.242, stratum 16, offset 0.150246, delay 0.02640 13 Sep 08:07:54 ntpdate[1055]: no server suitable for synchronization found
Which turns the icon red. BB used xntpc against the same machine, which works. I'm not familiar with ntpdate, what would be causing it to fail?
Thanks.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006
On Tue, 2005-09-13 at 11:39 -0400, Al Payne wrote:
The "stratum 16" would seem to indicate that your NTP server is not properly syncing with a higher ranking (lower stratum) server. As a result ntpdate views this server as unsuitable for getting time from. The ntpd process is still responding, which is why bb would pass the test, but there's still something wrong with the configuration. Start with checking the NTP communication between your NTP server and the server it is getting time from.
If you are using authenticated ntp, ntpdate probably won't work without some additional command-line options, where xntpdc knows about keys more automatically
-- Daniel J McDonald, CCIE # 2495, CNX, CISSP # 78281 Austin Energy
dan.mcdonald at austinenergy.com
participants (3)
-
apayne＠pleiades.com
-
dan.mcdonald＠austinenergy.com
-
rsmrcina＠wi.rr.com