corey.gray@LIGO.ORG - posted 16:06, Tuesday 24 March 2020 - last comment - 17:47, Tuesday 24 March 2020(55751)
Day Operator Shift Summary
TITLE: 03/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: OBSERVING
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
Light activities on-site, but with that said, we had (2) LN2 trucks, tumbleweed burning by the Fire Dept, and landscaping contractor visiting the site. H1 operation was fairly smooth with most of it being controlled remotely. Attached is the Reservation System items from the day.
LOG:
- See Maintenance Log for activity covering from 15:00 - 20:00
- Hanford FD was onsite for tumble weed burning (from Bubba email).
- 20:28 Adding Niko to remote alert system (affects H1 up time briefly, but will be restored) [Dave]
- ~21:00 Logged into new NoMachine remote server per Jonathan H. email.
- 21:30 nuc24 rebooted by Richard M. (40min ndscope was froze). He also rebooted the DARM spectra computer (nuc30) earlier in the day because that was froze.
Images attached to this report
Comments related to this report
Turns out the FOMs are preferentially using h1nds0 as their nds server, and threfore they all froze at 09:55 PDT when I restarted h1nds0. This evening, for each nds-client FOM machine I:
- edited ~controls/.bashrc and changed the env var NDSSERVER to only use h1nds1
- rebooted the machine
All FOMs are back up online and using h1nds1.