Web lists-archives.com

Re: ntp problem in broadcastclients




On Thursday 25 October 2018 14:08:47 Curt wrote:

> On 2018-10-25, Gene Heskett <gheskett@xxxxxxxxxxx> wrote:
> > On Thursday 25 October 2018 09:32:08 Curt wrote:
> >> On 2018-10-25, Greg Wooledge <wooledg@xxxxxxxxxxx> wrote:
> >> >> 2 machines report:
> >> >> pi@picnc:/etc $ ntpq -p
> >> >> No association ID's returned
> >> >
> >> > I've literally never seen such a message before.  I googled it,
> >> > and there are definitely results that look relevant.  After
> >> > adding "broadcast" to the search terms, I came up with this
> >> > result:
> >>
> >> I saw this:
> >>
> >> https://wiki.debian.org/NTP
> >>
> >>  Troubleshooting
> >>
> >>   If you run ntpq -p and you get
> >>
> >>   No association ID's returned
> >>
> >>  Run
> >>
> >>  dpkg-reconfigure ntp
> >>
> >> Seems kind of too easy and rather short on the explicit details,
> >> though.
> >
> > not to belabor the point, but it also didn't work.  Sigh.
>
> That too.
>
> >> > http://lists.ntp.org/pipermail/questions/2014-December/039401.htm
> >> >l

This link indicated that I also needed a server entry in the ntp.conf files.
Added that, and restarted ntp, and everything now has the proper response to
an ntpq -p query. And its all in the same second for the individual date command.

I think I'll quit while I'm ahead. :)

I added the router to the server list for this machine and get this for an ntpq -p:
    remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 router.coyote.d .INIT.          16 u    -  512    0    0.000    0.000   0.000
-ip7.nsg.sbbsnet 64.113.44.54     2 u   31   64   17   43.611    5.083   2.148
+142.147.92.5.st 216.218.192.202  2 u   37   64  377   82.436   -3.643   1.587
*dfw1.m-d.net    204.9.54.119     2 u   99   64  376   49.024   -0.327   1.700
+12.167.151.2    198.148.79.210   3 u   31   64  377   15.694    0.584   2.247
 192.168.71.255  .BCST.          16 u    -   64    0    0.000    0.000   0.000

And the daemon.log now says:
Oct 25 16:16:04 coyote ntpd[5026]: ntpd exiting on signal 15
Oct 25 16:16:06 coyote ntpd[2518]: ntpd 4.2.6p5@1.2349-o Fri Jul 22 18:00:30 UTC 2016 (1)
Oct 25 16:16:06 coyote ntpd[2519]: proto: precision = 0.274 usec
Oct 25 16:16:06 coyote ntpd[2519]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 25 16:16:06 coyote ntpd[2519]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 25 16:16:06 coyote ntpd[2519]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 25 16:16:06 coyote ntpd[2519]: Listen normally on 3 eth0 192.168.71.3 UDP 123
Oct 25 16:16:06 coyote ntpd[2519]: peers refreshed
Oct 25 16:16:06 coyote ntpd[2519]: Listening on routing socket on fd #20 for interface updates
 
Does that all look legit?

> > I'll look at that after I had a nap, been up since about 4ish.

Thanks all.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>