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

20030611: interpreting LDM 6.0.13 logfile messages

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: 20030611: interpreting LDM 6.0.13 logfile messages
  • Date: Wed, 11 Jun 2003 14:27:17 -0600
Robert,

>Date: Wed, 11 Jun 2003 15:16:30 -0500
>From: Robert Leche <address@hidden>
>Organization: Louisiana State University
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20030611: interpreting LDM 6.0.13 logfile messages

The above message contained the following:

> Sirocco does have a running LDM. The ldmd.conf has an allow line for
> seistan.<br> &nbsp;LDM communication&nbsp; only stopped a couple of
> hours ago and I don not know why. <br>

Interesting.  The log entries from Seistan's and Sirocco's LDM-s for the
relevant time period might be enlightening.

I note that I can connect to Sirocco's LDM 6 using the well-known
LDM port:

    $ rpcinfo -n 388 -t sirocco.srcc.lsu.edu 300029 6
    program 300029 version 6 ready and waiting

Regards,
Steve Emmerson