HP-UX Internet Services Administrator's Guide (February 2007)

with the other system’s clock. For more information, type man 1M ntpdate at the
HP-UX prompt.
Error Messages
This section describes the error messages that you may encounter while working with
NTP.
No server suitable for synchronization found.
This message indicates that the NTP server is not responding. Packets were sent out,
but a reply was not returned. The reason may be that the server is down, or the network
link is broken or extremely congested. Or, perhaps the NTP daemon died on the server
and has not locked on to its time sources. NTP version 3.5 and above take between 5
and 15 minutes after starting up the daemon to synchronize, and it does not respond
to client requests during this time.
Last adjustment did not complete.
This message indicates that NTP is attempting to make adjustments, larger than the
system’s maximum slew rate allows, in one clock tick. Therefore, the remaining
adjustments are pushed to the next clock tick. This is handled automatically. You can
notice this message during the first hour after the NTP daemon is started. If this message
continuous to appear after a few days of steady operation, this indicates that your
system clock is drifting. This may result in loss of contact with the network time server.
Synchronization lost.
This message indicates that NTP has cleared the statistics registers, and has started
evaluating the available time servers to choose the best time server. This message
appears when a step adjustment (greater than 128 milliseconds) is done because the
step leaves the system unsynchronized by definition. If the system does many step
adjustments, it indicates a network congestion problem. To review this problem, do
the following steps:
1. Run ntpq -p
2. Examine the dispersion statistics.
Common Problems
This section covers typical problems with ntp operation.
Problem 1: No suitable server for synchronization found.
Every NTP time hierarchy must have at least one stratum-1 server configured with an
external time source, such as, an attached radio clock (Netclock/2 WWVB Synchronized
Clock) or the local system clock. If a stratum-1 server in the hierarchy does not exist,
association is not formed. To verify whether the local xntpd is able to form an
association, issue the following command:
74 Configuring NTP