Virgo Logbook

Reports 1-1 of 1

Detector Operation (Operations Report)

Montanari - 23:07 Thursday 14 September 2017 (39478)

Operator Report - Afternoon Shift 14/09

Activities about 50Hz investigation finished at 14:15UTC.
After that, the planned atcivity was alignment.
It carried out with problems due to several unlocks that prevented the lock.

VPM
14:58UTC - nitelServer process restarted after a crash
15:09UTC - MdTrend process crashed and was not possible to restart via VPM, after 11 minutes it restarted by itself
19:31UTC - EarlyWarning process restarted after a crash
20:37UTC - EarlyWarning process restarted after a crash
20:54UTC - EarlyWarning process restarted after a crash
21:03UTC - EarlyWarning process restarted after a crash

Comments to this report:

pacaud - 15:44 Monday 18 September 2017 (39480)

I don't know for EarlyWarning process, but for MdTrend, the process may appeared as crashed (red), while it is still correctly running on the machine. It is a limitation in Vpm and Cm that prevent to distinguish between a crashed process, a hanged machine or an unresponsive process. The process should reappear as running after it become responsive again.

So, for MdTrend, it is better to check manually if the process is running. Trying a restart with Vpm won't hurt though, as Cm will prevent to run a second instance of MdTrend.