Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201648
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: ntp problem in broadcastclients |
| Date | 2018-10-25 23:00 +0200 |
| Message-ID | <wMUTv-3uS-1@gated-at.bofh.it> (permalink) |
| References | <wMqsq-2dH-5@gated-at.bofh.it> <wMSf0-28c-3@gated-at.bofh.it> <wMSoG-2bm-5@gated-at.bofh.it> <wMUJQ-3rH-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Oct 25, 2018 at 04:40:46PM -0400, Gene Heskett wrote: > 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 The first line (router.coyote.d, which I presume is your router) is showing stratum 16, which means it does not consider itself to be a valid time source yet. This could be because you haven't given it enough time to stabilize (i.e. you just restarted it), or because it can't actually contact any time servers in order to synchronize at all. If it remains "st 16" for more than a few minutes, then something is probably wrong. Meanwhile, this system is getting valid time synchronization from four other sources (three of them stratum 2, one stratum 3). Your offset values look good (the offset is shown in milliseconds, so you are within about 5 milliseconds of all your valid sources).
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-24 14:30 +0200
Re: ntp problem in broadcastclients Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-24 14:50 +0200
Re: ntp problem in broadcastclients john doe <johndoe65534@mail.com> - 2018-10-24 16:30 +0200
Re: ntp problem in broadcastclients rhkramer@gmail.com - 2018-10-24 17:10 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-25 00:30 +0200
Re: ntp problem in broadcastclients rhkramer@gmail.com - 2018-10-25 01:20 +0200
Re: ntp problem in broadcastclients rhkramer@gmail.com - 2018-10-25 01:20 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-25 00:30 +0200
Re: ntp problem in broadcastclients Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-25 14:30 +0200
Re: ntp problem in broadcastclients Curt <curty@free.fr> - 2018-10-25 15:40 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-25 20:10 +0200
Re: ntp problem in broadcastclients Curt <curty@free.fr> - 2018-10-25 20:20 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-25 22:50 +0200
Re: ntp problem in broadcastclients Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-25 23:00 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-25 23:40 +0200
Re: ntp problem in broadcastclients Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-26 14:30 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-26 15:40 +0200
Re: ntp problem in broadcastclients Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-26 16:00 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-26 16:40 +0200
Re: ntp problem in broadcastclients Curt <curty@free.fr> - 2018-10-26 15:10 +0200
Re: ntp problem in broadcastclients Gene Heskett <gheskett@shentel.net> - 2018-10-26 15:50 +0200
Re: ntp problem in broadcastclients Michael Stone <mstone@debian.org> - 2018-10-26 16:30 +0200
csiph-web