Displaying report 1-1 of 1.
Reports until 15:35, Tuesday 24 September 2024
H1 CDS
david.barker@LIGO.ORG - posted 15:35, Tuesday 24 September 2024 - last comment - 21:40, Tuesday 24 September 2024(80277)
CDS Maintenance Summary: Tuesday 24th September 2024

WP12093 Add h1iopsusex new LIGO DAC to the SWWD

Ryan C, Erik, Dave:

A new h1iopsusex model was built and installed using the custom rcg-9eb07c3200.

The new IOP model was installed using the procedure:

We decided to reboot rather than just restart the models because in the past this had not worked and we ended up rebooting anyways. Since the IOP restart necessitated a full model restart, rebooting did not slow the process much.

Now if the software watchdog (SWWD) on h1iopsusex were to initiate a local DACKILL, it wil kill all six local DACs: three 18-bit, two 20-bit and the one LIGO 28-bit.

WP12101 Reboot h1digivideo servers

Erik, Dave:

Due to a slow memory leak in the old digivideo servers h1digivideo[0,1,2] after an uptime of about 7 months h1digivideo2's memory usage had crept up to 95% (2024 trend attached).

We rebooted all three machines at 12:22 following the conclusion of h1alsey work (the h1alsey model receives ITMY camera data from h1digivideo2).

At time of writing the mem usages are; 0=20%; 1=22%; 2=18%

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 21:40, Tuesday 24 September 2024 (80283)

Tue24Sep2024
LOC TIME HOSTNAME     MODEL/REBOOT
12:23:23 h1susex      h1iopsusex  
12:23:36 h1susex      h1susetmx   
12:23:49 h1susex      h1sustmsx   
12:24:02 h1susex      h1susetmxpi 
 

Displaying report 1-1 of 1.