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

[IDD #FBU-715927]: ldm connection problem

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: [IDD #FBU-715927]: ldm connection problem
  • Date: Mon, 01 Oct 2007 13:08:02 -0600
Mike,

> OK, I did that, but nothing logs from "chinook". At the same time I
> had tcpdump running, which showed a small amount of traffic to and
> from Chinook. At the same time I had Mike Frost at NRL run and
> "ldmping" to rossby...(besides having ldm running).
> 
> Here is what "tail -f ldmd.log" shows:
> ---------------------------
> Oct 01 16:32:54 rossby rpc.ldmd[27715] NOTE: Going verbose
> Oct 01 16:36:41 rossby 129.15.194.233[27732] ERROR: Terminating due
> to LDM failure; Couldn't connect to LDM on 129.15.194.233 using
> either port 388 or portmapper; : RPC: Remote system error -
> Connection timed out
> Oct 01 16:37:11 rossby 129.15.194.233[27732] NOTE: LDM-6 desired
> product-class: 20071001153711.977 TS_ENDT
> {{NEXRAD2,  ".*"},{NONE,  "SIG=1bd7e2ae56567d7e7f64ffe5a2a89043"}}
> Oct 01 16:43:30 rossby 129.15.194.233[27732] ERROR: Terminating due
> to LDM failure; Couldn't connect to LDM on 129.15.194.233 using
> either port 388 or portmapper; : RPC: Remote system error -
> Connection timed out
> Oct 01 16:44:00 rossby 129.15.194.233[27732] NOTE: LDM-6 desired
> product-class: 20071001154400.062 TS_ENDT
> {{NEXRAD2,  ".*"},{NONE,  "SIG=1bd7e2ae56567d7e7f64ffe5a2a89043"}}
> Oct 01 16:50:18 rossby 129.15.194.233[27732] ERROR: Terminating due
> to LDM failure; Couldn't connect to LDM on 129.15.194.233 using
> either port 388 or portmapper; : RPC: Remote system error -
> Connection timed out
> Oct 01 16:50:48 rossby 129.15.194.233[27732] NOTE: LDM-6 desired
> product-class: 20071001155048.147 TS_ENDT
> {{NEXRAD2,  ".*"},{NONE,  "SIG=1bd7e2ae56567d7e7f64ffe5a2a89043"}}
> Oct 01 16:57:06 rossby 129.15.194.233[27732] ERROR: Terminating due
> to LDM failure; Couldn't connect to LDM on 129.15.194.233 using
> either port 388 or portmapper; : RPC: Remote system error -
> Connection timed out
> Oct 01 16:57:36 rossby 129.15.194.233[27732] NOTE: LDM-6 desired
> product-class: 20071001155736.232 TS_ENDT
> {{NEXRAD2,  ".*"},{NONE,  "SIG=1bd7e2ae56567d7e7f64ffe5a2a89043"}}
> -----------------------------

It appears that Rossby isn't seeing any connection attempt from
Chinook.

> If this is an asyncronous network routing problem, which I think it
> is, I don't understand why rossby wouldn't try to at least register a
> connection attempt if we are seeing some traffic with tcpdump.

Did the "tcpdump" utility run on Rossby?  If not, then the firewall
rules on Rossby might be preventing it from seeing the packets from
Chinook.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FBU-715927
Department: Support LDM
Priority: Normal
Status: On Hold