[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:02:30 -0600
Robert,

>Date: Wed, 11 Jun 2003 14:47:28 -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:

> Looks like ldm traffic from Seistan to Sirocco died at noon. Seistan
> is reporting the following erroe messages.
> 
> [ldm@seistan ~/etc]$ ldmping sirocco
> Jun 11 19:39:28      State    Elapsed Port   Remote_Host           rpc_stat
> Jun 11 19:39:28      NAMED   0.003006    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:39:53      NAMED   0.001127    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:40:18      NAMED   0.001085    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:40:44      NAMED   0.001228    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:41:09      NAMED   0.001099    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:41:34      NAMED   0.001133    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:41:59      NAMED   0.001077    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused
> Jun 11 19:42:24      NAMED   0.001120    0   sirocco      can't contact 
> portmapper: RPC: Unable to receive; errno = Connection refused

The above indicates that Sirocco's LDM was unavailable -- specifically
because Seistan wasn't allowed to query Sirocco's portmapper to discover
on what port Sirocco's LDM was listening.  You need to know, however,
that a downstream LDM only queries the portmapper on the upstream host
after first trying to connect to the upstream LDM using the well-known
LDM port (#388).  The fact that the pormapper query failed also indicates
that the attempt on port 388 failed.

The above is consistent with several possibilities, one of which is that
Sirocco is not running an LDM.  Another possibility is that Sirocco
doesn't have an ALLOW line for Seistan in its LDM configuration file
(etc/ldmd.conf).

I note that I can, currently, ping Sirocco's LDM from here:

$ ldmping -i0 sirocco.srcc.lsu.edu
Jun 11 19:59:38      State    Elapsed Port   Remote_Host           rpc_stat
Jun 11 19:59:38 RESPONDING   0.074959  388   sirocco.srcc.lsu.edu  

> Thanks for the help Steve

You're most welcome.

> Bob
> ----------------------------------------------------------------
> Robert Leche
> System Administrator
> Louisiana State University - Southern Regional Climate Center
> 260 Howe-Russell Building
> Baton Rouge, La. 70803
> address@hidden
> 225 578 5023
> ----------------------------------------------------------------

Regards,
Steve Emmerson