The log can be shrill at times.
Last update: 10-Mar-2014 05:12 UTC
You have come here because you found a cryptic message in the system log. This page by no means lists all messages that might be found, since new ones come and old ones go. Generally, however, the most common ones will be found here. They are listed by program module and log severity code in bold:
Most of the time
LOG_ERR messages are fatal, but often
ntpd limps onward in the hopes of discovering more errors. The
LOG_NOTICE messages usually mean the time has changed or some other condition that probably should be noticed. The
LOG_INFO messages usually say something about the system operations, but do not affect the time.
In the following a
? character stands for text in the message. The meaning should be clear from context.
buffer overflow ?
no reply; clock not set
ntpdatemode no servers have been found. The server(s) and/or network may be down. Standard debugging procedures apply.
proto_config: illegal item ?, value ?
Program error. Bugs can be reported here.
receive: autokey requires two-way communication
Configuration error on the
receive: server server maximum rate exceeded
A kiss-o’death packet has been received. The transmit rate is automatically reduced.
pps sync enabled
The PPS signal has been detected and enabled.
transmit: encryption key ? not found
The encryption key is not defined or not trusted.
precision = ? usec
This reports the precision measured for this machine.
using 10ms tick adjustments
Gotcha for some machines with dirty rotten clock hardware.
no servers reachable
The system clock is running on internal batteries. The server(s) and/or network may be down.
time correction of ? seconds exceeds sanity limit (?); set clock manually to the correct UTC time.
Fatal error. Better do what it says, then restart the daemon. Be advised NTP and Unix know nothing about local time zones. The clock must be set to Coordinated Universal Time (UTC). Believe it; by international agreement abbreviations are in French and descriptions are in English.
sigaction() fails to save SIGSYS trap: ?
sigaction() fails to restore SIGSYS trap: ?
frequency error ? exceeds tolerance 500 PPM
time slew ? s
time reset ? s
ntpd -xoption and wait forever.
kernel time sync disabled ?
pps sync disabled
kernel time sync status ?
Usually fatal errors. These messages display error codes returned from the OpenSSL library. See the OpenSSL documentation for explanation.
crypto_setup: certificate ? is trusted, but not self signed.
crypto_setup: certificate ? not for this host
crypto_setup: certificate file ? not found or corrupt
crypto_setup: host key file ? not found or corrupt
crypto_setup: host key is not RSA key type
crypto_setup: random seed file ? not found
crypto_setup: random seed file not specified
Fatal errors. These messages show problems during the initialization procedure.
cert_parse: expired ?
cert_parse: invalid issuer ?
cert_parse: invalid signature ?
cert_parse: invalid subject ?
ntp-keygenprogram. If it is held somewhere else, it must be fixed by the holder.
crypto_?: defective key
crypto_?: invalid filestamp
crypto_?: missing challenge
crypto_?: scheme unavailable
There is a problem with the identity scheme. Operation cannot proceed until the problem is fixed. Usually errors are due to misconfiguration or an orphan association. If the latter,
ntpd will usually time out and recover by itself.
crypto_cert: wrong PEM type ?
The certificate does not have MIME type
CERTIFICATE. You are probably using the wrong type from OpenSSL or an external certificate authority.
crypto_ident: no compatible identity scheme found
Configuration error. The server and client identity schemes are incompatible.
crypto_tai: kernel TAI update failed
The kernel does not support this function. You may need a new kernel or patch.
crypto_tai: leapseconds file ? error ?
The leapseconds file is corrupt. Obtain the latest file from NIST.
Was this page helpful?
Glad to hear it!
Sorry to hear that.