Is anyone able to shed some further light on this issue? I plan to
remove the LOCAL clock from ntp's configuration, but I'm still keen to
know why it's defaulting to the LOCAL clock once network connectivity is
down, and then ignoring any of the public NTP servers configured when
network connectivity returns. It stays locked to the LOCAL clock for
weeks until we actually restart it manually.
Cheers,
Stephen
[]
hostname .INIT. 16 u - 1024 0 0.000 0.000 0.000
hostname .INIT. 16 u - 1024 0 0.000 0.000 0.000
hostname .INIT. 16 u - 1024 0 0.000 0.000 0.000
hostname.INIT. 16 u - 1024 0 0.000 0.000 0.000
*LOCAL(0) .LOCL. 10 l 9 64 377 0.000 0.000
0.001
Your billboard output shows that ntpd isn't able to reach any of the
servers you have listed in the configuration file. See if you can ping
them, and check your firewall settings.
Cheers,
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
