[ntp:questions] Help : NTP System clock suddendly freeze

Junice sssia at cyberway.com.sg
Wed Aug 13 19:50:06 UTC 2003


Hi,
	Anyone know what is the cause for the NTP server clock to suddendly
stop this morning at 8.30am ? When I do a while do loop every 1
second, I get the following :

Tue Aug 12 08:30:14 SGT 2003
Tue Aug 12 08:30:12 SGT 2003
Tue Aug 12 08:30:13 SGT 2003
Tue Aug 12 08:30:14 SGT 2003
Tue Aug 12 08:30:12 SGT 2003
Tue Aug 12 08:30:13 SGT 2003
Tue Aug 12 08:30:14 SGT 2003
Tue Aug 12 08:30:12 SGT 2003
Tue Aug 12 08:30:13 SGT 2003
	After restarting the xntpd, the system time sync forward to the
correct afternoon time and the system clock run correctly.

	This NTP server 172.100.0.10 has been running for half a year and it
was only recently that the system clock stop as described above. I
have another NTP server 172.100.0.11 which sync to the same Stratum 2
server 192.168.0.1 does not has this problem. Both 172.100.0.10 and
172.100.0.11 are running NTP ver 3-5.93e on SUN solaris 2.8.
	
	Below are the configuration and the association, pe , showpeer,
loopinfo command which I have captured before I restart the xnptd this
morning.
	
	
The configuration for 172.100.0.10 and 172.100.0.11 are the same as
shown below:
/etc/inet/ntp.conf
server 192.168.0.1 prefer
server 192.168.0.2 
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
slewalways yes
disable pll



ntpq>ass
ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 51828  9624   yes   yes  none  sys.peer   reachable  2
  2 51829  8000   yes    no

ntpq>pe
     remote           refid      st t when poll reach   delay   offset
   disp
==============================================================================
*192.168.0.1  192.250.14.16     2 u  794 1024  377     5.39    0.810  
 1.28
 192.168.0.2    0.0.0.0         16 -    - 1024    0     0.00    0.000
16000.0

#xntpdc -c "showpeer 192.168.0.1"
remote 192.168.0.1, local 172.100.0.10
hmode client, pmode unspec, stratum 2, precision -18
leap 00, refid [192.250.14.16], rootdistance 0.02055, rootdispersion
0.00061
ppoll 10, hpoll 10, keyid 0, version 3, association 51828
valid 8, reach 377, unreach 0, flash 000, boffset 0.00391, ttl/mode 0
timer 218s, flags system_peer, config, bclient, prefer
reference time:      c2e2ad5c.bfac977a  Tue, Aug 12 2003  8:03:40.748
originate timestamp: c2e2b07a.e99a2654  Tue, Aug 12 2003  8:16:58.912
receive timestamp:   c2e2b07a.ea15c000  Tue, Aug 12 2003  8:16:58.914
transmit timestamp:  c2e2b07a.e8b1a000  Tue, Aug 12 2003  8:16:58.908
filter delay:  0.00539  0.00397  0.00385  0.00838 
               0.00542  0.00720  0.00571  0.00394 
filter offset: 0.000810 -0.00034 -0.00106 0.000787
               -0.00092 -0.00024 -0.00104 -0.00275
filter order:  0        1        2        3       
               4        5        6        7       
offset 0.000810, delay 0.00539, dispersion 0.00128, selectdisp 0.00000

#xntpdc -c loopinfo
offset:               0.000810 s
frequency:            3.301 ppm
poll adjust:          30
watchdog timer:       806 s

Thankyou
Junice



More information about the questions mailing list