Subject: bin/17899: ntpd log messages are misleading
To: None <email@example.com>
From: None <firstname.lastname@example.org>
Date: 08/09/2002 18:55:13
>Synopsis: ntpd says connection re-estabished, even if server is unreachable
>Arrival-Date: Fri Aug 09 11:56:00 PDT 2002
>Release: NetBSD 1.6E
System: NetBSD eros.endersgame.net 1.6E NetBSD 1.6E (EROS) #361: Wed Aug 7 14:43:33 EDT 2002 email@example.com:/disk2/a/cvs/netbsd/current/src/sys/arch/i386/compile/EROS i386
ntpd will say that a connection has been re-established, even if the ntp
server it is trying to contact is not currently reachable.
For example, I run ntpd on a machine here, and my cable modem was out for
twelve hours. many times during this period, ntpd told me:
Aug 9 10:17:53 eros ntpd: Connection re-established to 184.108.40.206
Aug 9 10:20:31 eros ntpd: Connection re-established to 220.127.116.11
Aug 9 10:22:44 eros ntpd: Connection re-established to 18.104.22.168
Aug 9 10:34:58 eros ntpd: sendto(22.214.171.124): No route to host
Aug 9 10:37:35 eros ntpd: sendto(126.96.36.199): No route to host
Aug 9 10:39:50 eros ntpd: sendto(188.8.131.52): No route to host
Thus, it tells me re-established, even when it is no such thing.
Run ntpd, set it up to contact a server somewhere, then remove all
connectivity to that server and wait for it to try and sync.
ntpd should not say re-established if it has not actually done so.
"Attempting to re-establish connection" or something of the like would be