Date: Sun, 2 Jan 2011 14:50:38 -0700 (MST)
Subject: Re: [SDSS3-infrastructure 4485] Re: 2.5m obslog 20110101 (MJD
From: "Daniel Oravetz"
Hi Stephen,
> DanO, Audrey: can you tell me exactly what the last thing was that did
> work
> with the platewebapp before it failed to load?  e.g. did you force
> complete
> or change the status of some other cart and then it stopped working?  Or
> did
> it just work all night and then suddenly stop working without you doing
> anything other than trying to load the plate page?
>
> Bottom line: it is working again after a platewebapp restart (
> "/etc/init.d/plateWebApp restart" ) but we don't know why it failed in the
> first place.  Apologies for the trouble.  If you are really stuck and it
> is
> blocking you, restarting the platewebapp is a safe thing to try, but in
> non-critical cases like this it is helpful for you to leave it in the
> broken
> state for developers to poke at it a bit.  Thanks.
>
> Regards,
>
> Stephen
I was attempting to update the plate status of cartridge 15, 4503 to
'Force Complete' and that's when the platedb web interface hung and failed
to reload thereafter.  As you probably know, cartridge 15 and 18 doneness
is currently based on sp1 values from SoS only and nearly all of the time
the sp2 (S/N)^2 values lag sp1 by something like a factor of two-ish, so
the platedb web interface must be told that a plate is complete (Force
Complete) for these cartridges.  In last night's case we were fortunate
that I already had drawn up a plugging email, so we figured since it was
the end of the night we'd leave the platedb web interface in its stuck
state so that perhaps you might be able to dig something up that would
otherwise be lost upon a restart.
DanO