Subject: Re: 2.5m obslog 20091119 (MJD 55155)
From: Robert Lupton the Good
Date: Fri, 20 Nov 2009 08:17:24 -0500
> We started guider but it did not update guider GUI and filename
> line. We ping guider and it was ok. We ping gcamera and it did not
> respond. We did not find any version on gcamera and restarted
> gcameraICC
> with its default version.
I didn't see the ticket about needing a cut version of gcamera.
> We did loadCart and gcamera flat again and ran guider. It still
> did not work.
> We restarted guider with version v1_0_15. We loaded cart
> and made gcamera flat again. We started guider and it requested
> guider dark
> also. Made guider dark and it strted to work again.
> Time stamps and information  about our commands are in problem
> section.
OK, let's look at the log extracts and sort out what was going on:
> 10:23:27 APO.viktorm 46 hub f NoTarget="the target named gcamera is
> not connected"
> 10:23:35 APO.viktorm 47 hub f NoTarget="the target named gcam is not
> connected"
> 10:23:53 APO.elenam 146 hub f NoTarget="the target named gcamera is
> not
> connected"10:23:55 APO.viktorm 48 hub f NoTarget="the target named
> gcamera is
> not connected"
> 10:27:39 APO.viktorm 50 hub f NoTarget="the target named gcamera is
> not
> connected"
It appears that the gcamera was not connected at 10:23 and was still
not connected at 10:27.  I'm not sure what commands you issued to get
these messages, but if it's not connected the first suspicion is that
it's down.  You should have tried reconnecting at 10:23:28, first with
"hub startNubs gcamera" and then (when that failed) immediately have
moved to restarting it with the stageManager.  There's no need to mess
with the guider at this point as there's not evidence of any problem.
When you had things working and the control room was quiet, what were
the error messages in the gcamera logs at about this time?
> -----------
> sdss3@hub25m[1000]$ setup gcameraICC
> sdss3@hub25m[1001]$ stageManager gcameraICC status
> gcameraICC is not running
> sdss3@hub25m[1002]$ stageManager gcameraICC start status
> Starting new gcameraICC... done.
> gcameraICC is running as process 4946
> sdss3@hub25m[1003]$ stageManager gcameraICC status
> gcameraICC is running as process 4946
> sdss3@hub25m[1004]$
OK, we're up.  Time to start the nub -- I assume that you did so,
although it's not in the log.
Is this when:
>> We did loadCart and gcamera flat again and ran guider. It still
>> did not work
If so, what were the messages?  What didn't work?   Why did you think
that you needed to restart the guider?
> ----------
> 10:51Z
> sdss3@hub25m[1000]$
> sdss3@hub25m[1000]$ setup guiderActor v1_0_15
> sdss3@hub25m[1001]$ stageManager guiderActor status
> guiderActor is running as process 12311
> sdss3@hub25m[1002]$ stageManager guiderActor status restart
> guiderActor is running as process 12311
> Stopping guiderActor.
> Starting new guiderActor... done.
> sdss3@hub25m[1003]$ stageManager guiderActor status
> guiderActor is running as process 5138
> sdss3@hub25m[1004]$
> --------
> hub startNubs guider
And we were back on the sky.  Hurrah.