Subject: Re: [sdss3-25mlog 1196] 2.5m obslog 20130411 (MJD 56394)
From: Kaike Pan
Date: Fri, 12 Apr 2013 11:39:22 -0600
I restarted sosActor, and stop, kill, start sos process on sos3. =
However, the deamon process did not
started after issue these command. Later on, Stephen was able to =
restarted these deamon process (he
will send out an email on this). After that, I took 5 biases and a set =
of BOSS calibration, and all exposures
have been processed automatically. In short, sosActor and SoS3 process =
are running normally.
 What remains unclear is that what caused SOS3 webpage hung.
On Apr 12, 2013, at 6:03 AM, asimmons@apo.nmsu.edu wrote:
>=20
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Thursday April 11, 2013
>=20
>                                  (MJD 56394)
>=20
> ----  Observing Team ----
>=20
> Dan Oravetz
> Audrey Oravetz
> Fritz Stauffer (support)
>=20
> ---- Observing Plan ----
>=20
> 11 Apr 2013  56394.0  0.12  02:41 11:27  09:00 17:47  BOSS  8.8 hours
>=20
>=20
> ---- Observing Summary ----
>=20
> We lost about 75% of the night due to clouds and nearby radar.=20
>=20
> We opened at 07:00Z, and observed:
>=20
> Cart 15, plate 6741 - DONE
> Cart 17, plate 6726 - DONE
> Cart 4, plate 5911, GALCEN_A - 1 X ABBA + 1 X AB; no missing fibers, =
faint fiber
> #284
>=20
> Problems:
> 1. The SOS3 webpage hung due to a web server failure on sdss-gateway. =
Fritz was
> contacted. His response: "I think the web server failure on =
sdss-gateway is
> related to some work installing the mirrored trac pages. I do see =
error
> messages showing the web server crashing, and since I restarted those =
messages
> have stopped. It looks like it is okay now."
>=20
> 2. After Fritz got the webpage back up and running, we ran sos_aporedo =
for
> tonight's MJD which successfully retrieved the information for all =
exposures up
> to that point. However, we had to run sos_aporedo for every exposure =
afterwards
> because sos_apocontrol status would show no that processes that were =
running,
> even though their were exposures ready in the queue.=20
>=20
> 3. SOS actor got disconnected somehow during the gotoField of cart 17, =
so the
> command failed. We restarted the actor through stageManager, but it =
still failed
> to connect. We ran cals and hartmanns manually since it was the last =
BOSS plate
> of the night. Would someone please reconnect the sos actor for us =
before
> tomorrow night's observations?
>=20
>=20
> ---- Observing Log ----
>=20
> Afternoon:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> motorPosition
>     sp1:    1540,    1512,    1567; =20
>     sp2:    -794,   -1941,   -1932; =20
> ----------
> Median spectrographs temperatures:
>     Tsp1=3D 4.5,  Tsp2=3D 4.1; =20
>     Outside air temperature=3D 10.6; =20
>=20
> 22:31:50 motorPos.sp1.move:  -5121,   -5123,   -5119; =20
> 22:31:55 motorPos.sp2.move:    -42,     -45,     -41; =20
>=20
> Moved b1 -2 degrees and b2 -3 degrees.
>=20
> COLLIMATE: Camera b1 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix)
> COLLIMATE: Predict blue camera ring movement of   -6.0 degrees for =
spectro-1
> COLLIMATE: Camera b2 appears to be OUT-OF-FOCUS (|mean| > 0.15 pix)
> COLLIMATE: Predict blue camera ring movement of    2.9 degrees for =
spectro-2
> COLLIMATE: Camera r1 appears to be IN-FOCUS (|mean|  COLLIMATE: Predict (red) piston movement of  170 steps for spectro-1
> COLLIMATE: Predict (red) piston movement of  384 steps for spectro-2
> COLLIMATE: Issue command: "boss moveColl spec=3Dsp2 a=3D384 b=3D384 =
c=3D384"
>=20
> 00:15Z - Started ventilating.
>=20
>=20