Re: ntpd not keeping time

To: Alvin Oga <aoga@Maggie.Linux-Consulting.com>
Cc: debian-user@lists.debian.org
Subject: Re: ntpd not keeping time
From: debian@clouded.org
Date: Wed, 29 Jan 2003 17:59:47 -0500 (EST)
Message-id: <[🔎] Pine.LNX.4.44.0301291638190.15864-100000@flux.clouded.org>
In-reply-to: <[🔎] Pine.LNX.3.96.1030129132115.18410C-100000@Maggie.Linux-Consulting.com>

Enabling the logfile in ntp.conf doesn't show anything special, just the
same start/stop stuff from daemon.log:

29 Jan 16:38:15 ntpd[23209]: frequency initialized 0.000 from /var/lib/ntp/ntp.drift
29 Jan 16:38:15 ntpd[23210]: signal_no_reset: signal 17 had flags 4000000
29 Jan 16:38:28 ntpd[23209]: ntpd exiting on signal 15


Here are the outputs of those commands:

# ntpdate -udb clock.psu.edu
29 Jan 16:38:39 ntpdate[23213]: ntpdate 4.1.0 Mon Mar 25 23:39:50 UTC 2002 (2)
transmit(128.118.25.3)
transmit(128.118.25.3)
transmit(128.118.25.3)
transmit(128.118.25.3)
transmit(128.118.25.3)
server 128.118.25.3, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036  1:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  1:28:16.000
transmit timestamp:  c1e2c862.691c6d1e  Wed, Jan 29 2003 16:38:42.410
filter delay:  0.00000  0.00000  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

29 Jan 16:38:43 ntpdate[23213]: no server suitable for synchronization found


# ntptrace -dv clock.psu.edu
DoTransmit(128.118.25.3)
DoTransmit to 128.118.25.3
timeout
DoTransmit(128.118.25.3)
DoTransmit to 128.118.25.3
timeout
DoTransmit(128.118.25.3)
DoTransmit to 128.118.25.3
timeout
DoTransmit(128.118.25.3)
DoTransmit to 128.118.25.3
timeout
DoTransmit(128.118.25.3)
DoTransmit to 128.118.25.3
timeout
otc2.psu.edu:   *Timeout*



And here's just plain 'ole ntpdate:

# ntpdate clock.psu.edu
29 Jan 16:39:56 ntpdate[23274]: step time server 128.118.25.3 offset -55.557580 sec




So it looks like running ntpdate without options works, while running with
those options does not. I've double-checked the firewall ruleset and it is
exactly the same as other boxes with ntp running just fine.

For some reason, though, on the problem box I found this:
Jan 29 16:40:30 haze kernel: Packet log: input DENY eth0 PROTO=17 128.118.25.3:123 64.61.10.115:32962 L=76 S=0

So I changed the rules for ntp hosts to allow udp:123 to anywhere and now
the above commands return this:


# ntpdate -udb clock.psu.edu
29 Jan 17:41:21 ntpdate[24452]: ntpdate 4.1.0 Mon Mar 25 23:39:50 UTC 2002 (2)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
server 128.118.25.3, port 123
stratum 2, precision -16, leap 00, trust 000
refid [192.5.41.209], delay 0.04216, dispersion 0.00023
transmitted 4, in filter 4
reference time:    c1e2d574.ef5cf249  Wed, Jan 29 2003 17:34:28.935
originate timestamp: c1e2d6f3.a58ab92c  Wed, Jan 29 2003 17:40:51.646
transmit timestamp:  c1e2d711.43e64f54  Wed, Jan 29 2003 17:41:21.265
filter delay:  0.04216  0.04269  0.04330  0.04219
         0.00000  0.00000  0.00000  0.00000
filter offset: -29.6269 -29.6268 -29.6273 -29.6272
         0.000000 0.000000 0.000000 0.000000
delay 0.04216, dispersion 0.00023
offset -29.626950

29 Jan 17:41:21 ntpdate[24452]: step time server 128.118.25.3 offset -29.626950 sec



# ntptrace -dv clock.psu.edu
DoTransmit(128.118.25.3)
DoTransmit to 128.118.25.3
ReceiveBuf(128.118.25.3, 128.118.25.3)
server 128.118.25.3, port 123
stratum 2, precision -16, leap 00
refid ntp2.usno.navy.mil delay 0.01788, dispersion 0.00000 offset -29.872159
rootdelay 0.03152, rootdispersion 0.04436, synch dist 0.06012
reference time:      c1e2d574.ef5cf249  Wed, Jan 29 2003 17:34:28.935
originate timestamp: c1e2d711.b211ec91  Wed, Jan 29 2003 17:41:21.695
transmit timestamp:  c1e2d72f.8efc9bc7  Wed, Jan 29 2003 17:41:51.558

