frank dreyfus

Hi,

I'm having trouble getting ntpd to sync with ANY external time server. I
have 12 or so servers in /etc/ntp.conf and ALL of them are "reject"ed.

I just upgraded to 2007. It had been working under 2006 but I haven't
double checked in quite a while.

I have udp 123 open in both directions. There are no indications in
syslog of any firewall issues related to port 123.

Here are the results of ntpq/peers and ntpq/assoc:

ntpq> peer
remote refid st t when poll reach delay offset
jitter
================================================== =======================
=====
*LOCAL(0) LOCAL(0) 10 l 60 64 377 0.000 0.000
0.001
s5.loopia.se .INIT. 16 u - 1024 0 0.000 0.000
4000.00
avi-lis.gw.ligh .CDMA. 1 u 837 1024 77 31.509 -236.07
1672.59
cudns.cit.corne 192.5.41.40 2 u 836 1024 77 44.616 -227.49
1683.61
hickory.cc.colu 128.59.39.48 2 u 832 1024 77 33.462 -238.04
1682.20
cs.columbia.edu 204.123.2.5 2 u 772 1024 77 30.915 -533.71
1609.15
mirror.packetsc 198.60.22.240 2 u 834 1024 77 60.946 -251.42
1678.04
netmon.rseng.ne 66.187.224.4 2 u 831 1024 77 67.167 -553.29
1503.45
srv1.dvmed.net 202.191.97.131 3 u 825 1024 77 70.141 -271.18
1673.54
dns01.flame.org 198.60.22.240 2 u 827 1024 77 91.635 -274.33
1668.39
radon.tilderoot 33.206.74.123 3 u 828 1024 77 114.404 -535.19
1506.24
ohno.mrbill.net 128.83.185.40 3 u 828 1024 77 69.101 -51.905
1872.21
fry.gwi.net .INIT. 16 u - 512 0 0.000 0.000
4000.00
ns2.medbanner.c 192.43.244.18 2 u 828 1024 77 83.486 -1003.3
1345.52


ntpq> assoc
ind assID status conf reach auth condition last_event cnt
================================================== =========
1 27564 9614 yes yes none sys.peer reachable 1
2 27565 8000 yes yes none reject
3 27566 b014 yes yes none reject reachable 1
4 27567 b014 yes yes none reject reachable 1
5 27568 b014 yes yes none reject reachable 1
6 27569 b014 yes yes none reject reachable 1
7 27570 b014 yes yes none reject reachable 1
8 27571 b014 yes yes none reject reachable 1
9 27572 b014 yes yes none reject reachable 1
10 27573 b014 yes yes none reject reachable 1
11 27574 b014 yes yes none reject reachable 1
12 27575 b014 yes yes none reject reachable 1
13 27576 8000 yes yes none reject
14 27577 b014 yes yes none reject reachable 1

I don't know what reach=77 means. Could it be the same as reject?

It seems that the delay, offset and jitter values are all quite high.

My system time is within a minute of the correct time.

Yet I've chosen some local tier 2 servers.

Any idea what's wrong?

Thanks,

Frank

bit twister

Hmmm, I have only one time server, time.windows.com on my firewall
and just block all incomming attempts. Works for me.

$ cat /etc/release
Mandriva Linux release 2007.0 (Official) for i586

I went into the Mandriva Control Center, System, date time
entered time.windows.com and click use time server, worked like a charm.

frank dreyfus

Hi Bit,

I tried time.windows.com but it fails to connect to that site when I
start ntpd. That may just be a temporary issue with the MS server.

When I use my other time sites startup doesn't fail to connect but ntp
won't sync with any of them (same problem as before).

