aLIGO LHO Logbook

H1 DAQ

david.barker@LIGO.ORG - posted 11:04, Wednesday 30 May 2018 - last comment - 13:18, Wednesday 30 May 2018(42229)

h1fw0 daqd segmentation fault, restarted itself

Jonathan, Dave:

the Debian8 framewriter h1fw0 crashed at 10:39 this morning, reporting a segmentation fault. I've included an image of the journald logs at the time of the crash. Systemd restarted the service correctly.

Images attached to this report

Comments related to this report

david.barker@LIGO.ORG - 11:06, Wednesday 30 May 2018 (42230)

Link

h1fw0 crashed again. There appears to be an E18 RAID issue. I'm getting error emails from the RAID starting at 10:17 to the effect:

Disk 6 pod 1 error

david.barker@LIGO.ORG - 11:20, Wednesday 30 May 2018 (42232)

Link

I've stopped fw0 while we diagnose the raid issue.

david.barker@LIGO.ORG - 11:23, Wednesday 30 May 2018 (42233)

Link

attached two images of E18 web page: error logs, and pod1-disk6 page

Images attached to this comment

david.barker@LIGO.ORG - 11:35, Wednesday 30 May 2018 (42234)

Link

POD1 just failed, reporting disk6 has failed.

Images attached to this comment

david.barker@LIGO.ORG - 13:18, Wednesday 30 May 2018 (42237)

Link

h1fw0 is stable again now that RAID has taken the bad disk out of service.

fw0 has been running for 90 minutes with no problems. Greg is contacting Nexsan for a replacement disk, we'll leave the failed disk in place until the replacement is ready.