What does status no_sys_peer mean?


#1

submitting an ntpq -crv yields the following:

associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,
version=“ntpd 4.2.8p10-a (1)”, processor=“amd64”,
system=“FreeBSD/11.0-RELEASE-p9”, leap=00, stratum=3, precision=-20,
rootdelay=0.861, rootdisp=12.887, refid=172.26.1.5,
reftime=dd0772a6.8ede7b33 Wed, Jul 5 2017 10:13:58.558,
clock=dd077345.588448aa Wed, Jul 5 2017 10:16:37.345, peer=65193, tc=6,
mintc=3, offset=-0.093192, frequency=31.630, sys_jitter=0.315736,
clk_jitter=0.029, clk_wander=0.003, tai=37, leapsec=201701010000,
expire=201706010000

Only if I restart the ntp service do I get a clock_sync status.

Ideas?


#2

Does ntpq -pn show a selected peer (indicated with a star)?

no_sys_peer and clock_sync are the last recorded system events, they don’t describe the current state. If no_sys_peer is reported, it means at some point no source could be selected. There is no event for selecting a peer, so even if everything works as expected, the event may stay there for a very long time, for example until the next leap second.

A list of system events is here.