[Bug 10466] New: ntpd: fails to sync if bad servers first in list

bugzilla at busybox.net bugzilla at busybox.net
Fri Oct 27 16:48:33 UTC 2017


            Bug ID: 10466
           Summary: ntpd: fails to sync if bad servers first in list
           Product: Busybox
           Version: 1.27.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Networking
          Assignee: unassigned at busybox.net
          Reporter: karlp at tweak.net.au
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Created attachment 7331
  --> https://bugs.busybox.net/attachment.cgi?id=7331&action=edit
failing case, good server last in list

Running 1.27.2 on LEDE(OpenWrt) specifically to pick up all the recent ntpd

If there is a good server at the _start_ of the list, all bad servers are
successfully ignored.  If the first server in the list is bad however, ntpd
will send and receive replies, but never step time, nor issue a stratum event
indicated sync has been achieved.

Logs (with annotations) from both cases attached separately.

It's important to note that this cannot be tested with typical "bad" hosts like
bad.example.org.  Those are explicitly recognised and return a dns failure
"immediately"  You need a good proper dns timeout.

It seems that it sends the query to the good server, then, instead of
processing the reply, it goes and tries dns resolution again for the bad
servers, before finally processing the (now old) reply, and discarding? it.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the busybox-cvs mailing list