[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hung downstream LDM


>Date: Wed, 19 Oct 2005 13:51:26 -0400
>From: Justin Cooke <address@hidden>
>Organization: NOAA/NWS/FSL
>To: Steve Emmerson <address@hidden>
>Subject: Re: hung downstream LDM

The above message contained the following:

> The NEXRAD2 data products come in a consistent stream.  After we  
> captured 30 minutes of truss logging from the hung downstream LDM we  
> restarted LDM and NEXRAD2 data products began again (~2035Z).
> >     2.  Is there anything in the LDM logfile on host
> >         that indicates a problem sending NEXRAD2 data-products to the
> >         downstream LDM on host b2n1 during the relevant time-interval?
> I was able to get the log files of yesterday from host  
> (our LDM is, a few pieces :
> The last NEXRAD2 item entered into our queue  at 17:52Z
> Oct 18 17:52:11 b2n1[1228948] INFO:     8168  
> 20051018175210.688 NEXRAD2 632021  L2-BZIP2/KDDC/20051018174531/632/21
> Oct 18 17:52:11 b2n1[1228948] INFO:    11872  
> 20051018175210.711 NEXRAD2 522025  L2-BZIP2/KBGM/20051018175032/522/25
>  From their logs:
> Oct 18 17:53:11 tgp48[20832]: up6.c:292:  
> nullproc_6() failure to RPC: Timed out
> ...
> Oct 18 20:37:07 tgp48[20832]: up6.c:172: HEREIS:  
> RPC: Unable to send; errno = Broken pipe

I assume that

    The IP address of b2n1 is; and
    The IP address of tgp48 is
Please tell me if this is incorrect.

Are there any other messages from PID 20832 in the tgp48 log file
between the above two?

Steve Emmerson

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.