NTP Syncornization Issue

Latest response

Hi,
Here is our NTP configuration:
/etc/ntp.conf

restrict 127.0.0.1
driftfile /var/lib/ntp/drift
server x.x.x.x burst iburst
restrict x.x.x.x mask 255.255.255.255 nomodify notrap

/etc/sysconfig/ntpd

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

I guess, there is an issue for synchronization because "refid" filed is always "LOCAL(1)":

remote refid st t when poll reach delay offset jitter

*10.110.1.254 LOCAL(1) 8 u 92 128 377 0.786 7.026 2.193

Please advise.

Responses

Check logs for issues with sync.

grep -i ntp /var/log/messages

Sidenote: Using only one NTP server means there is no way of telling if the time source is right or wrong. Four servers is recommended as ntpd will have a sufficient number of sources to choose from.

The asterisk at the beginning of the line indicates that this server you ran the "ntpq -p" command on is currently in sync with NTP server 10.110.1.254. The refid tells you where the remote NTP server (10.110.1.254) gets its time from. In this case, it looks like the server 10.110.1.254 is using its local clock, instead of another NTP server further upstream.

The "reach" field value 377 indicates this server has successfully polled the 10.110.1.254 server at least 8 times consecutively (the "reach" value is an octal bit-field, with the result of the most recent poll in the least significant bit). The delay/offset/jitter values also look good.

Go to the server that has IP address 10.110.1.254, verify its NTP configuration and, as Sam Wachira suggests, add several NTP sources to its configuration if possible.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.