Linux – NTP failing to update

clock-synchronizationlinuxntptime

I am attempting to use ntp on the server.

Checking ps the ntpd process seems to be running:

ntpd -u ntp:ntp -p /var/run/ntpd.pid -g

However the time is not being corrected, any ideas?

The drift is about 2 minutes per month, which is not a problem according to an answer to an earlier question I asked. I understand it can take some time to correct a badly drifted time but I corrected the time recently to an accurate value.

(Server details – Cent OS, Linux version 2.6.9.)

Results of ntpq -pn

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 72.14.188.52    .INIT.          16 u  62h 1024    0    0.000    0.000 4000.00
 4.79.132.217    .INIT.          16 u  10d 1024    0    0.000    0.000 4000.00
 72.14.179.211   .INIT.          16 u  62h 1024    0    0.000    0.000 4000.00
*127.127.1.0     LOCAL(0)        10 l    2   64  377    0.000    0.000   0.004

Contents of /etc/log/messages

Jan 10 04:21:36 server1 ntpd[18417]: sendto(72.14.188.52): Operation not permitted
Jan 10 04:21:41 server1 ntpd[18417]: sendto(72.14.179.211): Operation not permitted
Jan 10 04:22:13 server1 ntpd[18417]: sendto(4.79.132.217): Operation not permitted
Jan 10 04:38:41 server1 ntpd[18417]: sendto(72.14.188.52): Operation not permitted
....

Update

Thanks for the responses. I've updated the firewall settings and no more messages have been appended to etc/log/messages, so it looks like a problem has been resolved. I'll give it some more time to see what happens.

Best Answer

Are there any ntpd messages in /var/log/messages? As I was dealing with my EC2 NTP issues I noticed that NTP didn't like being too far out of sync and wanted a manual update. Perhaps you're too far out for it to decide it will update for you.

Related Topic