[ntp:questions] Re: load balancer
Richard B. Gilbert
rgilbert88 at comcast.net
Fri Oct 6 02:47:35 UTC 2006
Julie S. Lin wrote:
> Hi
>
> i'm having problems configuring ntp on my network
> i have 3 servers behaind a bigip running ntp, and
> they are unable to sync with my stratum 1 clock of choice.
> my other servers on another network are syncing beautifully.
>
> has anyone run into this problem and can give me advice on how
> to enable this syncing? i understand this is a networking issue
> but figure I'd make sure there's no ntp specific considerations. thanks
>
> the request looks like this
>
> [root]# /usr/sbin/ntpdate -d time-a.timefreq.bldrdoc.gov
> 4 Oct 14:57:28 ntpdate[23994]: ntpdate 4.1.2 at 1.892 Tue Feb 24 06:32:26
> EST 2004 (1)
> transmit(132.163.4.103)
> transmit(132.163.4.103)
> transmit(132.163.4.103)
> transmit(132.163.4.103)
> transmit(132.163.4.103)
> 132.163.4.103: Server dropped: no data
> server 132.163.4.103, port 123
> stratum 0, precision 0, leap 00, trust 000
> refid [0.0.0.0], delay 0.00000, dispersion 64.00000
> transmitted 4, in filter 4
> reference time: 00000000.00000000 Wed, Feb 6 2036 22:28:16.000
> originate timestamp: 00000000.00000000 Wed, Feb 6 2036 22:28:16.000
> transmit timestamp: c8ceaccb.e10df15a Wed, Oct 4 2006 14:57:31.879
> filter delay: 0.00000 0.00000 0.00000 0.00000
> 0.00000 0.00000 0.00000 0.00000
> filter offset: 0.000000 0.000000 0.000000 0.000000
> 0.000000 0.000000 0.000000 0.000000
> delay 0.00000, dispersion 64.00000
> offset 0.000000
>
> 4 Oct 14:57:32 ntpdate[23994]: no server suitable for synchronization found
>
>
>
> J
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
>
An almost identical command worked for me! Because ntpd is already
running I must use an unprivileged port instead of port 123.
sunblok_$ /usr/sbin/ntpdate -du time-a.timefreq.bldrdoc.gov
5 Oct 22:30:49 ntpdate[22333]: ntpdate 3-5.93e Mon Sep 20 15:45:30 PDT
1999 (1)
transmit(132.163.4.101)
receive(132.163.4.101)
transmit(132.163.4.101)
receive(132.163.4.101)
transmit(132.163.4.101)
receive(132.163.4.101)
transmit(132.163.4.101)
receive(132.163.4.101)
transmit(132.163.4.101)
server 132.163.4.101, port 123
stratum 1, precision -18, leap 00, trust 000
refid [ACTS], delay 0.12851, dispersion 0.00014
transmitted 4, in filter 4
reference time: c8d03e1e.ff2ecf20 Thu, Oct 5 2006 22:29:50.996
originate timestamp: c8d03e5a.97ebaf10 Thu, Oct 5 2006 22:30:50.593
transmit timestamp: c8d03e5a.8a008000 Thu, Oct 5 2006 22:30:50.539
filter delay: 0.12984 0.12871 0.12851 0.12892
0.00000 0.00000 0.00000 0.00000
filter offset: 0.003398 0.002714 0.002819 0.002695
0.000000 0.000000 0.000000 0.000000
delay 0.12851, dispersion 0.00014
offset 0.002819
5 Oct 22:30:50 ntpdate[22333]: adjust time server 132.163.4.101 offset
0.002819 sec
If your ntpd or xntpd is running, add the "-u" to to your command line.
It is perhaps worth noting that ntpdate is "deprecated" and you should
really be using something else to "synchronize your clock". Ntpdate
does still have its uses and will probably be around in some form for
the next fifty or one hundred years but (some of) the people responsible
for it wish it would go away.
To set your clock when starting the current version of ntpd (not xntpd)
you can use the -g option to have ntpd set the clock on a one time basis
when it starts. This replaces one of the major functions formerly
performed by ntpdate; setting the clock as part of starting (x)ntpd.
If (x)ntpd is not running, then you have a network problem that is
making it impossible to contact the server. Try pinging the server. If
that doesn't work you could try traceroute and you should definitely
talk to your network people to see if a firewall is blocking the connection.
More information about the questions
mailing list