Configuring the Network Time Protocol (NTP)

Troubleshooting NTP

The ntpd daemon records all problems and errors using the syslog(SLIB) system call into the file /usr/adm/syslog. You can examine this log for signs of trouble. For example, too many entries indicating that the local clock was stepped instead of slewed to the correct time suggest that the daemon is having trouble synchronizing the clock. (In this instance, more than two entries per hour on a consistent basis is probably too many.) The most likely cause is that some other program, perhaps timed, is also setting or slewing the clock.

Another sign of more than one entity setting or slewing the clock is the following message in the syslog file:

   Previous time adjustment did not complete
One of the following messages is issued when the clock of another host (the remote clock) is off by more than 1000 seconds from the clock on the local host (the local clock):
   Clock appears to be number_of_seconds seconds fast,
   something may be wrong
   Clock appears to be number_of_seconds seconds slow,
   something may be wrong
In this situation, ntpd will not try to synchronize with that host. If you want to synchronize with that host, you will need to set the local clock to within 1000 seconds of the remote clock. You can accomplish this by using the ntpdate(ADMN) command.
Next topic: Running mixed synchronization subnets
Previous topic: Further examples of NTP

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003