[LDM #RKK-379892]: LDM logging and operation issues

Evan,

I want to solve the problem of a downstream LDM on host c109-10 receiving data
from an upstream LDM on host ldm.atmos.colostate.edu first.  It is likely
that solving this problem will solve the other problem.

> Attached is the LDM log file for the problem with receiving NEXRAD2 data from
> our assigned upstream host:
> 
> Jul 05 22:02:02 c109-10 rpc.ldmd[9471] NOTE: Starting Up (version: 6.6.4;
> built: May 29 2007 18:16:01)
> Jul 05 22:02:02 c109-10 rpc.ldmd[9471] NOTE: Using local address 0.0.0.0:388
...
> Jul 05 22:02:02 c109-10 ldm.atmos.colostate.edu[9474] NOTE: Starting
> Up(6.6.4): ldm.atmos.colostate.edu:388 20070705210202.806 TS_ENDT {{NEXRAD2,
> ".*"}}
> Jul 05 22:02:02 c109-10 ldm.atmos.colostate.edu[9474] NOTE: LDM-6 desired
> product-class: 20070705210202.807 TS_ENDT {{NEXRAD2,  ".*"},{NONE,
> "SIG=b9bf6af170acc799503ce55a8fb7f075"}}
...
> Jul 05 22:02:02 c109-10 ldm.atmos.colostate.edu[9474] ERROR: Disconnecting due
> to LDM failure; Upstream LDM didn't reply to FEEDME request; RPC:
> Authentication error; why = (authentication error 5)

The above does appear to indicate that the LDM on c109-10 is not
allowed to receive NEXRAD2 data-products from the LDM on 
ldm.atmos.colostate.edu.  This could be because the LDM configuration-
file on ldm.atmos.colostate.edu doesn't have an appropriate ALLOW
entry for c109-10 for that data.

The way to verify whether or not c109-10 is allowed to receive that
data is to execute the following command as the LDM user on c109-10:

notifyme -vl- -f NEXRAD2 -h ldm.atmos.colostate.edu -o 3600

The output of this command will indicate 1) whether c109-10 is allowed
to connect and 2) whether ldm.atmos.colostate.edu has that data.

If c109-10 is not allowed to connect, then everything is *not* OK
on ldm.atmos.colostate.edu and you will have to work with the LDM
user on that system to fix the problem.  Have the LDM user on that
system verify that your IP address can be converted into a fully-
qualified hostname and that a regular expression for that hostname
exists in the LDM configuration file on that system for the NEXRAD2
data.

If that system can't convert your IP address into a hostname, then
the LDM configuration-file on that system must have an ALLOW entry
for that data with a regular expression that matches the IP address
instead of the hostname.

I note that ldm.atmos.colostate.edu does not allow an LDM at the
Unidata Program Center to connect:

~/udunits2/src/lib: notifyme -vl- -f NEXRAD2 -h ldm.atmos.colostate.edu -o 3600
Jul 06 15:07:35 notifyme[28220] NOTE: Starting Up: ldm.atmos.colostate.edu: 
20070706140735.913 TS_ENDT {{NEXRAD2,  ".*"}}
Jul 06 15:07:35 notifyme[28220] NOTE: LDM-5 desired product-class: 
20070706140735.913 TS_ENDT {{NEXRAD2,  ".*"}}
Jul 06 15:07:35 notifyme[28220] INFO: Resolving ldm.atmos.colostate.edu to 
129.82.48.22 took 0.055876 seconds
Jul 06 15:07:35 notifyme[28220] ERROR: NOTIFYME(ldm.atmos.colostate.edu): 7: 
Access denied by remote server
Jul 06 15:07:42 notifyme[28220] NOTE: exiting

which is contrary to our advice.  It is likely, therefore,
that a problem exists with that host's LDM.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RKK-379892
Department: Support LDM
Priority: Normal
Status: On Hold