[LEDE-DEV] busybox ntpd not syncing if any server is bad
Karl Palsson
karlp at tweak.net.au
Thu Aug 17 04:01:25 PDT 2017
Hi,
On old openwrt 15.05 builds, if I was running in a private
network, and only had some NTP servers available, ntpd would
still sync, and I could still query the local ntpd for it's sync
status.
However, now in lede-17.01 and lede current master, ntpd seems to
just get stuck trying the first listed ntp server, and never
gives up and tries the other listed servers. This seems rather
odd, and particularly unhelpful. Does anyone know any
workarounds?
# ntpd -n -d -l -S /usr/sbin/ntpd-hotplug -p bad.example.org -p somewhere.working.org
ntpd: bad address 'bad.example.org'
ntpd: bad address 'bad.example.org'
ntpd: bad address 'bad.example.org'
... forever....
It never gets to trying "somewhere.working.org" so simply never
gets sync. Same behaviour on both 17.01 and master branch, though
on 17.01, the :123 listen ports aren't opened up at all.
On openwrt 15.05 (busybox 1.23.2) the behaviour is markedly
different
# /usr/sbin/ntpd -d -n -l -S /usr/sbin/ntpd-hotplug -p bad.example.org -p somewhere.working.org
ntpd: resolved peer somewhere.working.org to 192.168.255.124
ntpd: sending query to 192.168.255.124 ntpd: bad address
'bad.example.org' ntpd: could not resolve peer bad.example.org,
skipping ntpd: reply from 192.168.255.124: offset:-0.004779
delay:0.012441 status:0x24 strat:3 refid:0xc1043a2c
rootdelay:0.001465 reach:0x01 ntpd: sending query to
192.168.255.124 ntpd: reply from 192.168.255.124:
offset:+0.001084 delay:0.002000 status:0x24 strat:3
refid:0xc1043a2c rootdelay:0.001465 reach:0x03
Sincerely,
Karl Palsson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.html
Type: application/pgp-signature
Size: 1161 bytes
Desc: OpenPGP Digital Signature
URL: <http://lists.infradead.org/pipermail/lede-dev/attachments/20170817/063eaa50/attachment.sig>
More information about the Lede-dev
mailing list