[LEDE-DEV] busybox ntpd not syncing if any server is bad

Magnus Kroken mkroken at gmail.com
Wed Aug 23 10:22:11 PDT 2017


On 21.08.2017 16:34, Karl Palsson wrote:
> on master, even with the ntpd patch for busybox applied.
> # ntpdate -q localhost
> server ::1, stratum 0, offset 0.000000, delay 0.00000
> server 127.0.0.1, stratum 0, offset 0.000000, delay 0.00000 21
> Aug 14:26:24 ntpdate[1392]: no server suitable for
> synchronization found
> # echo $?
> 1
> # ntpd -w -d -p localhost
> ntpd: sending query to 127.0.0.1
> ntpd: reply from 127.0.0.1: peer is unsynced
> ntpd: sending query to 127.0.0.1

Thanks for the clarification. Running ntpd like before (-p 
bad.example.org -p ntp.uio.no), LEDE master with Busybox 1.27.2 does 
seem to work:

root at LEDE:~# ntpdate -q ::1
server ::1, stratum 3, offset 0.000028, delay 0.02777
23 Aug 19:12:55 ntpdate[5416]: adjust time server ::1 offset 0.000028 sec
root at LEDE:~# echo $?
0

I also tested against my OpenWrt 15.05 VM and the current LEDE x86_64 
snapshot (r4723), and they both give the expected output as you describe 
(OpenWrt similar to above, LEDE fails).

Note that my patch in Patchwork only updates to Busybox 1.27.1, I will 
send the 1.27.2 patch shortly, after rebasing and testing it.

Regards
/Magnus



More information about the Lede-dev mailing list