cdslogin is in a strange state, not quite down but not sending alarms or alerts. It is pingable, I am still using it as a ssh-tunnel for my no-machine connection to opslogin0, but it does not accept any new ssh logins and my shell on it cannot find any commands.
File system error starting at 03:42:20 this morning
I power cycled cdslogin remotely via IPMI (10:50 power down, 10:52 power up) to force a fsck. The system came back up in operational mode, the systemd services alarms and locklossalerts started normally.
These services write to the local file system, which is presumably why they were down when the local FS switched to read-only mode.
Two improvements spring to mind:
Make alarms and alerts memory resident only, no reliance on any file system.
Make these services portable to cdsssh if cdslogin became unusable.
FRS32776
There is no indication of any mains power issues at 03:42 this morning. No UPS reports, and the three phases of the corner station mains-mon look good throughout.