from Alice’s Adventures in Wonderland, Lewis Carroll Caterpillar knows all the error codes, which is more than most of us do. |
1. Related Links
2. Table of Contents
3. Introduction
This page lists the status words, event messages and error codes used
for ntpd
reporting and monitoring. Status words are used to display
the current status of the running program. There is one system status
word and a peer status word for each association. There is a clock
status word for each association that supports a reference clock. There
is a flash code for each association which shows errors found in the
last packet received (pkt) and during protocol processing (peer). These
are commonly viewed using the ntpq
program.
Significant changes in program state are reported as events. There is
one set of system events and a set of peer events for each association.
In addition, there is a set of clock events for each association that
supports a reference clock. Events are normally reported to the
protostats
monitoring file and optionally to the system log.
In the following tables the Event Field is the status or event code assigned and the Message Field a short string used for display and event reporting. The Description field contains a longer explanation of the status or event. Some messages include additional information useful for error diagnosis and performance assessment.
4. System Status Word
The system status word consists of four fields LI (0-1), Source (2-7),
Count (8-11) and Event (12-15). It is reported in the first line of the
rv
display produced by the ntpq
program.
Leap |
Source |
Count |
Event |
The Leap Field displays the system leap indicator bits coded as follows:
Code |
Message |
Description |
|
|
normal synchronized state |
|
|
insert second after 23:59:59 of the current day |
|
|
delete second 23:59:59 of the current day |
|
|
never synchronized |
The Source Field displays the current synchronization source coded as follows:
Code |
Message |
Description |
|
|
not yet synchronized |
|
|
pulse-per-second signal (Cs, Ru, GPS, etc.) |
|
|
VLF/LF radio (WWVB, DCF77, etc.) |
|
|
MF/HF radio (WWV, etc.) |
|
|
VHF/UHF radio/satellite (GPS, Galileo, etc.) |
|
|
local timecode (IRIG, LOCAL driver, etc.) |
|
|
NTP |
|
|
other (IEEE 1588, openntp, chrony, etc.) |
|
|
eyeball and wristwatch |
|
|
telephone modem (ACTS, PTB, etc.) |
The Count Field displays the number of events since the last time the code changed. Upon reaching 15, subsequent events with the same code are ignored.
The Event Field displays the most recent event message coded as follows:
Code |
Message |
Description |
|
|
unspecified |
|
|
frequency file not available |
|
|
frequency set from frequency file |
|
|
spike detected |
|
|
initial frequency training mode |
|
|
clock synchronized |
|
|
program restart |
|
|
clock error more than 600 s |
|
|
no system peer |
|
|
leap second armed |
|
|
leap second disarmed |
|
|
leap event |
|
|
clock stepped |
|
|
kernel information message |
|
|
leapsecond values update from file |
|
|
new NIST leapseconds file needed |
5. Peer Status Word
The peer status word consists of four fields: Status (0-4), Select
(5-7), Count (8-11) and Code (12-15). It is reported in the first line
of the rv associd
display produced by the ntpq
program.
Status |
Select |
Count |
Code |
The Status Field displays the peer status code bits in hexadecimal; each bit is an independent flag. (Note this field is 5 bits wide, and combines with the 3-bit-wide Select Field to create the first full byte of the peer status word.) The meaning of each bit in the Status Field is listed in the following table:
Code |
Message |
Description |
|
|
broadcast association (not implemented in NTPsec) |
|
|
host reachable |
|
|
authentication ok |
|
|
authentication enabled |
|
|
persistent association |
The Select Field displays the current selection status. (The T Field in
the following table gives the corresponding tally codes used in the
ntpq peers
display.) The values are coded as follows:
Code |
Message |
T |
Description |
|
|
discarded as not valid (BOGON10-BOGON13) |
|
|
|
|
discarded by intersection algorithm |
|
|
|
discarded by table overflow (not used) |
|
|
|
discarded by the cluster algorithm |
|
|
|
included by the combine algorithm |
|
|
|
backup (more than |
|
|
|
system peer |
|
|
|
PPS peer (when the prefer peer is valid) |
The Count Field displays the number of events since the last time the code changed. Upon reaching 15, subsequent events with the same code are ignored.
The Event Field displays the most recent event message coded as follows:
Code |
Message |
Description |
|
|
association mobilized |
|
|
association demobilized |
|
|
server unreachable |
|
|
server reachable |
|
|
association restart |
|
|
no server found |
|
|
rate exceeded (kiss code |
|
|
access denied (kiss code |
|
|
leap armed from server LI code |
|
|
become system peer |
|
|
see clock status word |
|
|
authentication failure |
|
|
popcorn spike suppressor |
6. Clock Status Word
The clock status word consists of four fields: Unused (0-7), Count
(8-11) and Code (12-15). It is reported in the first line of the
clockvar associd
display produced by the ntpq
program.
Unused |
Count |
Code |
The Count Field displays the number of events since the last clockvar
command, while the Event Field displays the most recent event message
coded as follows:
Code |
Message |
Description |
|
|
nominal |
|
|
no reply to poll |
|
|
bad timecode format |
|
|
hardware or software fault |
|
|
signal loss |
|
|
bad date format |
|
|
bad time format |
When the clock driver sets the code to a new value, a clock_alarm
(11)
peer event is reported.
7. Flash Status Word
The flash status word is displayed by the ntpq
program rv
command.
It consists of a number of bits coded in hexadecimal as follows:
Code |
Tag |
Message |
Description |
|
BOGON1 |
|
duplicate packet |
|
BOGON2 |
|
bogus packet |
|
BOGON3 |
|
server not synchronized |
|
BOGON4 |
|
access denied |
|
BOGON5 |
|
authentication failure |
|
BOGON6 |
|
invalid leap or stratum |
|
BOGON7 |
|
header distance exceeded |
|
BOGON10 |
|
invalid header or stratum |
|
BOGON11 |
|
distance threshold exceeded |
|
BOGON12 |
|
synchronization loop |
|
BOGON13 |
|
unreachable or nonselect |
|
BOGON14 |
|
response took too long |
The "Tag" field is the name the source code uses for the status bit. Not all bits are in use, but have been kept for backwards compatibility.
8. Refid codes
Refid codes are used in kiss-o'-death (KoD) packets, the reference
identifier field in ntpq
and ntpmon
billboard displays and log
messages. They consist of a string of four zero-padded ASCII
characters. In practice they are informal and tend to change with time
and implementation. Following is the current list:
Code |
Description |
|
access denied by server |
|
association initialized |
|
rate exceeded |
|
association timeout |
|
step time change |
|
Waiting for DNS lookup |
|
DNS lookup succeeded, no NTP response yet |
|
Waiting for NTS key exchange |
|
NTS-KE succeeded, no NTP response yet |
The 4
or 6
in the 4th position indicates that the DNS
or NTS-KE
resulted in an IPv4
or IPv6
address.