From: Russell Owen
Subject: Re: [sdss3-25mlog 588] Re: 2.5m obslog 20120317 (MJD 56004)
Date: Mon, 19 Mar 2012 07:30:51 -0700
I think your tests need a time limit. That should be easy to add. Also they c=
an be asynchronous (send all queries first, then wait for replies) though th=
at is more work.=20
That said, I am puzzled why the existing watcher ping check is not sufficien=
t.
Russell
On Mar 18, 2012, at 1:24 PM, Elena Malanushenko  wrote:=
> I think I better not until apo actor could return proper code of fault.=20=
> We might need issue some exceptions to check apo actor with=20
> apo ping, or
> apo status, or=20
> apo version=20
>=20
> and if it does not return anything, it means it is not available.=20
>=20
> And when you disconnect from STUI after work
> you can see quitting of stui processes which were not completed
> and were hanging during the whole stui session :=20
>=20
> 20:04:52 APO.elenam 40 stui F Aborted; Actor=3D'apo'; Cmd=3D'ping'; Text=3D=
"disconnected"
> 20:04:52 APO.elenam 45 stui F Aborted; Actor=3D'apo'; Cmd=3D'version'; Tex=
t=3D"disconnected"
> 20:04:52 APO.elenam 46 stui F Aborted; Actor=3D'apo'; Cmd=3D'status'; Text=
=3D"disconnected"
> 20:04:52 APO.elenam 47 stui F Aborted; Actor=3D'apo'; Cmd=3D'ping'; Text=3D=
"disconnected"
> 20:04:52 APO.elenam 52 stui F Aborted; Actor=3D'apo'; Cmd=3D'ping'; Text=3D=
"disconnected"=20
>=20
> We need to wait for Jon.=20
> Elena
>=20
> On Mar 18, 2012, at 2:14 PM, snedden@apo.nmsu.edu wrote:
>=20
>> We know how to restart the apo actor. If Jon hasn't changed anything in
>> apoActor, maybe it would be okay to put it back into testActors?
>>=20
>> Steph
>>=20
>>> The last update of status of apo actor in
>>> archiver was  on
>>>       2012-03-13T17:04:25.090355
>>> 5 days ago
>>>=20
>>> Garrett, sorry.
>>> I think I wrote email about the removing of apo actor from
>>> testAcrots.  I did it for Stephanie for afternoon check, as apo
>>> actor hanged us many times.
>>>=20
>>>=20
>>> On Mar 18, 2012, at 1:47 PM, Garrett Ebelke wrote:
>>>=20
>>>> I was unaware that the apo actor was removed from the testActors script=
,
>>>> when I ran the testActors script several times, everything came back ok=
>>>> each time, so we assumed it was not a faulty actor. I guess if we have
>>>> this problem again then we will restart the apoActor.
>>>>=20
>>>> -Garrett
>>>>=20
>>>>=20
>>>>> Kaike,
>>>>>=20
>>>>> I do not know, I did not observe.
>>>>>=20
>>>>> It is not running now. ( ~1 hour ago I have checked it).
>>>>> And if other actors show "not availble" in case of
>>>>> problem (run  "ecamera ping" to see ) "apo ping" does not return
>>>>> code of fault.
>>>>> I removed  "apo ping" from  "testActors" two weeks ago
>>>>> as it hangs my script and prevent the testing of other actors.
>>>>>=20
>>>>> Regards,
>>>>> Elena
>>>>>=20
>>>>> On Mar 18, 2012, at 1:19 PM, Kaike Pan wrote:
>>>>>=20
>>>>>> was apoActor running last night?
>>>>>>=20
>>>>>> On Mar 18, 2012, at 12:14 PM, Elena Malanushenko wrote:
>>>>>>=20
>>>>>>> During last several night I got several complaines about
>>>>>>> apo actor problem and not all of my scripts were working
>>>>>>> as expected if it related with apo actor.
>>>>>>> i did not change anything in apo data reading during last several
>>>>>>> months and I need to ask Jon as he might changed
>>>>>>> something but did not expect to give us some follow up
>>>>>>> problems.
>>>>>>>=20
>>>>>>> dustcounts, enclosure status   are  from apo actor
>>>>>>>=20
>>>>>>>=20
>>>>>>> Elena
>>>>>>>=20
>>>>>>>=20
>>>>>>> On Mar 18, 2012, at 5:12 AM, gebelke@apo.nmsu.edu wrote:
>>>>>>>=20
>>>>>>>>=20
>>>>>>>>                  APACHE POINT OBSERVATORY SDSS 2.5M
>>>>>>>>=20
>>>>>>>>                            OBSERVING LOG
>>>>>>>>                     Saturday March 17, 2012
>>>>>>>>=20
>>>>>>>>                             (MJD 56004)
>>>>>>>>=20
>>>>>>>> ----  Observing Team ----
>>>>>>>>=20
>>>>>>>> Viktor Malanushenko
>>>>>>>> Garrett Ebelke
>>>>>>>>=20
>>>>>>>> ---- Observing Plan ----
>>>>>>>>=20
>>>>>>>> 17 Mar 2012  56004.0  0.28  02:35 11:47  07:16 16:29  BOSS  9.2
>>>>>>>> hours
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> ---- Observing Summary ----
>>>>>>>>=20
>>>>>>>> The entire night was lost due to high dust, high winds and heavy
>>>>>>>> cloud
>>>>>>>> coverage.
>>>>>>>>=20
>>>>>>>> The STUI dustCounter script and weatherPlot script are not working
>>>>>>>> on
>>>>>>>> either
>>>>>>>> minidru or landru.
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> Message 582 of sdss3-25mlog - Logs of nightly APO activities.
>>>>>>> sdss3-25mlog@sdss3.org
>>>>>>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>>>>>=20
>>>>>=20
>>>>> Elena Malanushenko
>>>>> elenam@apo.nmsu.edu
>>>>> All things are difficult before they are easy.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>> Elena Malanushenko
>>> elenam@apo.nmsu.edu
>>> All things are difficult before they are easy.
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Message 586 of sdss3-25mlog - Logs of nightly APO activities.
>>> sdss3-25mlog@sdss3.org
>>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>>=20
>>=20
>>=20
>=20
> Elena Malanushenko
> elenam@apo.nmsu.edu
> All things are difficult before they are easy.
>=20
>=20
>=20
> _______________________________________________
> Message 588 of sdss3-25mlog - Logs of nightly APO activities.
> sdss3-25mlog@sdss3.org
> https://sdss3.org/mailman/listinfo/sdss3-25mlog