Re: ntp daemon.
On Wed, Jan 18, 2012 at 03:55:16PM -0600, Stan Hoeppner wrote:
> On 1/18/2012 3:34 PM, Joey L wrote:
>
> > remote refid st t when poll reach delay offset jitter
> > ==============================================================================
> > 199.4.29.166 .INIT. 16 u - 64 0 0.000 0.000 0.000
> > name1.glorb.com .INIT. 16 u - 64 0 0.000 0.000 0.000
> > 173.244.211.10. .INIT. 16 u - 64 0 0.000 0.000 0.000
> > clock.xmission. .INIT. 16 u - 64 0 0.000 0.000 0.000
> > ntp.sunflower.c .INIT. 16 u - 64 0 0.000 0.000 0.000
> > ntp.cox.net .INIT. 16 u - 64 0 0.000 0.000 0.000
> > guinness.mcguyv .INIT. 16 u - 64 0 0.000 0.000 0.000
> > barricade.rack9 .INIT. 16 u - 64 0 0.000 0.000 0.000
>
> > all looks normal.
>
> That's because you don't know what "normal" should look like:
>
> remote refid st t when poll reach delay offset jitter
> ==============================================================================
> +navobs1.wustl.e .GPS. 1 u 104 128 377 48.924 -0.745 3.540
> *ntp.okstate.edu .USNO. 1 u 88 128 377 45.726 -0.294 1.259
> +tick.uh.edu .GPS. 1 u 43 128 377 45.574 -0.527 5.165
>
>
> See all of your columns with zeros? See mine don't have zeros, but actual data? It seems your ntpd is failing to contact the remote ntp servers. While watching iftop, stop and start ntpd. You should see connections going out to the remote ntp servers. We need to confirm that.
>
It can take a few minutes of ntpd running before you get the + and *
marks in the "remote" column, like Stan has. I don't remember exactly
what they mean, but it's something along the lines of your ntp daemon
having established a "link" with those remote ntp servers. I'm not sure
if that accounts for all the zeros in the other columns, though.
-Rob
Reply to: