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

20030325: LDM6-RPC Bind Errors

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: 20030325: LDM6-RPC Bind Errors
  • Date: Tue, 25 Mar 2003 09:19:28 -0700
Hi Charlie,

> To: address@hidden
> From: Charlie Murphy <address@hidden>
> Subject: LDM6 - RPC Bind errors
> Organization: UCAR/Unidata

The above message contained the following:

> We are having problems with our LDM-6, the log file (which is attached)
> contains these error messages:
> 
> Mar 25 14:50:54 hurri ldm[365]: Couldn't create version 5 client handle: 
> RPC: Rpcbind failure - RPC: Timed out

The above indicates that your LDM couldn't connect to an upstream LDM-5
because the connection-attempt to the upstream's portmaper timed-out.
This kind of connection (to an LDM-5 using the portmapper) is the last
one the LDM-6 tries.  When it fails, it prints this message.

The facts that your LDM-6 used to work and you're now having problems
after your firewall crashed is a very strong indication that the problem
lies with your firewall.  Make sure that the firewall forwards packets
destined for port 388 without interference (in BOTH directions).

> Mar 25 14:54:27 hurri rtstats[362]: 
> clnt_create(rtstats.unidata.ucar.edu, 300029, 5, "tcp"): 
> rtstats.unidata.ucar.edu: RPC: Miscellaneous tli error - An event 
> requires attentionError 0
> Mar 25 14:56:46 hurri last message repeated 2 times

The above indicates, basically, the same thing as before -- except for
the rtstats utility rather than the LDM itself.

> We got essentially no data yesterday and some is flowing today.
> 
> This started yesteday (Monday) after a power outage all weekend - when we
> booted up these errors occured. Our networking people said the firewall
> server went down last week and there have been some problems with it
> since.
> 
> Does this look like a local problem that could be firewall related??

Absolutely.

The ldmping utility might prove useful.  Try using it to "ping" the
upstream LDM.

Regards,
Steve Emmerson