Date: Sat, 23 Dec 2006 16:05:07 -0600 (CST)
From: Stephen Kent
Subject: Re: 2.5m obslog 20061222 (MJD 54092)
> ------------
> We had the same problem with tccmon for the second night in row.  When Kaike
> tried to open his tccmon session,  tccNode gave the fellowing warning message.
> Then he started tccMonitor 1 anyway, but the tccmon display would not update
> any information except for data and time (the same problem as Howard had last
> night). Then Steph restarted Murmur server and clean up semaphore, but it
> did not work out. Last night, tccmon came back and work properly after about
> 30 mintues. Tonight, it took about 90 minutues for tccmon display work
> correctly. Steph suspects that this problem may relate to sdsshost2 resources
> which might be taken by goStare commands when we did imager calibration. She
> will try to find a way to release host2 resources.
> tccmon warning message:
tccNode sets up the link to the TCC.  It is timing out, meaning that the
TCC is not responding to initial login.  We used to have problems in the
past like this, and I seem to recall that it might be due to too many
users logged in, a hung connection by another user causing buffers to fill
up, or something like that.  For example, I can connect now and see the
TCC status. If I do "show users", I see that there are 8 users connected -
this seems odd in the middle of a weekend afternoon.  Some of these might
be orphaned connections.
The message "Presuming success anyway" is - ahem - wishful thinking on
tccmon's part.  Sometimes the login would work but just take a long time,
and sometimes not.
Steve
> -----------------------
> watch> tccNode
> Timeout
> Lines collected so far:
>    Last interactive login on Friday, 22-DEC-2006 23:50:31.35
> 0 0 I TrackAdvTime=3.56
> 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,30.00,0.00; AxePos=121.00,30.46,0.0
> 0 0 I AxisErrCode="OK","OK","OK"
> 0 0 W AzStat=121.000471, 0.000000, 4673548412.50621, 0x00003800; BadAzStatus;
> DTime=0.0
> 0 0 W AltStat=30.455025, 0.000000, 4673548412.59312, 0x40003800; BadAltStatus;
> ltDTime=0.0
> 0 0 W RotStat=0.000610, 0.000000, 4673548412.75300, 0x00003800; BadRotStatus;
> tDTime=0.0; RotID=1, 0
> 0 0 I TrackAdvTime=3.48
> 0 0 I Modu="exe_BrdTelPos"; Text="1410100 packets sent successfully"
> 0 0 I TrackAdvTime=3.48
> 0 0 I TCCStatus="TTT","NNN"; TCCPos=121.00,30.00,0.00; AxePos=121.00,30.46,0.0
> 0 0 I AxisErrCode="OK","OK","OK"
> 0 0 W AzStat=121.000467, 0.000000, 4673548422.50602, 0x00003800; BadAzStatus;
> DTime=0.0
> 0 0 W AltStat=30.455017, 0.000000, 4673548422.63322, 0x40003800; BadAltStatus;
> ltDTime=0.0
> 0 0 W RotStat=0.000610, 0.000000, 4673548422.79288, 0x00003800; BadRotStatus;
> tDTime=0.0; RotID=1, 0
> Presuming success anyway!
> file3