40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Mon Aug 16 23:30:34 2021, Paco, Update, CDS, AS WFS commissioning; restarting models 
    Reply  Thu Aug 19 03:23:00 2021, Anchal, Update, CDS, Time synchornization not running 
       Reply  Thu Aug 19 14:14:49 2021, Koji, Update, CDS, Time synchornization not running 
          Reply  Fri Aug 20 00:28:55 2021, Anchal, Update, CDS, Time synchornization not running 
             Reply  Fri Aug 20 06:24:18 2021, Anchal, Update, CDS, Time synchornization not running 
Message ID: 16286     Entry time: Fri Aug 20 06:24:18 2021     In reply to: 16285
Author: Anchal 
Type: Update 
Category: CDS 
Subject: Time synchornization not running 

I read on some stack exchange that 'NTP synchornized' indicator turns 'yes' in the output of command timedatectl only when RTC clock has been adjusted at some point. I also read that timesyncd does not do the change if the time difference is too much, roughly more than 3 seconds.

So I logged into all FE machines and ran sudo hwclock -w to synchronize them all to the system clocks and then waited if the timesyncd does any correction on RTC. It did not. A few hours later, I found the RTC clocks drifitng again from the system clocks. So even if the timesynd service is running as it should, it si not performing time correction for whatever reason.

Maybe we should try to use some other service?

Quote:
 

The NTP synchronized flag in output of timedatectl command did not change to yes and the RTC is still 3 seconds ahead of the local clock.

 

ELOG V3.1.3-