oli.patane@LIGO.ORG - posted 21:05, Thursday 02 November 2023 - last comment - 21:55, Thursday 02 November 2023(73945)
Lockloss
Lockloss @ 11/03 04:00UTC
Right after the lockloss verbals said:
Could not connect to DAQ-DC0_UPTIME_SECONDS (Nov 3 04:00:16 UTC)
Could not connect to DAQ-DC0_GPS (Nov 3 04:00:16 UTC)
Error with DC0 (Nov 3 04:00:16 UTC)
Could not connect to DAQ-GDS0_UPTIME_SECONDS (Nov 3 04:00:16 UTC)
Error with GDS0 (Nov 3 04:00:16 UTC)
Re-established connection to DAQ-DC0_UPTIME_SECONDS (Nov 3 04:00:22 UTC)
Could not connect to DAQ-FW1_UPTIME_SECONDS (Nov 3 04:00:27 UTC)
Re-established connection to DAQ-DC0_GPS (Nov 3 04:00:27 UTC)
Error with FW1 (Nov 3 04:00:27 UTC)
Could not connect to DAQ-FW0_UPTIME_SECONDS (Nov 3 04:00:29 UTC)
Error with FW0 (Nov 3 04:00:29 UTC)
Re-established connection to DAQ-GDS0_UPTIME_SECONDS (Nov 3 04:00:37 UTC)
Re-established connection to DAQ-FW0_UPTIME_SECONDS (Nov 3 04:01:02 UTC)
Re-established connection to DAQ-FW1_UPTIME_SECONDS (Nov 3 04:01:39 UTC)
Could not connect to DAQ-DC0_GPS (Nov 3 04:00:16 UTC)
Error with DC0 (Nov 3 04:00:16 UTC)
Could not connect to DAQ-GDS0_UPTIME_SECONDS (Nov 3 04:00:16 UTC)
Error with GDS0 (Nov 3 04:00:16 UTC)
Re-established connection to DAQ-DC0_UPTIME_SECONDS (Nov 3 04:00:22 UTC)
Could not connect to DAQ-FW1_UPTIME_SECONDS (Nov 3 04:00:27 UTC)
Re-established connection to DAQ-DC0_GPS (Nov 3 04:00:27 UTC)
Error with FW1 (Nov 3 04:00:27 UTC)
Could not connect to DAQ-FW0_UPTIME_SECONDS (Nov 3 04:00:29 UTC)
Error with FW0 (Nov 3 04:00:29 UTC)
Re-established connection to DAQ-GDS0_UPTIME_SECONDS (Nov 3 04:00:37 UTC)
Re-established connection to DAQ-FW0_UPTIME_SECONDS (Nov 3 04:01:02 UTC)
Re-established connection to DAQ-FW1_UPTIME_SECONDS (Nov 3 04:01:39 UTC)
04:00 LOCKLOSS_SHUTTER_CHECK went to SHUTTER_FAIL
04:12:23 ALS_XARM reports "[INCREASE_FLASHES.run] USERMSG 2: Arm in Fault state! Waiting..."
04:35 Lockloss from FIND_IR right after IR was not found
- Errors with DC0, GDS0, FW1, FW0 again
- Connections reestablished
04:37 I put the detector in DOWN while waiting for Dave to verify that the computers were good - Guardian was slow to react to me INIT'ing DOWN and I had to reselect a few times
04:39 BRSX/Y_STAT nodes in Errors
BRSX/Y Log output:
2023-11-03_04:39:42.266215Z BRSX_STAT [DAMPER_ON.run] timer['run check'] done
2023-11-03_04:39:42.634847Z BRSX_STAT W: Traceback (most recent call last):
2023-11-03_04:39:42.634847Z File "/usr/lib/python3/dist-packages/guardian/worker.py", line 494, in run
2023-11-03_04:39:42.634847Z retval = statefunc()
2023-11-03_04:39:42.634847Z File "/usr/lib/python3/dist-packages/guardian/state.py", line 246, in __call__
2023-11-03_04:39:42.634847Z main_return = self.func.__call__(state_obj, *args, **kwargs)
2023-11-03_04:39:42.634847Z File "/opt/rtcds/userapps/release/isi/common/guardian/isiguardianlib/sensor_correction/brs_stat_main.py", line 193, in run
2023-11-03_04:39:42.634847Z where_BRS_should_be = Check_BRS()
2023-11-03_04:39:42.634847Z File "/opt/rtcds/userapps/release/isi/common/guardian/isiguardianlib/sensor_correction/brs_stat_main.py", line 105, in Check_BRS
2023-11-03_04:39:42.634847Z drift_dat = dat[1].data
2023-11-03_04:39:42.634847Z AttributeError: 'NoneType' object has no attribute 'data'
2023-11-03_04:39:42.635830Z BRSX_STAT [DAMPER_ON.run] USERMSG 0: USER CODE ERROR (see log)
2023-11-03_04:39:42.646044Z BRSX_STAT ERROR in state DAMPER_ON: see log for more info (LOAD to reset)