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

[LDM #JVG-389825]: ldm: can't contact portmapper



John,

> I recently installed ldm-6.10.1 on a box running CentOS 6.2. When I
> start ldm, I get the following errors:

The relevant log messages are

> May 15 17:05:16 caic0 ldm.madis-data.nws.noaa.gov[5830] NOTE: Starting 
> Up(6.10.1): ldm.madis-data.nws.noaa.gov:388 20120515220516.969 TS_ENDT 
> {{FSL2,  ^FSL.CompressedNetCDF.MADIS.(metar|sao|mesonet2|hydro2|snow)"}}
> May 15 17:05:16 caic0 ldm.madis-data.nws.noaa.gov[5830] NOTE: Previous 
> product-information file ".8811ad68602339cf39acbeef481ae754.info" doesn't 
> exist
> May 15 17:05:16 caic0 ldm.madis-data.nws.noaa.gov[5830] NOTE: LDM-6 desired 
> product-class: 20120515220516.970 TS_ENDT {{FSL2, 
> "^FSL.CompressedNetCDF.MADIS.metar|sao|mesonet2|hydro2|snow)"}}
> May 15 17:05:17 caic0 ldm.madis-data.nws.noaa.gov[5830] ERROR: Disconnecting 
> due to LDM failure; nullproc_6 failure to ldm.madis-data.nws.noaa.gov; RPC: 
> Unable to receive; errno = Connection reset by peer
> May 15 17:05:17 caic0 ldm.madis-data.nws.noaa.gov[5830] NOTE: LDM-6 desired 
> product-class: 201205152205 17.111 TS_ENDT {{FSL2, 
> "^FSL.CompressedNetCDF.MADIS.(metar|sao|mesonet2|hydro2|snow)"}}

These messages indicate that the downstream LDM process on host "caic0" 
couldn't connect to the upstream LDM server on host 
"ldm.madis-data.nws.noaa.gov". This is consistent with your ldmping(1) results:

> Snow 202% ldmping -vl- -h fcst.mtnweather.info
> May 15 23:30:54 INFO:      State    Elapsed Port   Remote_Host
> rpc_stat
> May 15 23:30:54 INFO: Resolving fcst.mtnweather.info to 67.174.122.3
> took 0.049939 seconds
> May 15 23:30:55 ERROR:  ADDRESSED   0.262519    0
> fcst.mtnweather.info  RPC: Unable to receive; errno = Connection reset
> by peer
> May 15 23:31:30 ERROR:      NAMED  10.000169    0
> fcst.mtnweather.info  can't contact portmapper: RPC: Timed out

A downstream LDM will try using the portmapper on the upstream LDM host if and 
only if the downstream LDM can't connect directly with the upstream LDM server 
using port 388; consequently, the "portmapper" error-message is a red herring.

It appears that port 388 on host "ldm.madis-data.nws.noaa.gov" cannot be 
accessed by host "caic0". ldmping(1) is a better test than your nc(1) command, 
in this regard, because it actually sends and receives data.

I suggest you consult with your network administrator to resolve the port 388 
issue.

> The ldm machine is running on a LAN, so I forwarded port 388 in the
> router to this machine (caic0). Are there other ports that need to be
> forwarded?
> 
> I turned off the firewalls in both the router and the ldm machine, but
> that did not work either.
> 
> Some other potentially useful information:
> 
> address@hidden etc]# rpcinfo -p
> program vers proto   port  service
> 100000    4   tcp    111  portmapper
> 100000    3   tcp    111  portmapper
> 100000    2   tcp    111  portmapper
> 100000    4   udp    111  portmapper
> 100000    3   udp    111  portmapper
> 100000    2   udp    111  portmapper
> 100024    1   udp  59270  status
> 100024    1   tcp  34968  status
> 300029    6   tcp    388  ldmd
> 300029    5   tcp    388  ldmd
> 
> From a machine outside the LAN:
> 
> Snow 218% nc -v -z fcst.mtnweather.info 388
> Connection to fcst.mtnweather.info 388 port [tcp/sunrpc] succeeded!
> 

> 
> Any thoughts on where to go from here?
> 
> Thanks,
> John Snook


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JVG-389825
Department: Support LDM
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.