From: rob.leadbeater@lynx.co.uk
Date: Mon Sep 06 2004 - 04:33:13 EDT
Hi Managers,
Thanks to the handful of people who responded, who suggested checking
various different things:
Martin Andersen:
Check in rc.config for any NTP configuration different to that in ntp.conf
Douglas Stephens:
Make sure that the upstream servers are actually version 1, and to check out
www.ntp.org
Florian Heigl:
To check the output from ntpdate -v -d time_server
All of things were useful in tracking down the issue, but the problem
appears to be that xntpd was being confused by NAT on our firewall, such
that replies weren't getting processed correctly. I set up ntpd on a
separate box which didn't need any address translation, then got the Tru64
boxes to point to this, and everything has now synchronised.
Regards,
Rob
----- Original Message -----
From: <rob.leadbeater@lynx.co.uk>
To: <tru64-unix-managers@ornl.gov>
Sent: Monday, August 23, 2004 10:05 AM
Subject: NTP Configuration
Hi Managers,
For some reason NTP doesn't appear to be working correctly for us, or
(probably) isn't configured correctly.
On a two node 5.1B memory channel cluster, I've got the following ntp.conf
files:
Node1:
server ntp0.pipex.net version 1
server ntp1.pipex.net version 1
server ntp2.pipex.net version 1
peer node2-ics0 version 3
Node2:
server ntp0.pipex.net version 1
server ntp1.pipex.net version 1
server ntp2.pipex.net version 1
peer node1-ics0 version 3
The output from ntpq -p indicates that no peer/server was selected:
ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
ntp0.pipex.net 0.0.0.0 16 u - 64 0 0.000 0.000
4000.00
ntp1.pipex.net 0.0.0.0 16 u - 64 0 0.000 0.000
4000.00
ntp2.pipex.net 0.0.0.0 16 u - 64 0 0.000 0.000
4000.00
node2-ics0 0.0.0.0 16 u 4 64 0 0.000 0.000
4000.00
however, if I query the external servers I can get the time OK:
node1 # ntpdate -q ntp0.pipex.net
server 158.43.128.33, stratum 2, offset -4.104927, delay 0.41115
23 Aug 09:41:28 ntpdate[791358]: step time server 158.43.128.33
offset -4.104927 sec
node1 # ntpdate -q ntp1.pipex.net
server 158.43.128.66, stratum 2, offset -3.999647, delay 0.20505
23 Aug 09:41:39 ntpdate[791362]: step time server 158.43.128.66
offset -3.999647 sec
node1 # ntpdate -q ntp2.pipex.net
server 158.43.192.66, stratum 2, offset -4.116835, delay 0.43454
23 Aug 09:41:47 ntpdate[791393]: step time server 158.43.192.66
offset -4.116835 sec
but querying the peer on the other node returns:
node1 # ntpdate -q node2-ics0
server 192.168.0.2, stratum 16, offset 7.979337, delay 0.02611
23 Aug 09:42:02 ntpdate[791399]: no server suitable for synchronization
found
Can someone give me some pointers as to what could be wrong...?
Cheers,
Rob
This message is intended only for the use of the person(s) ("The intended
Recipient(s)") to whom it is addressed. It may contain information which
is privileged and confidential within the meaning of applicable law. If
you are not the intended recipient, please contact the sender as soon as
possible. The views expressed in this communication are not necessarily
those held by LYNX Express Limited.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:07 EDT