Is ntpd working?

lhill · 08-28-2003, 08:19 PM

I have been trying to get ntpd up and running. It looks like it is running, but there are no log updates. On a couple of occasions, I have seen it make log updates for a few hours, but then it stops updating. Any suggestions on how to fix this would be greatly appreciated.

Output from ps:
ntp 24859 0.0 0.3 1880 1872 ? SL 19:31 0:00 ntpd -U ntp -l /v

ntp log:

28 Aug 19:31:38 ntpd[24859]: logging to file /var/log/ntp/ntp.log
28 Aug 19:31:38 ntpd[24859]: ntpd 4.1.1@1.786 Mon Apr 8 06:30:52 EDT 2002 (1)
28 Aug 19:31:38 ntpd[24859]: signal_no_reset: signal 13 had flags 4000000
28 Aug 19:31:38 ntpd[24859]: precision = 24 usec
28 Aug 19:31:38 ntpd[24859]: kernel time discipline status 0040
28 Aug 19:31:38 ntpd[24859]: frequency initialized 44.933 from /etc/ntp/drift
28 Aug 19:31:38 ntpd[24859]: running as uid(38)/gid(38) euid(38)/egid(38).
28 Aug 19:31:38 ntpd[24862]: signal_no_reset: signal 17 had flags 4000000
28 Aug 19:34:53 ntpd[24859]: kernel time discipline status change 41

lhill · 08-29-2003, 12:22 PM

Here is a copy of the ntp.conf file:

restrict default ignore
restrict 127.0.0.1

restrict X.X.X.X mask 255.255.255.255 nomodify notrap noquery
server X.X.X.X
restrict X.X.X.Xmask 255.255.255.255 nomodify notrap noquery
server X.X.X.X
#etc....

driftfile /etc/ntp/drift
broadcastdelay 0.008

and associations listed from ntpq:
ind assID status conf reach auth condition last_event cnt
===========================================================
1 11788 9414 yes yes none candidat reachable 1
2 11789 9314 yes yes none outlyer reachable 1
3 11790 9414 yes yes none candidat reachable 1
4 11791 9314 yes yes none outlyer reachable 1
5 11792 9614 yes yes none sys.peer reachable 1

Does "reachable" mean that ntp is working, or that the configuration is correct and something else is causing the logging problems?

ranger_nemo · 08-29-2003, 02:36 PM

You can run a "ntpq -p" as root to see if it's keep track of the servers you listed in ntp.conf. Here's my output...

Code:

root]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*time.nist.gov   .ACTS.           1 u  494 1024  377   64.444   -8.698  26.086
-caesar.cs.wisc. ben.cs.wisc.edu  2 u  576 1024  377   35.040  -10.853   4.443
+dr-zaius.cs.wis ben.cs.wisc.edu  2 u  593 1024  377   39.323   -8.782   1.555
-ns.nts.umn.edu  ippm-surveyor.n  2 u  719 1024  377   77.958   12.135  12.859
+nss.nts.umn.edu ippm-surveyor.n  2 u  488 1024  377   45.881   -7.065   5.179

"remote" is the ntp-server you are trying to reach.

"refid" is where the ntp-server is getting it's time.

"st" is the stratum... What level it is in the ntp system. 1 is top...

"t" is type.

"when" is when it was last checked (polled) in seconds.

"poll" is polling interval in seconds.

"reach" is reachability register, in octal. I dunno.

"offset" is how many seconds your clock is different.

The character in front of the ntp-server is a reference to how it is being used...

space is discarded for any of a few reasons.

* is used for synchronization.

+ is included in the final selection. It could be used if the * is lost.

- is discarded by the clustering algorithm.

lhill · 08-30-2003, 12:29 PM

Thanks for the info Nemo. I had found a reference to ntpq peers and this gave me the print out you mentioned. I guess that means that the server is working, just not writing anything to the log file.

Is this lack of log info normal?

ranger_nemo · 08-31-2003, 12:10 PM

I took a look at my log, and it seems to pretty much be only when it loses/regains contact with the servers... Which seems to happen quite a bit on my cable service.