[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
hung downstream LDM (was: "pbuf_flush: time elapsed" problem)
- Subject: hung downstream LDM (was: "pbuf_flush: time elapsed" problem)
- Date: Wed, 19 Oct 2005 10:14:49 -0600
Justin,
>Date: Wed, 19 Oct 2005 07:44:56 -0400
>From: Justin Cooke <address@hidden>
>Organization: NOAA/NWS/FSL
>To: Steve Emmerson <address@hidden>
>Subject: Re: "pbuf_flush: time elapsed" problem
The above message contained the following:
> Oct 18 14:15:01 b2n1 140.90.85.102[1228948] NOTE: LDM-6 desired
> product-class: 20051018141401.214 TS_ENDT {{NEXRAD2, ".*"},{NONE,
> "SIG=a239ff9ff6fa47cb8ab19f7c5e476ae1"}}
Now that I know we're dealing with a downstream LDM, I have some
questions:
1. How do you know that the downstream LDM on host b2n1 SHOULD have
been receiving NEXRAD2 data-products from an upstream LDM on
host 140.90.85.102 during the time-interval when it wasn't?
2. Is there anything in the LDM logfile on host 140.90.85.102
that indicates a problem sending NEXRAD2 data-products to the
downstream LDM on host b2n1 during the relevant time-interval?
Regards,
Steve Emmerson