Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Jul 2007 09:07:16 +0200
From:      "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: ntpd just sits there and does nothing
Message-ID:  <46A453A4.90008@gmx.de>
In-Reply-To: <20070719192749.GG1141@turion.vk2pj.dyndns.org>
References:  <469F9A85.4090209@gmx.de> <20070719192749.GG1141@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
My original intention was just to say that openntpd works just out of the box,
while ntpd doesn't. And since openntpd works fine for me, I am not really
interested in resolving this. Anyway since so many of you seem to be, here is
the requested data:

> ntp.conf

server 0.de.pool.ntp.org minpoll 4 maxpoll 8
server 1.de.pool.ntp.org minpoll 4 maxpoll 8
server 2.de.pool.ntp.org minpoll 4 maxpoll 8
server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8
server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8
server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8
server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8

restrict default ignore
restrict 127.0.0.1

> ntpdc -p -c kerni -c loopi -c sysi -c syss

     remote           local      st poll reach  delay   offset    disp
=======================================================================
=time.as-compute 192.168.1.12    16  256    0 0.00000  0.000000 0.00000
=mail.syncronisa 192.168.1.12    16  256    0 0.00000  0.000000 0.00000
=proxy1.rz.uni-k 192.168.1.12    16  256    0 0.00000  0.000000 0.00000
=proxy2.rz.uni-k 192.168.1.12    16  256    0 0.00000  0.000000 0.00000
=proxy3.rz.uni-k 192.168.1.12    16  256    0 0.00000  0.000000 0.00000
=proxy4.rz.uni-k 192.168.1.12    16  256    0 0.00000  0.000000 0.00000
=crux.pmsf.net   192.168.1.12    16  256    0 0.00000  0.000000 0.00000
pll offset:           0 s
pll frequency:        0.000 ppm
maximum error:        0.365516 s
estimated error:      1.6e-05 s
status:               2001  pll nano
pll time constant:    0
precision:            1e-09 s
frequency tolerance:  496 ppm
offset:               0.000000 s
frequency:            0.000 ppm
poll adjust:          0
watchdog timer:       730 s
system peer:          0.0.0.0
system peer mode:     unspec
leap indicator:       11
stratum:              16
precision:            -19
root distance:        0.00000 s
root dispersion:      0.01094 s
reference ID:         [73.78.73.84]
reference time:       00000000.00000000  Thu, Feb  7 2036  7:28:16.000
system flags:         auth monitor ntp kernel stats
jitter:               0.000000 s
stability:            0.000 ppm
broadcastdelay:       0.003998 s
authdelay:            0.000000 s
time since restart:     730
time since reset:       730
packets received:       87
packets processed:      0
current version:        0
previous version:       0
bad version:            0
access denied:          57
bad length or format:   0
bad authentication:     0
rate exceeded:          0

> ntpdate with -q in ntpdate_flags

# /etc/rc.d/ntpdate onestart
Setting date via ntp.
server 193.218.127.251, stratum 2, offset 0.631432, delay 0.04562
server 213.133.123.125, stratum 2, offset 0.630518, delay 0.03748
server 194.25.115.122, stratum 1, offset 0.633518, delay 0.04091
server 129.13.186.4, stratum 0, offset 0.000000, delay 0.00000
server 129.13.186.3, stratum 0, offset 0.000000, delay 0.00000
server 129.13.186.2, stratum 0, offset 0.000000, delay 0.00000
server 129.13.186.1, stratum 0, offset 0.000000, delay 0.00000
23 Jul 08:55:49 ntpdate[1772]: step time server 194.25.115.122 offset 0.633518 sec

> /usr/local/sbin/ntpd -sd # This is openntpd

