[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dual-core system will not create NTP peers



Alex Samad wrote:

ntpdc -p

After leaving this run for a couple of hours, I get this set of information, which is actually rather horrifying even to my untrained eye:

# ntpq -c as ; ntpdc -c peers -c sysinfo

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 37850  9024   yes   yes  none    reject   reachable  2
  2 37851  9024   yes   yes  none    reject   reachable  2
  3 37852  9024   yes   yes  none    reject   reachable  2
  4 37853  9024   yes   yes  none    reject   reachable  2
  5 37854  9024   yes   yes  none    reject   reachable  2
  6 37855  9024   yes   yes  none    reject   reachable  2

     remote           local      st poll reach  delay   offset    disp
=======================================================================
=mirror.web-ster 172.28.54.162    2   64  377 0.06209 243.41326 0.04036
=patbox.patrickd 172.28.54.162    2   64  377 0.06819 237.67744 0.05783
=druid.storyinme 172.28.54.162    2   64  277 0.03696 239.99789 0.04701
=ntp-1.gw.uiuc.e 172.28.54.162    2   64  377 0.01086 242.87614 0.04802
=ntp-2.gw.uiuc.e 172.28.54.162    2   64  377 0.01221 244.02863 0.03761
=64.73.32.134    172.28.54.162    2   64  377 0.01271 240.80815 0.05812

system peer:          0.0.0.0
system peer mode:     unspec
leap indicator:       11
stratum:              16
precision:            -20
root distance:        0.00000 s
root dispersion:      0.14473 s
reference ID:         [83.84.69.80]
reference time:       00000000.00000000  Thu, Feb  7 2036  0:28:16.000
system flags:         auth monitor ntp kernel stats
jitter:               0.332382 s
stability:            0.000 ppm
broadcastdelay:       0.003998 s
authdelay:            0.000000 s

I'm attempting the "use between four and seven ntp servers" method out of the US pool of ntp.org, as well as a couple of local machines, one of which is marked "prefer."

I'm using the Debian stable NTP, not that it's helping.

By way of contrast, here's what this same dump looks like on a single-processor AMD AthlonXP on the same local network:

# ntpq -c as ; ntpdc -c peers -c sysinfo

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 41784  9614   yes   yes  none  sys.peer   reachable  1

     remote           local      st poll reach  delay   offset    disp
=======================================================================
*ntp-1.gw.uiuc.e 172.28.54.160    2  256  377 0.01498 -0.007047 0.11313

system peer:          ntp-1.gw.uiuc.edu
system peer mode:     client
leap indicator:       00
stratum:              3
precision:            -20
root distance:        0.07011 s
root dispersion:      0.05965 s
reference ID:         [130.126.24.24]
reference time:       cb657ba1.e7d162e6  Tue, Feb 19 2008 10:00:33.905
system flags:         auth monitor ntp kernel stats
jitter:               0.004196 s
stability:            0.000 ppm
broadcastdelay:       0.003998 s
authdelay:            0.000000 s

In other words, it's not the firewall. And since it does sync up once it's not a problem with the conf file. It's something else, which I haven't been able to find in well over 10 days...

--
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
 "The aim of the middle manager is slightly more honest than the
  nobility, since former desire only to impress the oppressors
  while not depressing those who avoid oppression" -- Larry Tomko (ca 1992)


Reply to: