From: Craig Loomis
Subject: Re: 2.5m obslog 20041117 (MJD 53327)
Date: Fri, 19 Nov 2004 10:13:44 -0700
On Nov 18, 2004, at 5:15 AM, Stephanie Snedden wrote:
> Day crew stuff:
> 1) The TPM cards in the lower enclosure communications rack had to be
> reset.
>    Do you want to investigate?
    After 'mth crashed (see PT logs), the ports on monts1 were evidently
all logged out. This would have included the dust monitor and the dew
point sensor. The dust monitor was logged out between 3:18Z and 3:19Z;
the dew point sensor would have been logged out right around then.
    I understand that the telnet driver on TPM2 is prone to spinning
when its connection is lost; it is a good bet that happened when the
dew point sensor port was logged out, after which tpm2 started
misbehaving.
    Is there a newer, more robust, telnet driver?
>
> 04:16Z Pete reset both TPM cards in the communications rack in the
> lower
> enclosure. We had lost communication with many sensors (see problem
> section).
> The reset appeared to fix the problem.
>
> ---=== PROBLEMS IN DETAIL ===---
>
> TPM errors when communications were lost:
> -----------------------------------------
> m1 mig (Communications Fault: 2004-11-18 03:20:27Z)
> tmicro (Disconnected Sensor in M2B7:Disconnected
> Sensor in M2B6:Disconnected Sensor in M2B5:Disconnected
> Sensor in M2B4:Disconnected Sensor in M2B3:Disconnected
> Sensor in M2B2:Disconnected Sensor in M2B1:Disconnected
> Sensor in M2B0:Disconnected Sensor in M1B7:Disconnected
> Sensor in M1B6:Disconnected Sensor in M1B5:Disconnected
> Sensor in M1B4:Disconnected Sensor in M1B3:Disconnected
> Sensor in M1B2:Disconnected Sensor in M1B1:Disconnected
> Sensor in M1B0:Disconnected Sensor in M0B7:Disconnected
> Sensor in M0B6:Disconnected Sensor in M0B5:Disconnected
> Sensor in M0B4:Disconnected Sensor in M0B3:Disconnected
> Sensor in M0B2:Disconnected Sensor in M0B1:Disconnected
> Sensor in M0B0:Communications Fault: 2004-11-18
> 03:20:27Z )
  - craig