Servers just doen't work (after following the troubleshooting page)



Hi!

I am setting up two ntp servers. The two servers can synchronize their time, but it won't serve. I followed the instructions in http://ntp.isc.org/bin/view/Support/TroubleshootingNTP (remove restrict, check ntp port, check ntpd status, use online tools, no dhcp, no MS Windows) but so far it doesn't help.

Any ideas?

More information below:

Both server almost identical, Red Hat 7.3, kernel 2.4.20-28.7, ntp-4.1.1-1.

[root@server1 /]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+ntp-0.gw.uiuc.e truechimer.cso.  2 -   55 1024  377   26.019    1.585   2.253
*ntp3.tamu.edu   ntp1.tamu.edu    2 -   20 1024  377   44.892    1.253   1.445
+cisco1-mhk.kans navobs1.wustl.e  2 -   57 1024  377   47.829    3.943   2.297
 ntp2.<mydomain> 0.0.0.0         16 u    -  256    0    0.000    0.000 4000.00


[root@server2 /]# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *ntp-1.gw.uiuc.e truechimer.cso. 2 u 146 1024 377 96.335 -166.48 64.986 +ntp3.tamu.edu ntp1.tamu.edu 2 u 268 1024 377 68.509 -129.28 30.480 +cisco1-mhk.kans navobs1.wustl.e 2 u 229 1024 377 44.214 -126.14 33.813 ntp1.<mydomain> 0.0.0.0 16 u - 256 0 0.000 0.000 4000.00


[root@client1 /]# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== ntp2.<mydomain> 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00 ntp1.<mydomain> 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00



ntp.conf (for both server almost identical, except for peer):
----------------------------------------------------------------
server ntp.cso.uiuc.edu
server ntp5.tamu.edu
server ntp2.kansas.net

peer ntp2

driftfile /etc/ntp/drift
broadcastdelay	0.008
keys		/etc/ntp/keys
----------------------------------------------------------------



Output from http://www.vanheusden.com/query_ntp_do.php
to the first server:
----------------------------------------------------------------
Query NTP server
Output of NTP server at <server1.ip>


ntpdate

27 Sep 01:14:43 ntpdate[30362]: ntpdate 4.1.1@xxxxx Tue Sep 23 17:37:40 UTC 2003 (1)
server <server1.ip>, stratum 3, offset 0.002290, delay 0.15057
27 Sep 01:14:43 ntpdate[30362]: adjust time server <server1.ip> offset 0.002290 sec


ntpq -c pe

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+ntp-0.gw.uiuc.e truechimer.cso.  2 -  336 1024  377   23.481   -0.668   1.236
*ntp3.tamu.edu   ntp1.tamu.edu    2 -  302 1024  377   44.479   -0.192   0.377
+cisco1-mhk.kans navobs1.wustl.e  2 -  339 1024  377   48.220    6.240   0.819
<server1.int.ip> 0.0.0.0         16 u    -  256    0    0.000    0.000 4000.00


ntpq -crv

status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg,
version="ntpd 4.1.1@xxxxx Mon Apr  8 06:30:52 EDT 2002 (1)",
processor="i686", system="Linux2.4.20-28.7", leap=00, stratum=3,
precision=-16, rootdelay=44.662, rootdispersion=53.946, peer=41541,
refid=ntp3.tamu.edu,
reftime=c6e2fe36.ad7b84db  Tue, Sep 27 2005  1:09:42.677, poll=10,
clock=c6e2ff64.b1267408  Tue, Sep 27 2005  1:14:44.691, state=4,
offset=1.017, frequency=-7.506, jitter=22.768, stability=0.106


ntpq -c ntpversion -c version

NTP version being claimed is 2
ntpq 4.1.1@xxxxx Tue Sep 23 17:38:05 UTC 2003 (1)


ntpq -c associations

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 41540  9414   yes   yes  none  candidat   reachable  1
  2 41541  9614   yes   yes  none  sys.peer   reachable  1
  3 41542  9414   yes   yes  none  candidat   reachable  1
  4 41543  8000   yes   yes  none    reject


ntptrace

<server1.ip>: stratum 3, offset 0.002685, synch distance 0.07634
ntp3.tamu.edu: stratum 2, offset 0.001913, synch distance 0.01714
ntp1.tamu.edu: 	*Timeout*
----------------------------------------------------------------


Thank you!

--
                              Stephan Paul Arif Sahari Wibowo
   _____  _____  _____  _____
  /____  /____/ /____/ /____
 _____/ /      /    / _____/       http://www.arifsaha.com/
.



Relevant Pages

  • Re: ntpd not adjusting the clock?
    ... server 2.pl.pool.ntp.org prefer ... Unless you've got additional restrict lines which permit some hosts to make changes, using only "restrict default ignore" will prevent ntpd from paying attention to the timeservers you've listed and it will even prevent ntpd from changing the local clock or being administered via ntpq from localhost. ... These client machines end up querying NTP servers in the pool.ntp.org service repeatedly at minpoll because they discard the responses given to them, and therefore constitute an abuse of NTP server resources. ...
    (freebsd-questions)
  • Re: Isolated Network Drift Problem
    ... I have 4 NTP servers running in isolation (versions ... frequency offset, clock offset, estimated error and others. ... parallel port output line to the interrupt input, timing when I sent it out ... I've changed my server ntp.conf files so that one machine is ...
    (comp.protocols.time.ntp)
  • Re: Isolated Network Drift Problem
    ... I have 4 NTP servers running in isolation (versions ... designated as a server with its undisciplined clock set at stratum 5. ... the offset in ppm from my observed seconds per day? ... getting the estimated error values so soon after being initialized. ...
    (comp.protocols.time.ntp)
  • Re: Isolated Network Drift Problem
    ... I have 4 NTP servers running in isolation (versions ... A more adequate test would be to set up a server with a GPS receiver and compare the offset of all the local clocks under test every thirty minutes over a period of several days. ... the offset in ppm from my observed seconds per day? ... getting the estimated error values so soon after being initialized. ...
    (comp.protocols.time.ntp)
  • Re: Make complains "warning: Clock skew detected." on NFS client
    ... can see the need for having two set from ntp servers. ... Well, about 100 *NFS* clients, there was a non-trivial ... number of other machines, ... the NTP server be best? ...
    (comp.unix.solaris)