[Bug 787551] Re: ntpdate 4.2.6p2 at 1.2194-o: "no server suitable for synchronization found" - works with 4.2.4p8 at 1.1612-o
Bug Watch Updater
787551 at bugs.launchpad.net
Tue Jun 14 06:58:24 UTC 2011
Launchpad has imported 10 comments from the remote bug at
http://bugs.gentoo.org/show_bug.cgi?id=329571.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2010-07-23T12:44:04+00:00 Rose-g wrote:
We have a rather slow inhouse timeserver:
root at cheetah:/home/rose(53)# ping 10.101.10.20
PING 10.101.10.20 (10.101.10.20) 56(84) bytes of data.
64 bytes from 10.101.10.20: icmp_seq=1 ttl=127 time=6.88 ms
64 bytes from 10.101.10.20: icmp_seq=2 ttl=127 time=1.22 ms
64 bytes from 10.101.10.20: icmp_seq=3 ttl=127 time=2.15 ms
64 bytes from 10.101.10.20: icmp_seq=4 ttl=127 time=0.538 ms
64 bytes from 10.101.10.20: icmp_seq=5 ttl=127 time=87.9 ms
64 bytes from 10.101.10.20: icmp_seq=6 ttl=127 time=6.77 ms
64 bytes from 10.101.10.20: icmp_seq=7 ttl=127 time=7.13 ms
64 bytes from 10.101.10.20: icmp_seq=8 ttl=127 time=1.24 ms
64 bytes from 10.101.10.20: icmp_seq=9 ttl=127 time=0.354 ms
64 bytes from 10.101.10.20: icmp_seq=10 ttl=127 time=79.5 ms
64 bytes from 10.101.10.20: icmp_seq=11 ttl=127 time=0.416 ms
64 bytes from 10.101.10.20: icmp_seq=12 ttl=127 time=0.427 ms
64 bytes from 10.101.10.20: icmp_seq=13 ttl=127 time=1.90 ms
^C
--- 10.101.10.20 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12011ms
rtt min/avg/max/mdev = 0.354/15.118/87.950/29.409 ms
Setting the system time with net-misc/ntp-4.2.6_p2 fails with:
root at cheetah:/home/rose(33)# ntpdate -v -d -d -b -u 10.101.10.20
23 Jul 12:54:11 ntpdate[813]: ntpdate 4.2.6p2 at 1.2194-o Mon Jul 19 02:43:33 UTC 2010 (1)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
10.101.10.20: Server dropped: no data
server 10.101.10.20, port 123
stratum 5, precision -17, leap 00, trust 000
refid [10.101.10.20], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: cff3f35a.029c6b63 Fri, Jul 23 2010 12:54:18.010
originate timestamp: cff3f35a.029c6b63 Fri, Jul 23 2010 12:54:18.010
transmit timestamp: cff3f35a.02f5a519 Fri, Jul 23 2010 12:54:18.011
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
23 Jul 12:54:19 ntpdate[7112]: no server suitable for synchronization
found
If I downgrade to net-misc/ntp-4.2.6_p1-r1 I can set the system time:
root at cheetah:/home/rose(35)# emerge -v1 =net-misc/ntp-4.2.6_p1-r1
...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
* IMPORTANT: 13 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
root at cheetah:/home/rose(36)# ntpdate -v -d -d -b -u 10.101.10.20
23 Jul 13:06:26 ntpdate[17815]: ntpdate 4.2.6p1 at 1.2158-o Fri Jul 23 10:59:23 UTC 2010 (1)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
server 10.101.10.20, port 123
stratum 5, precision -17, leap 00, trust 000
refid [10.101.10.20], delay 0.02599, dispersion 0.00063
transmitted 4, in filter 4
reference time: cff3f632.3c2ab5bc Fri, Jul 23 2010 13:06:26.235
originate timestamp: cff3f632.3c2ab5bc Fri, Jul 23 2010 13:06:26.235
transmit timestamp: cff3f632.40929678 Fri, Jul 23 2010 13:06:26.252
filter delay: 0.02840 0.03220 0.02599 0.02600
0.00000 0.00000 0.00000 0.00000
filter offset: -0.01843 -0.02038 -0.01740 -0.01740
0.000000 0.000000 0.000000 0.000000
delay 0.02599, dispersion 0.00063
offset -0.017409
23 Jul 13:06:26 ntpdate[17815]: step time server 10.101.10.20 offset
-0.017409 sec
If I now upgrade again ntp, setting system time fails again:
root at cheetah:/home/rose(38)# emerge -vuDN world
...
root at cheetah:/home/rose(38)# dispatch-conf
...
root at cheetah:/home/rose(52)# ntpdate -v -d -d -b -u 10.101.10.20
23 Jul 13:33:03 ntpdate[6092]: ntpdate 4.2.6p2 at 1.2194-o Fri Jul 23 11:27:06 UTC 2010 (1)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
10.101.10.20: Server dropped: no data
server 10.101.10.20, port 123
stratum 5, precision -17, leap 00, trust 000
refid [10.101.10.20], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: cff3fc75.be9b403b Fri, Jul 23 2010 13:33:09.744
originate timestamp: cff3fc75.be9b403b Fri, Jul 23 2010 13:33:09.744
transmit timestamp: cff3fc75.c877304d Fri, Jul 23 2010 13:33:09.783
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
23 Jul 13:33:11 ntpdate[6092]: no server suitable for synchronization
found
PS. Setting of system time with net-misc/ntp-4.2.6_p2 fails on three PCs.
With an other PC outside our institute (not restricted by a firewall) I have no problems to set the system time with net-misc/ntp-4.2.6_p2 and using 0.gentoo.pool.ntp.org as timeserver.
Reproducible: Always
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/0
------------------------------------------------------------------------
On 2010-07-28T18:49:15+00:00 Rose-g wrote:
I have the same issue with net-misc/ntp-4.2.6_p2-r1.
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/1
------------------------------------------------------------------------
On 2010-08-25T05:35:17+00:00 S-paul-n wrote:
I noticed a few days ago that this version's daemon fails to keep my
home (behind a broadband router) computer's time correct, and because it
doesn't bother saying anything at all about what it's doing in syslog
anymore, I had no idea where the problem might lie. Since the ntp
documentation is also appallingly opaque, I just downgraded again.
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/2
------------------------------------------------------------------------
On 2010-11-09T19:13:49+00:00 Rose-g wrote:
More than two month later I still have this problem. The connection to the timeserver seems to be faster:
root at cheetah:/root(34)# ping 10.101.10.20
PING 10.101.10.20 (10.101.10.20) 56(84) bytes of data.
64 bytes from 10.101.10.20: icmp_req=1 ttl=127 time=0.286 ms
64 bytes from 10.101.10.20: icmp_req=2 ttl=127 time=0.315 ms
64 bytes from 10.101.10.20: icmp_req=3 ttl=127 time=0.298 ms
64 bytes from 10.101.10.20: icmp_req=4 ttl=127 time=0.197 ms
64 bytes from 10.101.10.20: icmp_req=5 ttl=127 time=0.354 ms
64 bytes from 10.101.10.20: icmp_req=6 ttl=127 time=0.395 ms
64 bytes from 10.101.10.20: icmp_req=7 ttl=127 time=0.516 ms
64 bytes from 10.101.10.20: icmp_req=8 ttl=127 time=0.388 ms
64 bytes from 10.101.10.20: icmp_req=9 ttl=127 time=0.496 ms
64 bytes from 10.101.10.20: icmp_req=10 ttl=127 time=0.535 ms
64 bytes from 10.101.10.20: icmp_req=11 ttl=127 time=0.221 ms
^C
--- 10.101.10.20 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 9997ms
rtt min/avg/max/mdev = 0.197/0.363/0.535/0.112 ms
But ntpdate still says "Server dropped: no data":
root at cheetah:/root(35)# ntpdate -o 2 -t 5.0 -p 8 -d -d 10.101.10.20
9 Nov 21:31:30 ntpdate[3227]: ntpdate 4.2.6p2 at 1.2194-o Wed Jul 28 02:36:37 UTC 2010 (1)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
transmit to 10.101.10.20
receive(10.101.10.20)
transmit(10.101.10.20)
10.101.10.20: Server dropped: no data
server 10.101.10.20, port 123
stratum 5, precision -17, leap 00, trust 000
refid [10.101.10.20], delay 0.00000, dispersion 64.00000
transmitted 8, in filter 8
reference time: d084190a.bc06b19f Tue, Nov 9 2010 20:01:30.734
originate timestamp: d084190a.bc06b19f Tue, Nov 9 2010 20:01:30.734
transmit timestamp: d0842e30.a4d34fbb Tue, Nov 9 2010 21:31:44.643
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
9 Nov 21:31:46 ntpdate[3227]: no server suitable for synchronization
found
Nmap identifies the timeserver as:
IP ID Sequence Generation: Busy server or unknown class
Service Info: Host: *.*.*.*; OSs: NetWare, Unix
Any idea besides downgrading of ntp to solve the problem?
There is a similar bug: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=599793
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/3
------------------------------------------------------------------------
On 2010-11-10T15:32:42+00:00 Rose-g wrote:
I posted this bug upstream, compare URL, and got the answer that ntpdate
is deprecated. Perhaps gentoo should modify /etc/init.d/ntp-client.
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/4
------------------------------------------------------------------------
On 2010-11-10T21:39:22+00:00 MikeFrysinger wrote:
ntpdate has been "deprecated" for almost a decade at this point. see
Bug 21527.
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/5
------------------------------------------------------------------------
On 2010-11-11T10:20:29+00:00 Rose-g wrote:
If I run 'ntpd -g -q -x -d' instead of 'ntpdate -v -d -d -b -u 10.101.10.20', I see:
root at moose:/tmp/tiff_test(76)# ntpd -g -q -x -d
ntpd 4.2.6p2 at 1.2194-o Thu Nov 11 09:53:35 UTC 2010 (1)
addto_syslog: proto: precision = 0.102 usec
event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled
Finished Parsing!!
addto_syslog: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
addto_syslog: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
addto_syslog: Listen and drop on 1 v6wildcard :: UDP 123
addto_syslog: Listen normally on 2 lo 127.0.0.1 UDP 123
restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags 00003000 flags 00000001
addto_syslog: Listen normally on 3 br0 192.168.2.20 UDP 123
restrict: op 1 addr 192.168.2.20 mask 255.255.255.255 mflags 00003000 flags 00000001
addto_syslog: Listen normally on 4 virbr0 192.168.100.1 UDP 123
restrict: op 1 addr 192.168.100.1 mask 255.255.255.255 mflags 00003000 flags 00000001
addto_syslog: Listen normally on 5 br0 fe80::21f:d0ff:fea1:b79c UDP 123
restrict: op 1 addr fe80::21f:d0ff:fea1:b79c mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff mflags 00003000 flags 00000001
addto_syslog: Listen normally on 6 eth0 fe80::21f:d0ff:fea1:b79c UDP 123
restrict: op 1 addr fe80::21f:d0ff:fea1:b79c mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff mflags 00003000 flags 00000001
addto_syslog: Listen normally on 7 lo ::1 UDP 123
restrict: op 1 addr ::1 mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff mflags 00003000 flags 00000001
restrict: op 1 addr 0.0.0.0 mask 0.0.0.0 mflags 00000000 flags 00000090
restrict: op 1 addr :: mask 0.0.0.0 mflags 00000000 flags 00000090
restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags 00000000 flags 00000000
key_expire: at 0 associd 55448
peer_clear: at 0 next 1 associd 55448 refid INIT
event at 0 10.101.10.20 8011 81 mobilize assoc 55448
newpeer: 192.168.2.20->10.101.10.20 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000
event at 0 0.0.0.0 c016 06 restart
event at 0 0.0.0.0 c012 02 freq_set ntpd 105.462 PPM
transmit: at 1 192.168.2.20->10.101.10.20 mode 3 len 48
auth_agekeys: at 1 keys 1 expired 0
receive: at 1 192.168.2.20<-10.101.10.20 mode 4 len 48
event at 1 10.101.10.20 8024 84 reachable
clock_filter: n 1 off 0.016817 del 0.000711 dsp 7.937504 jit 0.000000
transmit: at 3 192.168.2.20->10.101.10.20 mode 3 len 48
receive: at 3 192.168.2.20<-10.101.10.20 mode 4 len 48
clock_filter: n 2 off 0.016646 del 0.000439 dsp 3.937513 jit 0.000171
transmit: at 5 192.168.2.20->10.101.10.20 mode 3 len 48
receive: at 5 192.168.2.20<-10.101.10.20 mode 4 len 48
clock_filter: n 3 off 0.016624 del 0.000485 dsp 1.937522 jit 0.000137
transmit: at 7 192.168.2.20->10.101.10.20 mode 3 len 48
receive: at 7 192.168.2.20<-10.101.10.20 mode 4 len 48
clock_filter: n 4 off 0.016485 del 0.000336 dsp 0.937528 jit 0.000227
select: combine offset 0.016485415 jitter 0.000227401
event at 7 10.101.10.20 963a 8a sys_peer
clock_update: at 7 sample 7 associd 55448
addto_syslog: ntpd: time slew +0.016485 s
ntpd: time slew +0.016485s
root at moose:/tmp/tiff_test(77)# echo $?
0
It looks OK for me.
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/6
------------------------------------------------------------------------
On 2010-11-11T11:12:11+00:00 Michel Alexandre Salim wrote:
The same bug affects Fedora (see the upstream bug report that superceded
1716) and has now been fixed upstream.
https://bugs.ntp.org/show_bug.cgi?id=1709
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/7
------------------------------------------------------------------------
On 2011-04-27T16:32:11+00:00 Jeremy Olexa wrote:
To the best of my knowledge, this bug was fixed in 4.2.6_p3. I've opened
a stablereq for that version in bug 365097
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/8
------------------------------------------------------------------------
On 2011-04-27T16:33:07+00:00 Jeremy Olexa wrote:
Resolved, obsolete because net-misc/ntp-4.2.6_p2 version isn't even in
the tree. Feel free to re-open if I am incorrect. Thanks.
Reply at: https://bugs.launchpad.net/ntp/+bug/787551/comments/9
** Changed in: ntp (Debian)
Status: Unknown => New
** Changed in: gentoo
Status: Unknown => Expired
** Changed in: gentoo
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/787551
Title:
ntpdate 4.2.6p2 at 1.2194-o: "no server suitable for synchronization
found" - works with 4.2.4p8 at 1.1612-o
To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp/+bug/787551/+subscriptions
More information about the Ubuntu-server-bugs
mailing list