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.
Merrill, > To: address@hidden > From: Merrill Bean <address@hidden> > Subject: re: 20030515: request to upgrade to latest Unidata LDM release, > 6.0.11 (fwd) > Organization: PSL The above message contained the following: > Since the upgrade we haven't recieved data, error log shows: > May 29 14:36:41 mariaz pqbinstats[24982]: Starting Up (24980) > May 29 14:36:41 mariaz pqact[24983]: Starting Up > May 29 14:36:41 mariaz rtstats[24984]: Starting Up (24980) > May 29 14:36:41 mariaz nimbus[24985]: Connecting to upstream LDM using > protocol > version 6... > May 29 14:36:41 mariaz nimbus[24986]: Connecting to upstream LDM using > protocol > version 6... > May 29 14:36:42 mariaz nimbus[24985]: Upstream LDM is willing to feed > May 29 14:36:42 mariaz nimbus[24986]: Upstream LDM is willing to feed > May 29 14:39:50 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-6 > using > port 388: RPC: Remote system error - Connection timed out > May 29 14:40:50 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-6 > using > portmapper: RPC: Port mapper failure - RPC: Timed out > May 29 14:43:59 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-5 > using > port 388: RPC: Remote system error - Connection timed out > May 29 14:44:59 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-5 > using > portmapper: RPC: Port mapper failure - RPC: Timed out > May 29 14:45:29 mariaz usgodae3[24987]: Desired product class: > 20030529133641.69 > 1 TS_ENDT {{FNMOC, "^US058GMET-GR1mdl.0058_0240.*"}} > May 29 14:48:38 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-6 > using > port 388: RPC: Remote system error - Connection timed out > May 29 14:49:39 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-6 > using > portmapper: RPC: Port mapper failure - RPC: Timed out > May 29 14:52:48 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-5 > using > port 388: RPC: Remote system error - Connection timed out > May 29 14:53:48 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-5 > using > portmapper: RPC: Port mapper failure - RPC: Timed out > May 29 14:54:18 mariaz usgodae3[24987]: Desired product class: > 20030529133641.69 > 1 TS_ENDT {{FNMOC, "^US058GMET-GR1mdl.0058_0240.*"}} > May 29 14:57:27 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-6 > using > port 388: RPC: Remote system error - Connection timed out > May 29 14:58:27 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-6 > using > portmapper: RPC: Port mapper failure - RPC: Timed out > May 29 15:01:36 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-5 > using > port 388: RPC: Remote system error - Connection timed out > May 29 15:02:36 mariaz usgodae3[24987]: Couldn't connect to upstream LDM-5 > using > portmapper: RPC: Port mapper failure - RPC: Timed out > > Is this a problem with my system or the remote? The way I read the log its > not > working on the remote system, but the problem showed up after the upgrade so > I'm > trying to make sure. > Thanks > Merrill Bean > (sys admin for Max BLeiweiss) Judging from the above log entries, I'd say that host usgodae3 isn't on-line, isn't running an LDM, or isn't making it's LDM visible. I don't see anything that indicates a problem at your end. What's the fully-qualified hostname of usgodae3? Can you ping(1) that host? For example ping usgodae3... (use the fully-qualified hostname). What does an ldmping(1) of that host show? For example ldmping -vl- -h usgodae3... Regards, Steve Emmerson