I didn't know you could set up /etc/ntp.conf via the control panel.
Thanks for that. It makes life easier.
But my problem remains :>(

Thanks,

Frank

bit twister

Hmmm.

Shutting down ntpd: [ OK ]
Syncing time for ntpd: Looking for host time.windows.com and service ntp
host found : time.windows.com
[ OK ]
Starting ntpd: [ OK ]
Shutting down ntpd: [ OK ]
Looking for host time.windows.com and service ntp
host found : time.windows.com
6 Nov 15:15:09 ntpdate[29127]:
adjust time server 207.46.130.100 offset 0.001224 sec
Syncing time for ntpd: Looking for host time.windows.com and service ntp
host found : time.windows.com
[ OK ]
Starting ntpd: [ OK ]


Yes, sometimes gui wipes out config file, inserts new data and clears
up typos and old values.

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 time.windows.com
#server pool.ntp.org
#server pool.ntp.org
#server pool.ntp.org

#
# 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
----------------------------------------------------------

# cat /etc/ntp/drift
68.149

----------------------------------------------------------
cat /etc/ntp/keys
#
# PLEASE DO NOT USE THE DEFAULT VALUES HERE.
#
#65535 M akey
#1 M pass

----------------------------------------------------------

# cat /etc/ntp/step-tickers
time.windows.com

dave pickles

"Reach" is a byte value, expressed in octal, showing the results of the
last eight polls for that server. If a valid time was obtained for all
eight then the Reach would show 377. Your value of 77 simply means that
the last six polls were OK; maybe you hadn't been running ntp for long
enough to get eight polls.


NTP has rejected all of your external sources and has fallen back on its
local clock. The jitter value is probably to blame as it is extremely
high for all of them. Did you have a download maxing out your internet
connection?
--
Dave

bit twister

Doesn't system time need to be pretty close for sync?

frank dreyfus

Hmmm is right :>)

Here's my stuff. Note that even though I set time.microsoft.com as the
first server it doesn't load.


Shutting down ntpd: [ OK ]

Syncing time for ntpd: Looking for host 0.us.pool.ntp.org and service ntp
host found : time.awin.com
Looking for host 1.us.pool.ntp.org and service ntp
host found : vitruvian.fmt.firsttracks.net
Looking for host 2.us.pool.ntp.org and service ntp
host found : timeclock.imageman.com
[ OK ]
Starting ntpd: [ OK ]

[ junk]# cat /etc/ntp.conf
# comment lines removed for brevity
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10

server time.microsoft.com
server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server clock.nyc.he.net
server ntp0.cornell.edu
server sundial.columbia.edu
server timex.cs.columbia.edu

driftfile /etc/ntp/drift
multicastclient # listen on default 224.0.1.1
broadcastdelay 0.008

[ junk]# cat /etc/ntp/drift -235.771
ntpq> peer
remote refid st t when poll reach delay offset
jitter
================================================== =========================
===
*LOCAL(0) LOCAL(0) 10 l 22 64 377 0.000 0.000
0.001
time.awin.com 209.81.9.7 2 u 587 1024 377 122.390 -19837.
3153.16
vitruvian.fmt.f 216.218.254.202 2 u 580 1024 377 104.933 -19863.
3144.30
timeclock.image .PPS. 1 u 578 1024 377 79.084 -19862.
3140.82
avi-lis.gw.ligh .CDMA. 1 u 577 1024 377 36.436 -19868.
3142.06
cudns.cit.corne 192.5.41.40 2 u 569 1024 377 48.932 -19909.
3153.21
hickory.cc.colu 128.59.39.48 2 u 580 1024 377 39.356 -19862.
3138.59
cs.columbia.edu 204.123.2.5 2 u 568 1024 377 38.651 -19911. 3152.35
ntpq> assoc
ind assID status conf reach auth condition last_event cnt
================================================== =========
1 35428 9614 yes yes none sys.peer reachable 1
2 35429 b014 yes yes none reject reachable 1
3 35430 b014 yes yes none reject reachable 1
4 35431 b014 yes yes none reject reachable 1
5 35432 b014 yes yes none reject reachable 1
6 35433 b014 yes yes none reject reachable 1
7 35434 b014 yes yes none reject reachable 1
8 35435 b014 yes yes none reject reachable 1

frank dreyfus

Hi Dave,

That must be it but I don't understand why that should be.

I'm currently seeing about 20KB/s up and 1KB/s down. I'm controlling the
LM host via VNC so that's probably the reason for the upload rate being
higher than the download rate. Other than that, nothing else is running.

Thanks for your help,

Frank

frank dreyfus

Yes. My system time is within a minute of the sync time.

Thanks,

Frank

bit twister

$ host time.microsoft.com
Host time.microsoft.com not found: 3(NXDOMAIN)
[bittwister@wb ~]$ host time.microsoft.com
Host time.microsoft.com not found: 3(NXDOMAIN)

$ host time.windows.com
time.windows.com has address 207.46.130.100
time.windows.com has address 207.46.232.189