I've been doing some network upgrades, and my ntpd was working pretty well and
suddenly its acting very weird. From what I can see, all the network
firewall rules are still in place, and a trace shows packets going out and
coming back (both from me as a client, and me as a server to others). But I
can't sync up, and the clock is loosing massive amounts of time. Overnight,
the system clock lost 10 minutes. I've tried restarting ntpd, seeing if one
of my piers is off, etc, but can't figure the problem. Anyone seen anything
like this? I'm on Mandriva 2009.0
The only real change I've been trying to make to my system is I added another
interface to setup some firewall rules for a wireless net I'm trying to
setup. According to netstat, ntpd is listening on all interfaces.
netstat -a|grep ntp
udp 0 0 216.160.0.218:ntp *:*
udp 0 0 192.168.1.1:ntp *:*
udp 0 0 murdock.foddy.home:ntp *:*
udp 0 0 192.168.0.2:ntp *:*
udp 0 0 murdock.foddy.home:ntp *:*
udp 0 0 *:ntp *:*
udp 0 0 fe80::290:27ff:fe0e:ntp *:*
udp 0 0 fe80::202:b3ff:fe90:ntp *:*
udp 0 0 ::1:ntp *:*
udp 0 0 fe80::2c0:4fff:fe79:ntp *:*
udp 0 0 *:ntp *:*
216.160.0.218 is the public interface (ppp0), the others are private nets.
ntpd -u ntp:ntp -p /var/run/ntpd.pid
cat /etc/ntp.conf
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
#
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
server ntp3.cs.wisc.edu #stratum 2
server ntp.sycharlutheran.org #stratum 2
server clock.nyc.he.net #stratum 1
#
#
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
#
driftfile /etc/ntp/drift
multicastclient # listen on default 224.0.1.1
broadcastdelay 0.008
#
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will.
#
#keys /etc/ntp/keys
#trustedkey 65535
#requestkey 65535
#controlkey 65535
#restrict default ignore
restrict 127.0.0.1
restrict default kod nomodify notrap nopeer noquery
restrict ntp.visi.com nomodify
restrict ntp3.cs.wisc.edu nomodify
restrict ntp.sycharlutheran.org nomodify
restrict ntp1.sjbcom.com nomodify
restrict clock.nyc.he.net nomodify
After only 20 minutes, its many seconds off already.
ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 .LOCL. 10 l 32 64 377 0.000 0.000 0.977
128.105.37.11 128.105.201.11 2 u 26 256 377 64.117 10503.0 3750.77
173.16.32.174 99.150.184.201 2 u 18 256 377 58.125 10599.0 3771.55
209.51.161.238 .CDMA. 1 u 16 256 377 68.408 14408.1 6707.28
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
