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

[LDM #FDF-961547]: No data from the upgraded LDM server

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: [LDM #FDF-961547]: No data from the upgraded LDM server
  • Date: Fri, 07 Mar 2014 09:11:58 -0700
Hiro,

> Full Name: Hiro Gosen
> Email Address: address@hidden
> Organization: CIRA/CSU
> Package Version: 6.11.6
> Operating System: CentOS Release 5.10
> Hardware: Dell Precision T5500
> Description of problem: I updated LDM 6.6.5 to 6.11.6 and I'm not able to 
> distribute my data to other LDM systems (clients).  I've included a partial 
> log file that indicates problem with port388 and some troubleshooting I've 
> done.  The ldm server is able to use the pqinsert to process my data, and it 
> looks good, but for some reason the connection from the "client" side is not 
> working and they're not able to retrieve the data.  Is there some other 
> config file that I need to modify for the newer version?

The relevant hostnames and IP addresses are:

    awips.cira.colostate.edu   129.82.109.147
    awips1.cira.colostate.edu  129.82.109.124
    awips72.cira.colostate.edu 129.82.109.135

The downstream LDM log file on Awips72 contained lines like this:

    Mar 06 23:50:49 awips72 awips.cira.colostate.edu[6805] NOTE: LDM-6 desired 
product-class: 20140306225049.183 TS_ENDT {{EXP,  "CIRA.AWIPS.WC.ABIWRFWV.*"}} 
    Mar 06 23:50:49 awips72 awips.cira.colostate.edu[6805] ERROR: Disconnecting 
due to LDM failure; Couldn't connect to LDM on awips.cira.colostate.edu using 
either port 388 or portmapper;: RPC: Program not registered

This indicates that Awips72's LDM couldn't connect to Awips' LDM -- probably 
because it's not allowed, either by firewall rules or by not matching an ALLOW 
entry in Awips' LDM configuration-file.

netstat(1) on Awips1 printed lines like this:

    [root@awips1 ~]# netstat -A inet -t -n | grep 388
    tcp        0      0 129.82.109.124:35203        129.82.109.147:388          
ESTABLISHED 
    ...

Unfortunately, this information isn't relevant because host Awips72 isn't 
mentioned.

I recommend checking the LDM log file on Awips for relevant entries regarding 
Awips72 (there might not be any) and verifying that the LDM configuration file 
on Awips has an ALLOW entry that authorizes connections from Awips72. If both 
of these indicate that Awips72 should be able to connect, then I would check 
your firewall rules (IP tables?) to ensure that Awips72 isn't blocked from 
connecting.

Incidentally, you can use the notifyme(1) utility of the LDM package to check 
authorization by executing the following command on Awips72:

    notifyme -vl- -h awips.cira.colostate.edu

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FDF-961547
Department: Support LDM
Priority: Normal
Status: Closed