ntpd does not sufficiently log failures
Bug #244685 reported by
Forest
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: ntp
I recently spent way too much time trying to figure out why ntpd was starting but not associating with any peers. In the end, I found out that ntpd doesn't write a log message when a dns lookup fails. It simply forgets the unresolved ntp server was ever listed in ntp.conf. Also, ntpd command line failures at boot time (due to rejected command line options in /etc/default/ntp) do not seem to get logged.
These problems were observed on Ubuntu Hardy, ntp 1:4.2.4p4+
Changed in ntp (Ubuntu): | |
status: | Confirmed → Triaged |
To post a comment you must log in.
Thanks Ill consider it for karmic + 1.
Regards
chuck