dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed

Hazy Arc

Greenwood, SC
·Embarq Now Centu..

Ubuntu NTP Server Stuck at Stratum 16?

We use an Ubuntu installation as the time server for our local network. All was working fine until a few days ago, when a glitch in our content filter was blocking the ability for our time server to sync with external sources. We fixed the problem with that and the time is syncing, but even after 48 hours, the box still considers itself as a stratum 16, which means our other machines will not sync with it.

Here's the output of ntpq -c lpeer:

netadmin@Timesync:~$ ntpq -c lpeer
     remote           refid      st t when poll reach   delay   offset  jitter
 Timesync        .BCST.          16 u    -   64    0    0.000    0.000   0.001
+fairy.mattnordh  2 u  633 1024  377   17.227   -0.086   0.104
+twist.pathennes        2 u  667 1024  377   28.542    1.313   0.987
-vimo.dorui.net   2 u 1693 1024  376   29.278    1.434   0.266
*ntp2.eecs.wsu.e .GPS.            1 u  734 1024  377   94.854    0.511   2.746
-louie.udel.edu   2 u  659 1024  377   28.961   -2.346   2.619
-otc2.psu.edu     2 u  670 1024  377   50.277    3.215   0.231
-dns3.cit.cornel     2 u  654 1024  377   39.155   -2.245   0.599

Is there anything else we are missing?

Charlotte, NC
You sure it is getting time?

What does ntp.drift say?

Bounced ntpd?

How bad is the current time on the system vs real time?

Hazy Arc

Greenwood, SC
We've bounced NTPD and rebooted the server several times. The time on the server is perfect. The entry in ntp.drift is 25.280

Hazy Arc

Greenwood, SC
reply to Hazy Arc
Problem solved. Apparently broadcast stratums are supposed to be 16, which is normal. Our server was actually working - the two machines I was using to test sync were the problem (chalk up another to crappy Windoze NTP/W32Time).