DoTransmit(192.5.41.209)
DoTransmit to 192.5.41.209
timeout
DoTransmit(192.5.41.209)
DoTransmit to 192.5.41.209
timeout
DoTransmit(192.5.41.209)
DoTransmit to 192.5.41.209
timeout
DoTransmit(192.5.41.209)
DoTransmit to 192.5.41.209
timeout
DoTransmit(192.5.41.209)
DoTransmit to 192.5.41.209
timeout
ntp2.usno.navy.mil:     *Timeout*




So now nothing is being blocked by the firewall (except for
ntp2.usno.navy.mil) and ntp still isn't sync'ing time on the box. I even
tried disabling the firewall for a few minutes, still no time sync. In a
few hours the clock has managed to creep ahead by 30 seconds.

I'm wondering if something's up with the clock on the motherboard, some
freaky incompatibility with the way ntpd updates time or something. It's a
Gigabyte GA-7VKML, in case anyone's curious. Just a possibility.

Or maybe when ntp calculates the "drift" or how long it takes to get a
response from the time server, something is causing it to miscalculate
each time which could be causing it to slowly increase it's adjustments.

Or maybe I'm just going wild with speculation. :)



On Wed, 29 Jan 2003, Alvin Oga wrote:

>
> hi ya
>
> turn on logfile in your ntp.conf
>
> -- run some ntptrace and ntpdate commands
>    and post its output
>
>
> ntpdate -udb time.apple.com
> 	( use your servers from your ntp.conf file )
>
> ntptrace -dv time.apple.com
>
> more ntp jibberish ( urls  to other docs too )
> 	http://www.Linux-Consulting.com/NTP/NTP.Commands.txt
>
> c ya
> alvin
>
> On Wed, 29 Jan 2003 debian@clouded.org wrote:
>
> > Hello all. I've got this weird problem with ntpd. Up until now I've never
> > had ntpd fail me. But on this one box I've got the clock speeding up by 30
> > minutes each day. I've got ntpd installed and configured properly with
> > working ntp servers. In fact, ntpdate sets the clock properly, but ntpd is
> > failing to keep the clock in sync with the ntp servers.
> >
> > I've tried purging ntp & ntp-simple and reinstalling, but that didn't
> > help. There are no errors in any logs in /var/log. Any ideas or
> > suggestions would be greatly appreciated. Thanks.
> >
> >
> > # uname -a
> > Linux haze 2.4.18 #1 SMP Fri Dec 27 00:01:51 EST 2002 i686 AMD Athlon(tm)
> > Processor AuthenticAMD GNU/Linux
> >
> >
> > # dpkg -l|grep ntp
> > ii  ntp            4.1.0-8        Daemon and utilities for full NTP v4 timekee
> > ii  ntp-simple     4.1.0-8        NTP v4 daemon for simple systems.
> > ii  ntpdate        4.1.0-8        The ntpdate client for setting system time f
> >
> >
> > # cat /etc/ntp.conf
> > # /etc/ntp.conf, configuration for ntpd
> >
> > # ntpd will use syslog() if logfile is not defined
> > #logfile /var/log/ntpd
> >
> > driftfile /var/lib/ntp/ntp.drift
> > statsdir /var/log/ntpstats/
> >
> > statistics loopstats peerstats clockstats
> > filegen loopstats file loopstats type day enable
> > filegen peerstats file peerstats type day enable
> > filegen clockstats file clockstats type day enable
> >
> > ### lines starting 'server' are auto generated,
> > ### use dpkg-reconfigure to modify those lines.
> >
> > server timex.cs.columbia.edu
> > server clock.psu.edu
> > server bonehed.lcs.mit.edu
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >
>

Reply to:

Follow-Ups:
- Re: ntpd not keeping time -fw
  - From: Alvin Oga <aoga@Maggie.Linux-Consulting.com>

References:
- Re: ntpd not keeping time
  - From: Alvin Oga <aoga@Maggie.Linux-Consulting.com>

Prev by Date: Re: Mount problems
Next by Date: Re: cu program?
Previous by thread: Re: ntpd not keeping time
Next by thread: Re: ntpd not keeping time -fw
Index(es):
- Date
- Thread