ntpd sync issue

[MikeL_4]

When I startup ntpd on Red Hat 5 server I receive:
service ntpd start
ntpd: Synchronizing with time server: [FAILED]
Starting ntpd: [ OK ]

There is nothing in the ntpd.log file indicating a problem....

I then tried the ntpdate command to see if it can tell me anything additional:

ntpdate -du ntp1.spc.speechport.net
30 Jan 13:51:25 ntpdate[31605]: ntpdate 4.2.2p1@1.1570-o Thu Jan 17 18:14:10 UTC 2008 (1)
Looking for host ntp1.spc.speechport.net and service ntp
host found : 10.18.0.59
transmit(10.18.0.59)
transmit(10.18.0.59)
transmit(10.18.0.59)
transmit(10.18.0.59)
transmit(10.18.0.59)
10.18.0.59: Server dropped: no data
server 10.18.0.59, port 123
stratum 0, precision 0, leap 00, trust 000
refid [10.18.0.59], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
transmit timestamp: cd2dcab0.4e81ecd4 Fri, Jan 30 2009 13:51:28.306
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

30 Jan 13:51:29 ntpdate[31605]: no server suitable for synchronization found

Not sure where to look to resolve the issue, any suggestions would be appreciated...

The same ntp servers are coded in ntp.conf and step-tickers....

[Ivan Ferreira · Accepted solution]

Please run ntpq -pn to identify if you can reach the server. You should get something like:

# ntpq -pn remotehost
remote refid st t when poll reach delay offset jitter
==============================================================================
127.127.1.0 LOCAL(0) 3 l 40 64 377 0.000 0.000 10.010
-200.218.171.41 200.20.186.75 2 u 809 1024 377 273.530 6.278 2.820
+200.55.63.254 200.160.0.8 3 u 240 256 377 285.350 1.417 0.580
-200.199.205.149 200.20.186.75 2 u 684 1024 375 303.420 -9.362 4.730
216.27.190.202 0.0.0.0 16 u 602 1024 0 0.000 0.000 16000.0
-200.19.74.21 200.19.119.69 2 u 836 1024 377 346.650 40.206 2.700
209.134.7.18 0.0.0.0 16 - - 1024 0 0.000 0.000 16000.0
+131.216.22.9 208.38.65.37 3 u 32 256 377 237.980 4.713 0.560
172.16.4.1 0.0.0.0 16 - - 1024 0 0.000 0.000 16000.0
*172.16.4.2 200.199.205.149 3 u 133 256 377 0.380 -2.393 3.300


If you do can, then ensure that your time is close enough to start the sync, run ntpdate -b .

[MikeL_4]

Thanks, ntpq shows we are transmitting but not receiving from the time server....