40m
QIL
Cryo_Lab
CTN
SUS_Lab
TCS_Lab
OMC_Lab
CRIME_Lab
FEA
ENG_Labs
OptContFac
Mariner
WBEEShop
|
40m Log |
Not logged in |
 |
|
Mon Aug 23 11:51:26 2021, Koji, Update, General, Campus Wide Power Glitch Reported: Monday, 8/23/21 at 9:30am
|
Mon Aug 23 19:00:05 2021, Koji, Update, General, Campus Wide Power Glitch Reported: Monday, 8/23/21 at 9:30am
|
Mon Aug 23 22:51:44 2021, Anchal, Update, General, Time synchronization efforts
|
Tue Aug 24 09:22:48 2021, Anchal, Update, General, Time synchronization working now
|
Tue Aug 24 18:11:27 2021, Paco, Update, General, Time synchronization not really working
|
Tue Aug 24 22:37:40 2021, Anchal, Update, General, Time synchronization not really working
|
Wed Nov 17 17:37:53 2021, Anchal, Update, General, Placed Nodus and fb1 on UPS power
|
Thu Nov 18 15:16:10 2021, Anchal, Update, General, Moved Chiara to 1X7 above nodus powered with same UPS
|
Mon Nov 22 17:42:19 2021, Anchal, Update, General, Connected Megatron to battery backed ports of another UPS
|
Tue Nov 30 17:11:06 2021, Paco, Update, General, Moved white rack to 1X3.5 
|
|
Message ID: 16291
Entry time: Mon Aug 23 22:51:44 2021
In reply to: 16290
Reply to this: 16292
|
Author: |
Anchal |
Type: |
Update |
Category: |
General |
Subject: |
Time synchronization efforts |
|
|
Related elog thread: 16286
I didn't really achieve anything but I'm listing what I've tried.
- I know now that the timesyncd isn't working because systemd-timesyncd is known to have issues when running on a read-only file system. In particular, the service does not have privileges to change the clock or drift settings at /run/systemd/clock or /etc/adjtime.
- The workarounds to these problems are poorly rated/reviews in stack exchange and require me to change the /etc/systmd/timesyncd.conf file but I'm unable to edit this file.
- I know that Paco was able to change these files earlier as the files are now changed and configured to follow a debian ntp pool server which won't work as the FEs do not have internet access. So the conf file needs to be restored to using ntpserver as the ntp server.
- From system messages, the ntpserver is recognized by the service as shown in the second part of 16285. I really think the issue is in file permissions. the file /etc/adjtime has never been updated since 2017.
- I got help from Paco on how to edit files for FE machines. The FE machines directories are exported from fb1:/diskless/root.jessie/
- I restored the /etc/systmd/timesyncd.conf file to how it as before with just servers=ntpserver line. Restarted timesyncd service on all FEs,I tried a few su the synchronization did not happen.
- I tried a few suggestions from stackexchange but none of them worked. The only rated solution creates a tmpfs directory outside of read-only filesystem and uses that to run timesyncd. So, in my opinion, timesyncd would never work in our diskless read-only file system FE machines.
- One issue in an archlinux discussion ended by the questioner resorting to use opennptd from openBSD distribution. The user claimed that opennptd is simple enough that it can run ntp synchornization on a read-only file system.
- Somehwat painfully, I 'kind of' installed the openntpd tool in the fb1:/diskless/root.jessie directory following directions from here. I had to manually add user group and group for the FEs (which I might not have done correctly). I was not able to get the openntpd daemon to start properly after soe tries.
- I restored everything back to how it was and restarted timesyncd in c1sus even though it would not do anything really.
Quote: |
This time no matter how we try to set the time, the IOPs do not run with "DC status" green. (We kept having 0x4000)
|
|