NTPDATE problem - no suitable server...

Mark msalists at gmx.net
Tue Jun 14 22:35:19 UTC 2005


Hi,

I have a problem with ntp clients randomly getting a "no server suitable for synchronization found".

It happens on some servers of the subnet, while at the same time, other servers within the same subnet are updating fine.
Then just a little later, the situation is just reversed. The problem comes and goes...
So it is not a firewall issue, it sometimes works, and UDP on 123 is open in both directions.

Below is a snapshot from one server, these commands were typed in this order, nothing else in between - the first one doesnt work,
the second one does...

I tried "-d" in between for debug, but I noticed that the man pages show the -d option twice, once for debug and once for using
non-privileged ports, so I am not sure if it actually does a debug or not... 

I ran iptraf on the server and is looks like there is no traffic coming in when the "no server suitable for synchronization found"
error comes back. But I don't really know why! My network has a pretty low load, so that should not be the issue...

Any idea what could cause this???

Oh... btw - the clients are the latest FC3, all RPMs that are installed are up2date, server is redhat 9, this one is not so
up2date...

Thanks,

MARK

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

14 Jun 14:52:24 ntpdate[8916]: ntpdate 4.2.0a at 1.1190-r Mon Oct 11 09:10:21 EDT 2004 (1)
14 Jun 14:52:28 ntpdate[8916]: no server suitable for synchronization found

[root at dbserv2 ~]# ntpdate -v ntp1.mydomain.com
14 Jun 14:58:24 ntpdate[8923]: ntpdate 4.2.0a at 1.1190-r Mon Oct 11 09:10:21 EDT 2004 (1)
14 Jun 14:58:24 ntpdate[8923]: adjust time server 192.168.1.29 offset 0.083743 sec

[root at dbserv2 ~]# ntpdate -d ntp1.mydomain.com
14 Jun 14:58:58 ntpdate[8926]: ntpdate 4.2.0a at 1.1190-r Mon Oct 11 09:10:21 EDT 2004 (1)
Looking for host ntp1.mydomain.com and service ntp
host found : ntp1.mydomain.com
transmit(192.168.1.29)
transmit(192.168.1.29)
transmit(192.168.1.29)
transmit(192.168.1.29)
transmit(192.168.1.29)
192.168.1.29: Server dropped: no data
server 192.168.1.29, port 123
stratum 0, precision 0, leap 00, trust 000
refid [192.168.1.29], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Wed, Feb  6 2036 22:28:16.000
originate timestamp: 00000000.00000000  Wed, Feb  6 2036 22:28:16.000
transmit timestamp:  c659d1a5.42f6e829  Tue, Jun 14 2005 14:59:01.261
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

14 Jun 14:59:02 ntpdate[8926]: no server suitable for synchronization found

[root at dbserv2 ~]# ntpdate -v ntp1.mydomain.com
14 Jun 14:59:04 ntpdate[8927]: ntpdate 4.2.0a at 1.1190-r Mon Oct 11 09:10:21 EDT 2004 (1)
14 Jun 14:59:04 ntpdate[8927]: adjust time server 192.168.1.29 offset 0.049147 sec




More information about the fedora-list mailing list