On 09/03/16 05:35, Antonio Querubin wrote: <snip> >> A 7 second variance shouldn't be that much of an issue. > > A time offset greater than a fraction of second suggests ntpd really > isn't time-synced. > > Not sure if this is related but I've found that ntpd on SL7 systems dies > during bootup and require a manual start (using an unchanged ntp.conf). > This is what I see immediately after doing a fresh boot of a SL7 system: > > $ sudo systemctl status ntpd > ● ntpd.service - Network Time Service > Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; > vendor preset: disabled) > Active: inactive (dead) > $ sudo systemctl restart ntpd > $ sudo systemctl status ntpd > ● ntpd.service - Network Time Service > Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; > vendor preset: disabled) > Active: active (running) since Tue 2016-03-08 19:22:28 HST; 3s ago > Process: 2417 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS > (code=exited, status=0/SUCCESS) > Main PID: 2418 (ntpd) > CGroup: /system.slice/ntpd.service > └─2418 /usr/sbin/ntpd -u ntp:ntp -g > <snip> > Mar 08 19:22:29 sl7-dev ntpd[2418]: 0.0.0.0 c016 06 restart > Mar 08 19:22:29 sl7-dev ntpd[2418]: 0.0.0.0 c012 02 freq_set kernel > -0.605 PPM > Mar 08 19:22:29 sl7-dev ntpd[2418]: 0.0.0.0 c615 05 clock_sync > > > If the mirror masters are running SL7 and ntpd is enabled for time sync, > somebody may want to verify that ntpd really is running on them. > > > Antonio Querubin > e-mail: [log in to unmask] > > xmpp: [log in to unmask] But doesn't SL7 use chrony? $ systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2016-03-02 17:43:02 GMT; 6 days ago Main PID: 767 (chronyd) CGroup: /system.slice/chronyd.service └─767 /usr/sbin/chronyd John P