19c2daa00SOllivier Robert<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 29c2daa00SOllivier Robert<html> 39c2daa00SOllivier Robert<head> 4ea906c41SOllivier Robert<meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> 59c2daa00SOllivier Robert<meta name="generator" content="HTML Tidy, see www.w3.org"> 69c2daa00SOllivier Robert<title>ntpd System Log Messages</title> 79c2daa00SOllivier Robert<link href="scripts/style.css" type="text/css" rel="stylesheet"> 89c2daa00SOllivier Robert</head> 99c2daa00SOllivier Robert<body> 109c2daa00SOllivier Robert<h3><tt>ntpd</tt> System Log Messages</h3> 11*2b15cb3dSCy Schubert<img src="pic/flatheads.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> 12*2b15cb3dSCy Schubert<p>The log can be shrill at times.</p> 13*2b15cb3dSCy Schubert<p>Last update: 14*2b15cb3dSCy Schubert <!-- #BeginDate format:En2m -->10-Mar-2014 05:12<!-- #EndDate --> 15*2b15cb3dSCy Schubert UTC</p> 169c2daa00SOllivier Robert<br clear="left"> 179c2daa00SOllivier Robert<h4>Related Links</h4> 18*2b15cb3dSCy Schubert<p> 19*2b15cb3dSCy Schubert <script type="text/javascript" language="javascript" src="scripts/install.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> 28*2b15cb3dSCy Schubert <dt><tt>buffer overflow ? </tt></dt> 29*2b15cb3dSCy Schubert <dd>Fatal error. An input packet is too long for processing.</dd> 309c2daa00SOllivier Robert</dl> 319c2daa00SOllivier Robert<p><tt><b>LOG_NOTICE</b></tt></p> 329c2daa00SOllivier Robert<dl> 33*2b15cb3dSCy Schubert <dt><tt>no reply; clock not set</tt></dt> 34*2b15cb3dSCy Schubert <dd>In <tt>ntpdate</tt> mode no servers have been found. The server(s) and/or network may be down. Standard debugging procedures apply.</dd> 35*2b15cb3dSCy Schubert</dl> 369c2daa00SOllivier Robert<p><tt><b>LOG_INFO</b></tt></p> 37*2b15cb3dSCy Schubert<dl> 38*2b15cb3dSCy Schubert <dt><tt>proto_config: illegal item ?, value ?</tt></dt> 39*2b15cb3dSCy Schubert <dd>Program error. Bugs can be reported <a href="bugs.html">here</a>.</dd> 40*2b15cb3dSCy Schubert <dt><tt>receive: autokey requires two-way communication</tt></dt> 41*2b15cb3dSCy Schubert <dd>Configuration error on the <tt>broadcastclient</tt> command.</dd> 42*2b15cb3dSCy Schubert <dt><tt>receive: server <i>server</i> maaximum rate exceeded</tt></dt> 43*2b15cb3dSCy Schubert <dd>A kiss-o'death packet has been received. The transmit rate is automatically reduced.</dd> 44*2b15cb3dSCy Schubert <dt><tt>pps sync enabled</tt></dt> 45*2b15cb3dSCy Schubert <dd>The PPS signal has been detected and enabled.</dd> 46*2b15cb3dSCy Schubert <dt><tt>transmit: encryption key ? not found</tt></dt> 47*2b15cb3dSCy Schubert <dd>The encryption key is not defined or not trusted.</dd> 48*2b15cb3dSCy Schubert <dt><tt>precision = ? usec </tt></dt> 49*2b15cb3dSCy Schubert <dd>This reports the precision measured for this machine.</dd> 50*2b15cb3dSCy Schubert <dt><tt>using 10ms tick adjustments</tt></dt> 51*2b15cb3dSCy Schubert <dd>Gotcha for some machines with dirty rotten clock hardware.</dd> 52*2b15cb3dSCy Schubert <dt><tt>no servers reachable</tt></dt> 53*2b15cb3dSCy Schubert <dd>The system clock is running on internal batteries. The server(s) and/or network may be down.</dd> 549c2daa00SOllivier Robert</dl> 559c2daa00SOllivier Robert<h4>Clock Discipline Module</h4> 569c2daa00SOllivier Robert<p><tt><b>LOG_ERR</b></tt></p> 579c2daa00SOllivier Robert<dl> 58*2b15cb3dSCy Schubert <dt><tt>time correction of ? seconds exceeds sanity limit (?); set clock manually to the correct UTC time</tt>.</dt> 59*2b15cb3dSCy Schubert <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.</dd> 60ea906c41SOllivier Robert <dt><tt>sigaction() fails to save SIGSYS trap: ?<br> 61*2b15cb3dSCy Schubert </tt><tt>sigaction() fails to restore SIGSYS trap: ?</tt></dt> 62*2b15cb3dSCy Schubert <dt>Program error. Bugs can be reported <a href="bugs.html">here</a>.</dt> 639c2daa00SOllivier Robert</dl> 649c2daa00SOllivier Robert<p><tt><b>LOG_NOTICE</b></tt></p> 659c2daa00SOllivier Robert<dl> 66*2b15cb3dSCy Schubert <dt><tt>frequency error ? exceeds tolerance 500 PPM</tt></dt> 67*2b15cb3dSCy Schubert <dd>The hardware clock frequency error exceeds the rate the kernel can correct. This could be a hardware or a kernel problem.</dd> 68*2b15cb3dSCy Schubert <dt><tt>time slew ? s</tt></dt> 69*2b15cb3dSCy Schubert <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.</dd> 70*2b15cb3dSCy Schubert <dt><tt>time reset ? s</tt></dt> 71*2b15cb3dSCy Schubert <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.</dd> 72*2b15cb3dSCy Schubert <dt><tt>kernel time sync disabled ?</tt></dt> 73*2b15cb3dSCy Schubert <dd>The kernel reports an error. See the codes in the <tt>timex.h</tt> file.</dd> 74*2b15cb3dSCy Schubert <dt><tt>pps sync disabled</tt></dt> 75*2b15cb3dSCy Schubert <dd>The PPS signal has died, probably due to a dead radio, broken wire or loose connector.</dd> 769c2daa00SOllivier Robert</dl> 779c2daa00SOllivier Robert<p><tt><b>LOG_INFO</b></tt></p> 789c2daa00SOllivier Robert<dl> 79*2b15cb3dSCy Schubert <dt><tt>kernel time sync status ? </tt></dt> 80*2b15cb3dSCy Schubert <dd>For information only. See the codes in the <tt>timex.h</tt> file.</dd> 819c2daa00SOllivier Robert</dl> 829c2daa00SOllivier Robert<h4>Cryptographic Module</h4> 839c2daa00SOllivier Robert<p><tt><b>LOG_ERR</b></tt></p> 849c2daa00SOllivier Robert<dl> 85ea906c41SOllivier Robert <dt><tt>cert_parse ?<br> 86ea906c41SOllivier Robert </tt><tt>cert_sign ?<br> 87ea906c41SOllivier Robert </tt><tt>crypto_cert ?<br> 88ea906c41SOllivier Robert </tt><tt>crypto_encrypt ?<br> 89ea906c41SOllivier Robert </tt><tt>crypto_gq ?<br> 90ea906c41SOllivier Robert </tt><tt>crypto_iff ?<br> 91ea906c41SOllivier Robert </tt><tt>crypto_key ?<br> 92ea906c41SOllivier Robert </tt><tt>crypto_mv ?<br> 93ea906c41SOllivier Robert </tt><tt>crypto_setup ?<br> 94*2b15cb3dSCy Schubert </tt><tt>make_keys ?</tt></dt> 95*2b15cb3dSCy Schubert <dd>Usually fatal errors. These messages display error codes returned from the OpenSSL library. See the OpenSSL documentation for explanation.</dd> 96ea906c41SOllivier Robert <dt><tt>crypto_setup: certificate ? is trusted, but not self signed.<br> 97ea906c41SOllivier Robert </tt><tt>crypto_setup: certificate ? not for this host<br> 98ea906c41SOllivier Robert </tt><tt>crypto_setup: certificate file ? not found or corrupt<br> 99ea906c41SOllivier Robert </tt><tt>crypto_setup: host key file ? not found or corrupt<br> 100ea906c41SOllivier Robert </tt><tt>crypto_setup: host key is not RSA key type<br> 101ea906c41SOllivier Robert </tt><tt>crypto_setup: random seed file ? not found<br> 102*2b15cb3dSCy Schubert </tt><tt>rypto_setup: random seed file not specified</tt></dt> 103*2b15cb3dSCy Schubert <dd>Fatal errors. These messages show problems during the initialization procedure.</dd> 1049c2daa00SOllivier Robert</dl> 1059c2daa00SOllivier Robert<p><tt><b>LOG_INFO</b></tt></p> 1069c2daa00SOllivier Robert<dl> 107ea906c41SOllivier Robert <dt><tt>cert_parse: expired ?<br> 108ea906c41SOllivier Robert </tt><tt>cert_parse: invalid issuer ?<br> 109ea906c41SOllivier Robert </tt><tt>cert_parse: invalid signature ?<br> 110*2b15cb3dSCy Schubert </tt><tt>cert_parse: invalid subject ?</tt></dt> 111*2b15cb3dSCy Schubert <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.</dd> 112ea906c41SOllivier Robert <dt><tt>crypto_?: defective key<br> 113ea906c41SOllivier Robert </tt><tt>crypto_?: invalid filestamp<br> 114ea906c41SOllivier Robert </tt><tt>crypto_?: missing challenge<br> 115*2b15cb3dSCy Schubert </tt><tt>crypto_?: scheme unavailable</tt></dt> 116*2b15cb3dSCy Schubert <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.</dd> 117*2b15cb3dSCy Schubert <dt><tt>crypto_cert: wrong PEM type ?</tt></dt> 118*2b15cb3dSCy Schubert <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.</dd> 119*2b15cb3dSCy Schubert <dt><tt>crypto_ident: no compatible identity scheme found</tt></dt> 120*2b15cb3dSCy Schubert <dd>Configuration error. The server and client identity schemes are incompatible.</dd> 121*2b15cb3dSCy Schubert <dt><tt>crypto_tai: kernel TAI update failed</tt></dt> 122*2b15cb3dSCy Schubert <dd>The kernel does not support this function. You may need a new kernel or patch.</dd> 123*2b15cb3dSCy Schubert <dt><tt>crypto_tai: leapseconds file ? error ?</tt></dt> 124*2b15cb3dSCy Schubert <dd>The leapseconds file is corrupt. Obtain the latest file from <tt>time.nist.gov</tt>.</dd> 1259c2daa00SOllivier Robert</dl> 1269c2daa00SOllivier Robert<hr> 1279c2daa00SOllivier Robert<script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> 1289c2daa00SOllivier Robert</body> 1299c2daa00SOllivier Robert</html> 130
