[ntp:questions] Re: Correcting my time servers clock drift on Alpha ES40s / Tru64

brett.sander at tenix.com brett.sander at tenix.com
Fri Oct 21 01:14:12 UTC 2005


Dave,

The clocks on the 2 servers (as far as I can tell) are running at the
same time.  I will have to take a look into the orphan mode. If the
clock of my alpha box that I designate as the server is not great at
keeping time though, doesn't that mean my whole network will be out as
it is now?

Below are some extracts of the ntp logs:

terrance:

20 Jul 17:17:10 xntpd[764]: frequency initialized -5.490 from
/cluster/members/{memb}/etc/ntp.drift
20 Jul 17:17:10 xntpd[764]: using kernel phase-lock loop 0041
20 Jul 17:22:42 xntpd[764]: ntpd exiting on signal 15
20 Jul 17:40:44 xntpd[764]: logging to file /var/adm/ntpd.log
20 Jul 17:40:44 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
20 Jul 17:40:44 xntpd[764]: precision = 976 usec
20 Jul 17:40:44 xntpd[764]: kern_enable is 1
20 Jul 17:40:44 xntpd[764]: using kernel phase-lock loop 0040
20 Jul 17:40:44 xntpd[764]: frequency initialized -5.490 from
/cluster/members/{memb}/etc/ntp.drift
20 Jul 17:40:44 xntpd[764]: using kernel phase-lock loop 0041
22 Aug 17:21:18 xntpd[764]: ntpd exiting on signal 15
22 Aug 17:23:13 xntpd[764]: logging to file /var/adm/ntpd.log
22 Aug 17:23:13 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
22 Aug 17:23:13 xntpd[764]: precision = 976 usec
22 Aug 17:23:13 xntpd[764]: kern_enable is 1
22 Aug 17:23:13 xntpd[764]: using kernel phase-lock loop 0040
22 Aug 17:23:13 xntpd[764]: frequency initialized -5.454 from
/cluster/members/{memb}/etc/ntp.drift
22 Aug 17:23:13 xntpd[764]: using kernel phase-lock loop 0041
22 Aug 17:46:06 xntpd[764]: time reset 0.520856 s
22 Aug 17:46:06 xntpd[764]: synchronisation lost
29 Sep 16:55:38 xntpd[764]: ntpd exiting on signal 15
29 Sep 16:57:32 xntpd[764]: logging to file /var/adm/ntpd.log
29 Sep 16:57:32 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
29 Sep 16:57:32 xntpd[764]: precision = 976 usec
29 Sep 16:57:32 xntpd[764]: kern_enable is 1
29 Sep 16:57:32 xntpd[764]: using kernel phase-lock loop 0040
29 Sep 16:57:32 xntpd[764]: frequency initialized -5.491 from
/cluster/members/{memb}/etc/ntp.drift
29 Sep 16:57:32 xntpd[764]: using kernel phase-lock loop 0041
29 Sep 17:18:38 xntpd[764]: time reset -0.465399 s
29 Sep 17:18:38 xntpd[764]: synchronisation lost


phillip:

18 Jul 18:40:49 xntpd[764]: using kernel phase-lock loop 0040
18 Jul 18:40:49 xntpd[764]: frequency initialized -10.437 from
/cluster/members/{memb}/etc/ntp.drift
18 Jul 18:40:49 xntpd[764]: using kernel phase-lock loop 0041
18 Jul 19:04:55 xntpd[764]: time reset -0.800453 s
18 Jul 19:04:55 xntpd[764]: synchronisation lost
20 Jul 17:18:02 xntpd[764]: logging to file /var/adm/ntpd.log
20 Jul 17:18:02 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
20 Jul 17:18:03 xntpd[764]: precision = 976 usec
20 Jul 17:18:03 xntpd[764]: kern_enable is 1
20 Jul 17:18:03 xntpd[764]: using kernel phase-lock loop 0040
20 Jul 17:18:03 xntpd[764]: frequency initialized -10.384 from
/cluster/members/{memb}/etc/ntp.drift
20 Jul 17:18:03 xntpd[764]: using kernel phase-lock loop 0041
20 Jul 17:22:29 xntpd[764]: ntpd exiting on signal 15
20 Jul 17:41:50 xntpd[764]: logging to file /var/adm/ntpd.log
20 Jul 17:41:50 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
20 Jul 17:41:50 xntpd[764]: precision = 976 usec
20 Jul 17:41:50 xntpd[764]: kern_enable is 1
20 Jul 17:41:50 xntpd[764]: using kernel phase-lock loop 0040
20 Jul 17:41:50 xntpd[764]: frequency initialized -10.384 from
/cluster/members/{memb}/etc/ntp.drift
20 Jul 17:41:50 xntpd[764]: using kernel phase-lock loop 0041
20 Jul 18:04:47 xntpd[764]: time reset 0.556995 s
20 Jul 18:04:47 xntpd[764]: synchronisation lost
22 Aug 17:21:21 xntpd[764]: ntpd exiting on signal 15
22 Aug 17:23:12 xntpd[764]: logging to file /var/adm/ntpd.log
22 Aug 17:23:12 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
22 Aug 17:23:12 xntpd[764]: precision = 976 usec
22 Aug 17:23:12 xntpd[764]: kern_enable is 1
22 Aug 17:23:12 xntpd[764]: using kernel phase-lock loop 0040
22 Aug 17:23:12 xntpd[764]: frequency initialized -10.281 from
/cluster/members/{memb}/etc/ntp.drift
22 Aug 17:23:12 xntpd[764]: using kernel phase-lock loop 0041


Is the synchronisation lost message a normal thing?

Some more information:  I am running xntpd and according to the man
pages "The xntpd daemon is a complete implementation of the Network
Time Protocol (NTP) version 3 standard as defined by RFC 1305".  We
also have a number of Windows 2000 servers that are clients and are
configured using "net time /setsntp:time-server" where time-server is
an aliase to one of the alpha machines.




More information about the questions mailing list