Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

I have installed a very simple NTP server on a Red Hat server I own, the configuration is pretty basic:

driftfile /var/lib/ntp/drift
restrict default kod nomodify notrap 
restrict -6 default kod nomodify notrap 
restrict 127.0.0.1 
restrict -6 ::1
restrict 192.168.200.0 mask 255.255.255.0 nomodify notrap
server 0.rhel.pool.ntp.org
includefile /etc/ntp/crypto/pw
keys /etc/ntp/keys

If I try to test this from localhost, it seems to work properly:

ntpq -p localhost
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 gw-ge.esaote.co 62.48.53.90      3 u   56   64  173   81.474  -163823 67736.2

If I try to query it from a remote machine, same result:

ntpq -p 192.168.200.151
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 gw-ge.esaote.co 62.48.53.90      3 u    -   64  367   75.500  -163838 61828.5

But, if I invoke ntpdate, doesn't work:

ntpdate 192.168.200.151
12 Mar 10:35:51 ntpdate[2688]: no server suitable for synchronization found
share|improve this question
    
Your ntp server should use more servers, at least three. –  Martin Schröder Mar 13 at 9:41

1 Answer 1

Your NTP server is too far out of sync from the pool servers. You'll note that the leftmost character before the hostname in the ntpq -p output is a space. If NTP was synchronised to the remote server, this would be a *. Also note the very large offset value, which tells you that the time set on your server is way off.

Stop NTP, do a ntpdate pool.ntp.org, and restart it. After a few minutes it should settle down and synchronise, and your client should then be able to query it.

share|improve this answer
1  
Don't use ntpdate. –  Martin Schröder Mar 13 at 9:40
    
Ooh, thanks for that. 'After a suitable period of mourning, the ntpdate program may be retired'. I am so old school ;-( –  Flup Mar 13 at 9:43
    
What I discovered is that, regardless the error I posted above, the npt client synced slowly to the server. I can't simply why I had that error in first place. –  ludiegu Mar 13 at 9:57

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.