ntp engine ready
reply from 84.16.235.165: offset 0.573124 delay 0.011219, next query 8s
reply from 87.106.95.189: offset 0.573368 delay 0.014235, next query 8s
reply from 212.112.228.242: offset 0.574221 delay 0.014708, next query 7s
reply from 88.198.8.101: offset 0.573796 delay 0.015175, next query 6s
reply from 212.77.176.178: offset 0.574222 delay 0.016076, next query 5s
reply from 195.179.15.118: offset 0.541673 delay 0.022011, next query 5s
reply from 85.214.23.162: offset 0.568205 delay 0.022973, next query 9s
reply from 194.77.75.99: offset 0.573878 delay 0.033467, next query 8s
reply from 212.77.176.178: offset 0.570650 delay 0.014009, next query 7s
reply from 195.179.15.118: offset 0.537944 delay 0.020095, next query 5s
reply from 88.198.8.101: offset 0.570179 delay 0.013163, next query 9s
reply from 84.16.235.165: offset 0.568732 delay 0.009621, next query 6s
reply from 212.112.228.242: offset 0.569989 delay 0.013116, next query 5s
reply from 87.106.95.189: offset 0.568727 delay 0.013139, next query 6s
reply from 194.77.75.99: offset 0.570201 delay 0.029342, next query 6s
reply from 85.214.23.162: offset 0.562845 delay 0.021890, next query 9s
reply from 195.179.15.118: offset 0.536313 delay 0.021833, next query 7s
reply from 212.112.228.242: offset 0.567116 delay 0.012397, next query 7s
reply from 212.77.176.178: offset 0.567040 delay 0.014119, next query 7s
reply from 84.16.235.165: offset 0.565892 delay 0.010525, next query 6s
no reply from 129.13.186.4 received in time, next query 610s
no reply from 129.13.186.3 received in time, next query 607s
no reply from 129.13.186.2 received in time, next query 624s
no reply from 129.13.186.1 received in time, next query 600s
reply from 87.106.95.189: offset 0.565603 delay 0.013103, next query 7s
reply from 194.77.75.99: offset 0.564807 delay 0.031786, next query 8s
reply from 88.198.8.101: offset 0.565200 delay 0.013461, next query 8s
peer 195.179.15.118 now valid
reply from 195.179.15.118: offset 0.531713 delay 0.019114, next query 6s
reply from 85.214.23.162: offset 0.558348 delay 0.022025, next query 8s
peer 84.16.235.165 now valid
reply from 84.16.235.165: offset 0.561778 delay 0.012217, next query 7s
peer 212.112.228.242 now valid
reply from 212.112.228.242: offset 0.561791 delay 0.019195, next query 6s
peer 212.77.176.178 now valid
reply from 212.77.176.178: offset 0.561985 delay 0.019901, next query 6s
peer 87.106.95.189 now valid
reply from 87.106.95.189: offset 0.562176 delay 0.013402, next query 9s
peer 194.77.75.99 now valid
reply from 194.77.75.99: offset 0.562401 delay 0.028594, next query 8s
peer 88.198.8.101 now valid
reply from 88.198.8.101: offset 0.561575 delay 0.012842, next query 8s
reply from 195.179.15.118: offset 0.528773 delay 0.019426, next query 5s
reply from 212.112.228.242: offset 0.560407 delay 0.012300, next query 9s
reply from 212.77.176.178: offset 0.560345 delay 0.013367, next query 5s
reply from 84.16.235.165: offset 0.558545 delay 0.011407, next query 5s
peer 85.214.23.162 now valid
reply from 85.214.23.162: offset 0.554267 delay 0.021485, next query 9s
reply from 195.179.15.118: offset 0.526468 delay 0.019568, next query 5s
reply from 212.77.176.178: offset 0.557854 delay 0.013748, next query 5s
reply from 87.106.95.189: offset 0.557904 delay 0.014053, next query 7s
reply from 194.77.75.99: offset 0.559026 delay 0.029746, next query 6s
reply from 84.16.235.165: offset 0.556647 delay 0.009941, next query 8s
reply from 88.198.8.101: offset 0.557425 delay 0.013203, next query 5s
reply from 195.179.15.118: offset 0.523956 delay 0.019786, next query 30s
reply from 212.112.228.242: offset 0.555780 delay 0.012275, next query 9s
reply from 212.77.176.178: offset 0.555285 delay 0.013967, next query 33s
reply from 85.214.23.162: offset 0.550332 delay 0.022219, next query 8s
reply from 88.198.8.101: offset 0.555151 delay 0.012796, next query 7s
reply from 194.77.75.99: offset 0.555651 delay 0.029299, next query 9s
reply from 87.106.95.189: offset 0.554548 delay 0.014033, next query 6s
reply from 84.16.235.165: offset 0.552542 delay 0.010245, next query 32s
reply from 88.198.8.101: offset 0.551669 delay 0.012910, next query 33s
reply from 212.112.228.242: offset 0.551312 delay 0.012952, next query 31s
reply from 87.106.95.189: offset 0.550479 delay 0.014415, next query 33s
reply from 85.214.23.162: offset 0.546266 delay 0.022961, next query 9s
reply from 194.77.75.99: offset 0.551037 delay 0.029102, next query 33s
reply from 85.214.23.162: offset 0.542017 delay 0.022399, next query 32s
reply from 195.179.15.118: offset 0.509119 delay 0.019754, next query 32s
reply from 212.77.176.178: offset 0.539421 delay 0.013574, next query 34s
reply from 84.16.235.165: offset 0.537270 delay 0.010030, next query 31s
reply from 212.112.228.242: offset 0.535541 delay 0.012949, next query 33s
reply from 88.198.8.101: offset 0.535249 delay 0.012831, next query 30s
reply from 87.106.95.189: offset 0.534487 delay 0.013206, next query 32s
reply from 194.77.75.99: offset 0.535031 delay 0.029762, next query 31s
reply from 85.214.23.162: offset 0.525685 delay 0.023148, next query 32s
adjusting local clock by 0.558063s



As you can see some of the servers don't reply as is expected, because which
servers are available depends on where I am. However some (in this case the
de.pool.ntp.org servers) do reply. Only ntpd isn't able to hear them. As I
mentioned before. I don't have access to the first firewall, so I cannot
forward any ports. The picture is the same on my machine that acts as 2nd
firewall, so the problem lies with the configuration of the first.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46A453A4.90008>