Reports until 05:04, Thursday 20 February 2014
H1 SUS
kiwamu.izumi@LIGO.ORG - posted 05:04, Thursday 20 February 2014 - last comment - 09:12, Thursday 20 February 2014(10196)
SUS_PRM guardian not running, unable to restart

Sorry, Jamie. I have another guardian job for you.

controls@opsws4:~ 0$ guardctrl start SUS_PRM
starting node SUS_PRM...
fail: SUS_PRM: unable to change to service directory: file does not exist

Comments related to this report
jameson.rollins@LIGO.ORG - 09:12, Thursday 20 February 2014 (10204)
Link

After the recent upgrade, where I rebuilt the node supervision infrastructure on h1guardian0, I did not yet get around to re-creating and restarting all of the nodes that had been running previously.  Arnaud and I are now restarting all the SUS nodes, but just in case, this should be an easy issue to resolve:

The guardctrl utility will tell you which nodes are currently running:

jameson.rollins@operator1:~ 0$ guardctrl list
IFO_IMC * run: IFO_IMC: (pid 11768) 144328s, want down; run: log: (pid 26686) 145415s
ISI_HAM4 * run: ISI_HAM4: (pid 26143) 3148s, want down; run: log: (pid 11352) 53329s
LSC * run: LSC: (pid 20593) 48884s, want down; run: log: (pid 11727) 48972s
SUS_ETMX * down: SUS_ETMX: 145415s; run: log: (pid 26687) 145415s
SUS_MC1 * run: SUS_MC1: (pid 29305) 145317s, want down; run: log: (pid 26685) 145415s
SUS_MC2 * run: SUS_MC2: (pid 29314) 145317s, want down; run: log: (pid 26863) 145413s
SUS_MC3 * run: SUS_MC3: (pid 29327) 145317s, want down; run: log: (pid 26864) 145413s
SUS_SRM * run: SUS_SRM: (pid 1869) 63862s, normally down, want down; run: log: (pid 1027) 150829s
jameson.rollins@operator1:~ 0$

Any node you think should be there but is not showing up, you can just create:

jameson.rollins@operator1:~ 0$ guardctrl create SUS_PRM
creating node SUS_PRM...
adding node SUS_PRM...
guardian node created:
ifo: H1
name: SUS_PRM
path: /opt/rtcds/userapps/release/sus/common/guardian/SUS_PRM.py
prefix: SUS-PRM
usercode:
  /opt/rtcds/userapps/release/sus/common/guardian/sustools.py
  /opt/rtcds/userapps/release/sus/common/guardian/SUS.py
states (*=requestable):
  0 MISALIGNED *
  1 SAFE *
  2 DAMPED *
  3 ALIGNED *
  4 INIT
  5 TRIPPED
jameson.rollins@operator1:~ 0$

Once the node is created, it is ready to start.  Before starting, I usually pop open a window viewing the log from the node so I can watch the start up.  This is most easily done by opening up the medm control panel for the node via the GUARD_OVERVIEW screen, and clicking on the "log" link.

Finally, just start the node:

jameson.rollins@operator1:~ 0$ guardctrl start SUS_PRM
starting node SUS_PRM...
jameson.rollins@operator1:~ 0$

We're working on making all the guardians smart enough to identify the current state of the system on startup, and identify the correct state to jump to.  The SUS guardians are programmed to go to the ALIGNED state on startup.  We're now working on enabling them to identify if the optic is currently misaligned and to go to the MISALIGNED state in that case.