Happen to notice a Red Box on the Ops Overview medm which said there was a GraceDB Querying Failure.  I wanted to figure out when this occurred, but I was not able to figure it out (trended the channel in DV, used conlog, looked on the CAL_INJ medm [where this RED Box also lives]).  Maybe this happened between 21-22:00?

So checking alogs, found a link to the following instructions.  It was not clear to me what state I was in:  did I need a "code start up" or a "code restart".  I followed the "code start up" instructions.

On the operator2 terminal (which is generally logged in as controls), I did the following:

ssh controls@h1fescript0
cd /opt/rtcds/userapps/release/cal/common/scripts
screen

python ext_alert.py run

This gave a GREEN "GraceDB querying Successful" box on the CAL_INJ medm (and the box entirely disappeared on the Ops Overview).

As I detatched from the screen environment, I did not get process ID # for the screen session; I only had a "[detached]" prompt.  So I did NOT store a file with a PID# under the home directory.  Maybe I should have followed the restart instructions?  Distinguishing how to determine what error state one is in will help with the instructions here.

I'm also assuming it's OK to restart/start this computer while in Observation Mode (because I did).