[ntp:questions] Default config on Ubuntu doesn't work as client

Michael B Allen miallen at ioplex.com
Mon Mar 10 16:15:15 UTC 2008


On 10 Mar 2008 12:08:53 GMT
Steve Kostecke <kostecke at ntp.org> wrote:

> On 2008-03-10, Michael B Allen <miallen at ioplex.com> wrote:
> > Harlan Stenn <stenn at ntp.org> wrote:
> >
> >> Michael B Allen <miallen at ioplex.com> writes:
> >> 
> >> The default config is inlined below. The only thing I changed was
> >> server 192.168.2.15' which is the time server (which I know
> >> works).
> >> 
> >> I think you need a "restrict" line for 192.168.2.15 .
> >> 
> >> See http://support.ntp.org/Support/AccessRestrictions .
> >
> > Adding 'restrict 192.168.2.15' had no effect after 5 minutes and counting.
> 
> That's because there was nothing in your restrict lines blocking time
> service. If you want to know more about how the restrict lines work
> please take the time to read Support.AccessRestrictions.
> 
> > Below is a request and response if that helps in the diagnosis.
> 
> The output of 'ntpq -pcrv' is what we need to see.
> 
> BTW: You should append 'iburst' to your server lines to speed up initial sync
> from a bit over 5 minutes to a bit less than 20 seconds (assuming no other
> issues exist).

Hi Steve,

Output of ntpq:

# ntpq -pcrv
assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
version="ntpd 4.2.4p0 at 1.1472-o Thu Oct  4 20:58:45 UTC 2007 (1)",
processor="i686", system="Linux/2.6.22-14-server", leap=11, stratum=16,
precision=-20, rootdelay=0.000, rootdispersion=0.210, peer=0,
refid=INIT, reftime=00000000.00000000  Thu, Feb  7 2036  1:28:16.000,
poll=6, clock=cb7fdd9b.a61cc7fd  Mon, Mar 10 2008 12:17:31.648, state=1,
offset=0.000, frequency=0.000, jitter=0.001, noise=0.001,
stability=0.000, tai=0
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 nano.foo.net    69.31.13.210     3 u   13   64    1    0.364  -420416   0.001

And here's syslog on startup:

Mar 10 12:17:17 ls3 ntpd[5923]: ntpd 4.2.4p0 at 1.1472-o Thu Oct  4 20:58:45 UTC 2007 (1)
Mar 10 12:17:17 ls3 ntpd[5924]: precision = 1.000 usec
Mar 10 12:17:17 ls3 ntpd[5924]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Mar 10 12:17:17 ls3 ntpd[5924]: Listening on interface #1 wildcard, ::#123 Disabled
Mar 10 12:17:17 ls3 ntpd[5924]: Listening on interface #2 lo, ::1#123 Enabled
Mar 10 12:17:17 ls3 ntpd[5924]: Listening on interface #3 eth0, fe80::20c:29ff:fe82:21c2#123 Enabled
Mar 10 12:17:17 ls3 ntpd[5924]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
Mar 10 12:17:17 ls3 ntpd[5924]: Listening on interface #5 eth0, 192.168.2.23#123 Enabled
Mar 10 12:17:17 ls3 ntpd[5924]: kernel time sync status 0040
Mar 10 12:17:17 ls3 ntpd[5924]: frequency initialized 0.000 PPM from /var/lib/ntp/ntp.drift

Note: I removed the insignificant restrict line and restarted ntpd.

Mike




More information about the questions mailing list