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

Re: hung downstream LDM



Justin,

>Date: Wed, 19 Oct 2005 16:46:10 -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:

[snip]
> >     The IP address of b2n1 is 192.58.3.196; and
> >
> >     The IP address of tgp48 is 140.90.85.102.
> >
> > Please tell me if this is incorrect.
> 
> Yes that is correct,  I know in the earlier message I referred to b2n1 
> as 192.58.3.207 but 192.58.3.196 is the same node.
> 
> > Are there any other messages from PID 20832 in the tgp48 log file
> > between the above two?
> 
> There is nothing else for 20832 between those two entries...

Then I think I know the problem.  There's a bug in version 6.3.0 of the
upstream LDM code that's activated if and when an upstream LDM hasn't
sent a data-product for 30 seconds and a subsequent attempt to flush the
connection via a NULLPROC message times-out.  How this bug presents is
not known.  In your case it appears to cause the upstream LDM to hang.

Is it possible to upgrade the LDM on tgp48?  The latest version is
6.4.2.  An upgrade shouldn't take more than 5 minutes.

Regards,
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.