Bug 7910 - ntpd daemon raise "peer is unsynced" message
Summary: ntpd daemon raise "peer is unsynced" message
Status: RESOLVED WORKSFORME
Alias: None
Product: Busybox
Classification: Unclassified
Component: Networking (show other bugs)
Version: 1.22.x
Hardware: PC Linux
: P5 major
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-06 08:27 UTC by rainbow
Modified: 2017-10-30 17:27 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
ntpd still failing after latest patch (6.38 KB, text/x-log)
2017-10-30 16:29 UTC, Karl Palsson 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rainbow 2015-03-06 08:27:52 UTC 
I have checked the talk between Laszlo Papp and Denys Vlasenko about ntpd daemon in mail list.
http://lists.busybox.net/pipermail/busybox/2015-March/082405.html

From the talk, seems ntpd support accept the PEER parameter properly to function as a client as well as server with following options:
# /usr/sbin/ntpd -n -l -d -p 10.56.212.32

But when i trying to sync time from the "server", i got "peer is unsynced" message. (169.254.0.4 is internal address of the "server")
# /usr/sbin/ntpd -n -d -p 169.254.0.4
ntpd: sending query to 169.254.0.4
ntpd: reply from 169.254.0.4: peer is unsynced
ntpd: sending query to 169.254.0.4
ntpd: reply from 169.254.0.4: peer is unsynced
ntpd: sending query to 169.254.0.4
ntpd: reply from 169.254.0.4: peer is unsynced

My BusyBox version is v1.22.1.
Comment 1 Denys Vlasenko 2017-04-07 19:19:51 UTC 
Can't reproduce on current git:

# ./busybox ntpd -dddnw -p 127.0.0.1
ntpd: sending query to 127.0.0.1
ntpd: reply from 127.0.0.1: offset:+0.000032 delay:0.002000 status:0x24 strat:2 refid:0x414d4443 rootdelay:0.158251 reach:0x01
ntpd: no valid datapoints, no peer selected
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 127.0.0.1
ntpd: reply from 127.0.0.1: offset:+0.000031 delay:0.002000 status:0x24 strat:2 refid:0x414d4443 rootdelay:0.158251 reach:0x03
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 127.0.0.1
ntpd: reply from 127.0.0.1: offset:+0.000023 delay:0.002000 status:0x24 strat:2 refid:0x414d4443 rootdelay:0.158251 reach:0x07
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 127.0.0.1
ntpd: reply from 127.0.0.1: offset:+0.000011 delay:0.002000 status:0x24 strat:2 refid:0x414d4443 rootdelay:0.158251 reach:0x0f
ntpd: poll:1s sockets:0 interval:1s
ntpd: sending query to 127.0.0.1
ntpd: reply from 127.0.0.1: offset:-0.000005 delay:0.002000 status:0x24 strat:2 refid:0x414d4443 rootdelay:0.158251 reach:0x1f
ntpd: poll:33s sockets:0 interval:32s
^C

(The server is also bbox ntpd).
Comment 2 Karl Palsson 2017-10-30 16:29:32 UTC 
Created attachment 7346 [details]
ntpd still failing after latest patch

applied the patch to 1.27.2 cleanly, nothing else seems relevant.

It's "better" but still never syncs, and still has long blocks between sending and getting replies.

It's even worse with more bad addresses, and also with a host listed by IP that is also unreachable.
Comment 3 Karl Palsson 2017-10-30 17:27:25 UTC 
sorry, this got attached to the wrong bug, sorry about that.