Reports until 21:26, Tuesday 21 July 2015
H1 INJ
jeffrey.kissel@LIGO.ORG - posted 21:26, Tuesday 21 July 2015 (19817)
Attempt to restart CW injections appear to have Failed
J. Kissel

We restarted the h1hwinj1 and h1hwinj2 injection machines today to check whether they were contributing to the recent EPICs freeze problems we've been seeing on control room work stations. The reboot did NOT help the problem. However, since they've now been restored, I figured I'd try my luck at using Eric's instructions on how to restart them (LHO aLOG 18831, T1400349). 

While I was able to log on to h1hwinj, find the appropriate directory, and start_psinject, after the 60 sec start up time, I did NOT see the injection start (looking at the excitation channel in the H1:CAL-INJ_CW_EXCMON or H1:CAL-INJ_HARDWARD_OUTMON), nor does the CAL-CS GDS_TP sceen indicate that there has been a test point selected, even though the interaction with start_psinject was as follows:
-bash-4.1$ ./bin/start_psinject 
Currently, we are running on: h1hwinj1.cds.ligo-wa.caltech.edu
Result of checking injection status: H1 injection is NOT RUNNING
  Automatic restart should occur within 10 minutes; no human action is required
H1 injection will be started with configuration ER7 if you proceed

For logging purposes, please enter your name     (or Ctrl-C to cancel)
Jeffrey Kissel
Type a BRIEF explanation (a few words) for why start_psinject is being executed
Hardware Injection Machines were restarted today to see if they were affecting EPICs slowdown seen in the control room. See LHO aLOG 19809.
Starting H1 injection into H1:CAL-INJ_CW_EXC on h1hwinj1.cds.ligo-wa.caltech.edu using ER7
exec /data/scirun/O1/HardwareInjection/Details/bin/exec_psinject_from_script /data/scirun/O1/HardwareInjection/Details/pulsar/ER7 /ligo/apps/sl6/gds-2.16.12 H1 H1:CAL-INJ_CW_EXC 1121573769
Injection will start at t=1121573769 (60 seconds from now)...
Injection starting now
-bash-4.1$ 


Also -- while the hardware injection machines were down, there was NO indication on the injection overview screen that the hardware injection machines were down / dead. In fact, since the EPICs records that *are* shown on the screen are all defined and stored in the front-end, they had been left in the ALL GREEN state making it deceivingly look like all is well. There should be a look-alive heartbeat EPICs variable sent from these machines, or at least a static alarm bit somewhere to indicate that these injection machines are down or up.