19c2daa00SOllivier Robert<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 29c2daa00SOllivier Robert 39c2daa00SOllivier Robert<html> 49c2daa00SOllivier Robert 59c2daa00SOllivier Robert <head> 69c2daa00SOllivier Robert <meta name="generator" content="HTML Tidy, see www.w3.org"> 79c2daa00SOllivier Robert <title>ntpd System Log Messages</title> 89c2daa00SOllivier Robert <link href="scripts/style.css" type="text/css" rel="stylesheet"> 99c2daa00SOllivier Robert </head> 109c2daa00SOllivier Robert 119c2daa00SOllivier Robert <body> 129c2daa00SOllivier Robert <h3><tt>ntpd</tt> System Log Messages</h3> 139c2daa00SOllivier Robert <img src="pic/alice47.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/~mills/pictures.html">from <i>Alice's Adventures in Wonderland</i>, Lewis Carroll</a> 149c2daa00SOllivier Robert <p>The mushroom knows all the error codes, which is more than most of us do.</p> 159c2daa00SOllivier Robert <p>Last update: <csobj format="ShortTime" h="24" locale="00000409" region="0" t="DateTime" w="50">02:23</csobj> UTC <csobj format="LongDate" h="24" locale="00000409" region="0" t="DateTime" w="254">Saturday, February 01, 2003</csobj></p> 169c2daa00SOllivier Robert <br clear="left"> 179c2daa00SOllivier Robert <h4>Related Links</h4> 189c2daa00SOllivier Robert <p> 199c2daa00SOllivier Robert <script type="text/javascript" language="javascript" src="scripts/links7.txt"></script> 209c2daa00SOllivier Robert </p> 219c2daa00SOllivier Robert <hr> 229c2daa00SOllivier Robert <p>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: <tt><b>LOG_ERR</b></tt>, <b><tt>LOG_NOTICE</tt></b> and <tt><b>LOG_INFO</b></tt>.</p> 239c2daa00SOllivier Robert <p>Most of the time <b><tt>LOG_ERR</tt></b> messages are fatal, but often <tt>ntpd</tt> limps onward in the hopes of discovering more errors. The <tt><b>LOG_NOTICE</b></tt> messages usually mean the time has changed or some other condition that probably should be noticed. The <tt><b>LOG_INFO</b></tt> messages usually say something about the system operations, but do not affect the time.</p> 249c2daa00SOllivier Robert <p>In the following a '?' character stands for text in the message. The meaning should be clear from context.</p> 259c2daa00SOllivier Robert <h4>Protocol Module</h4> 269c2daa00SOllivier Robert <p><tt><b>LOG_ERR</b></tt></p> 279c2daa00SOllivier Robert <dl> 289c2daa00SOllivier Robert <dt>buffer overflow ? 299c2daa00SOllivier Robert <dd>Fatal error. An input packet is too long for processing. 309c2daa00SOllivier Robert </dl> 319c2daa00SOllivier Robert <p><tt><b>LOG_NOTICE</b></tt></p> 329c2daa00SOllivier Robert <dl> 339c2daa00SOllivier Robert <dt><tt>no reply; clock not set </tt> 349c2daa00SOllivier Robert <dd>In <tt>ntpdate</tt> mode no servers have been found. The server(s) and/or network may be down. Standard debugging procedures apply. 359c2daa00SOllivier Robert </dl> 369c2daa00SOllivier Robert <p><tt><b>LOG_INFO</b></tt></p> 379c2daa00SOllivier Robert <dl> 389c2daa00SOllivier Robert <dt><tt>proto_config: illegal item ?, value ? </tt> 399c2daa00SOllivier Robert <dd>Program error. Please report to bugs@ntp.org. 409c2daa00SOllivier Robert <dt><tt>pps sync enabled </tt> 419c2daa00SOllivier Robert <dd>The PPS signal has been detected and enabled. 429c2daa00SOllivier Robert <dt><tt>transmit: encryption key ? not found </tt> 439c2daa00SOllivier Robert <dd>The key cache is inconsistent. Please report to bugs@ntp.org. 449c2daa00SOllivier Robert <dt><tt>precision = ? usec </tt> 459c2daa00SOllivier Robert <dd>This reports the precision measured for this machine. 469c2daa00SOllivier Robert <dt><tt>using 10ms tick adjustments </tt> 479c2daa00SOllivier Robert <dd>Gotcha for some machines with dirty rotten clock hardware. 489c2daa00SOllivier Robert <dt><tt>no servers reachable </tt> 499c2daa00SOllivier Robert <dd>The system clock is running on internal batteries. The server(s) and/or network may be down. 509c2daa00SOllivier Robert </dl> 519c2daa00SOllivier Robert <h4>Clock Discipline Module</h4> 529c2daa00SOllivier Robert <p><tt><b>LOG_ERR</b></tt></p> 539c2daa00SOllivier Robert <dl> 549c2daa00SOllivier Robert <dt><tt>time correction of ? seconds exceeds sanity limit (?); set clock manually to the correct UTC time</tt>. 559c2daa00SOllivier Robert <dd>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. 569c2daa00SOllivier Robert <dt><tt>sigaction() fails to save SIGSYS trap: ? </tt> 579c2daa00SOllivier Robert <dt><tt>sigaction() fails to restore SIGSYS trap: ? </tt> 589c2daa00SOllivier Robert <dd>Program error. Please report to bugs@ntp.org. 599c2daa00SOllivier Robert </dl> 609c2daa00SOllivier Robert <p><tt><b>LOG_NOTICE</b></tt></p> 619c2daa00SOllivier Robert <dl> 629c2daa00SOllivier Robert <dt><tt>frequency error ? exceeds tolerance 500 PPM</tt> 639c2daa00SOllivier Robert <dd>The hardware clock frequency error exceeds the rate the kernel can correct. This could be a hardware or a kernel problem. <dt><tt>time slew ? s </tt> 649c2daa00SOllivier Robert <dd>The time error exceeds the step threshold and is being slewed to the correct time. You may have to wait a very long time. 659c2daa00SOllivier Robert <dt><tt>time reset ? s </tt> 669c2daa00SOllivier Robert <dd>The time error exceeds the step threshold and has been reset to the correct time. Computer scientists don't like this, but they can set the <tt>ntpd -x</tt> option and wait forever. 679c2daa00SOllivier Robert <dt><tt>kernel time sync disabled ? </tt> 689c2daa00SOllivier Robert <dd>The kernel reports an error. See the codes in the <tt>timex.h</tt> file. 699c2daa00SOllivier Robert <dt><tt>pps sync disabled </tt> 709c2daa00SOllivier Robert <dd>The PPS signal has died, probably due to a dead radio, broken wire or loose connector. 719c2daa00SOllivier Robert </dl> 729c2daa00SOllivier Robert <p><tt><b>LOG_INFO</b></tt></p> 739c2daa00SOllivier Robert <tt>kernel time sync status ? </tt> 749c2daa00SOllivier Robert <dl> 759c2daa00SOllivier Robert <dd>For information only. See the codes in the <tt>timex.h</tt> file. 769c2daa00SOllivier Robert </dl> 779c2daa00SOllivier Robert <h4>Cryptographic Module</h4> 789c2daa00SOllivier Robert <p><tt><b>LOG_ERR</b></tt></p> 799c2daa00SOllivier Robert <dl> 809c2daa00SOllivier Robert <dt><tt>cert_parse ? </tt> 819c2daa00SOllivier Robert <dt><tt>cert_sign ? </tt> 829c2daa00SOllivier Robert <dt><tt>crypto_cert ? </tt> 839c2daa00SOllivier Robert <dt><tt>crypto_encrypt ? </tt> 849c2daa00SOllivier Robert <dt><tt>crypto_gq ? </tt> 859c2daa00SOllivier Robert <dt><tt>crypto_iff ? </tt> 869c2daa00SOllivier Robert <dt><tt>crypto_key ? </tt> 879c2daa00SOllivier Robert <dt><tt>crypto_mv ? </tt> 889c2daa00SOllivier Robert <dt><tt>crypto_setup ? </tt> 899c2daa00SOllivier Robert <dt><tt>make_keys ? </tt> 909c2daa00SOllivier Robert <dd>Usually fatal errors. These messages display error codes returned from the OpenSSL library. See the OpenSSL documentation for explanation. 919c2daa00SOllivier Robert <dt><tt>crypto_setup: certificate ? is trusted, but not self signed. </tt> 929c2daa00SOllivier Robert <dt><tt>crypto_setup: certificate ? not for this host </tt> 939c2daa00SOllivier Robert <dt><tt>crypto_setup: certificate file ? not found or corrupt </tt> 949c2daa00SOllivier Robert <dt><tt>crypto_setup: host key file ? not found or corrupt </tt> 959c2daa00SOllivier Robert <dt><tt>crypto_setup: host key is not RSA key type </tt> 969c2daa00SOllivier Robert <dt><tt>crypto_setup: random seed file ? not found</tt> 979c2daa00SOllivier Robert <dt><tt>crypto_setup: random seed file not specified </tt> 989c2daa00SOllivier Robert <dd>Fatal errors. These messages show problems during the initialization procedure. 999c2daa00SOllivier Robert </dl> 1009c2daa00SOllivier Robert <p><tt><b>LOG_INFO</b></tt></p> 1019c2daa00SOllivier Robert <dl> 1029c2daa00SOllivier Robert <dt><tt>cert_parse: expired ? </tt> 1039c2daa00SOllivier Robert <dt><tt>cert_parse: invalid issuer ? </tt> 1049c2daa00SOllivier Robert <dt><tt>cert_parse: invalid signature ? </tt> 1059c2daa00SOllivier Robert <dt><tt>cert_parse: invalid subject ? </tt> 1069c2daa00SOllivier Robert <dd>There is a problem with a certificate. Operation cannot proceed untill the problem is fixed. If the certificate is local, it can be regenerated using the <tt>ntp-keygen</tt> program. If it is held somewhere else, it must be fixed by the holder. 1079c2daa00SOllivier Robert <dt><tt>crypto_?: defective key </tt> 1089c2daa00SOllivier Robert <dt><tt>crypto_?: invalid filestamp </tt> 1099c2daa00SOllivier Robert <dt><tt>crypto_?: missing challenge </tt> 1109c2daa00SOllivier Robert <dt><tt>crypto_?: scheme unavailable </tt> 1119c2daa00SOllivier Robert <dd>There is a problem with the identity scheme. Operation cannot proceed untill the problem is fixed. Usually errors are due to misconfiguration or an orphan association. If the latter, <tt>ntpd</tt> will usually time out and recover by itself. 1129c2daa00SOllivier Robert <dt><tt>crypto_cert: wrong PEM type ? </tt> 1139c2daa00SOllivier Robert <dd>The certificate does not have MIME type <tt>CERTIFICATE</tt>. You are probably using the wrong type from OpenSSL or an external certificate authority. 1149c2daa00SOllivier Robert <dt><tt>crypto_ident: no compatible identity scheme found </tt> 1159c2daa00SOllivier Robert <dd>Configuration error. The server and client identity schemes are incompatible. 1169c2daa00SOllivier Robert <dt><tt>crypto_tai: kernel TAI update failed </tt> 1179c2daa00SOllivier Robert <dd>The kernel does not support this function. You may need a new kernel or patch. 1189c2daa00SOllivier Robert <dt><tt>crypto_tai: leapseconds file ? error ? </tt> 1199c2daa00SOllivier Robert <dd>The leapseconds file is corrupt. Obtain the latest file from <tt>time.nist.gov</tt>. 1209c2daa00SOllivier Robert </dl> 1219c2daa00SOllivier Robert <hr> 1229c2daa00SOllivier Robert <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> 1239c2daa00SOllivier Robert </body> 1249c2daa00SOllivier Robert 1259c2daa00SOllivier Robert</html>
