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

Re: LDM error condition

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: LDM error condition
  • Date: Fri, 16 Dec 2005 09:21:33 -0700
Tom,

>Date: Fri, 16 Dec 2005 09:06:13 -0700
>From: "Tom Baltzer" <address@hidden>
>Organization: UCAR/Unidata
>To: "'Steve Emmerson'" <address@hidden>
>Subject: RE: LDM error condition

The above message contained the following:

> After some changes of configuration on the lead testbed systems, we have
> started receiving the following set of messages:
> 
> =20
> 
> Dec 16 15:55:22 lead4 idd[3352] ERROR: Terminating due to LDM failure;
> Couldn't connect to LDM on idd.unidata.ucar.edu using either port 388 or
> portmapper; : RPC: Remote system error - Connection refused=20

The above means that the downstream LDM on Lead4 couldn't connect to the
LDM server on Idd using either port 388 or the RPC portmapper.  The
reason is that the connection was refused.  The LDM log file on Idd
might prove illuminating.

> Dec 16 15:55:25 lead4 idd[3352] NOTE: LDM-6 desired product-class:
> 20051216154008.319 TS_ENDT {{WMO,  ".*"},{NONE,
> "SIG=3D29c3da510e9a3a49dcc86573fc307df0"}}=20

As so, the downstream LDM on Lead4 tries again.  The last WMO data-product
that it received had the given signature (MD5 checksum).

> Dec 16 15:55:25 lead4 idd[3352] NOTE: Product reclassification by =
> upstream
> LDM: 20051216154008.319 TS_ENDT {{WMO,  ".*"},{NONE,
> "SIG=3D29c3da510e9a3a49dcc86573fc307df0"}} -> 20051216154008.319 TS_ENDT
> {{WMO,  ".*"}}=20

The downstream LDM on Lead4 was able to connect but the version of the 
upstream LDM on Idd is, apparently, earlier than 6.4 and, consequently,
the data-product specification in the request was changed as noted.

> Dec 16 15:55:25 lead4 idd[3352] NOTE: Upstream LDM-6 on =
> idd.unidata.ucar.edu
> is willing to be a primary feeder

Success.

> Can you tell me what that might imply?  Something to do w/network
> connectivity?

I see no problem other than the LDM on Idd should be upgraded.

> Thanks,
> Tom.
> 
> =20
> 
> Tom Baltzer
> 
> Software Engineer                                           =20
> 
> UCAR Office of Programs                               =20
> Unidata Program Center                                  =20
> P.O. Box 3000
> Boulder, CO 80307-3000

Regards,
Steve Emmerson