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

[IDD #KAR-675101]: NEXRAD2 data

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 #KAR-675101]: NEXRAD2 data
  • Date: Thu, 08 Jan 2015 14:52:11 -0700
Hi Terri,

re:
> Should have included this the first time, but upon restart of the ldm, these 
> errors show up
> in the log file:
> 
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8776] NOTE: LDM-6 desired 
> product-class: 20150108203305.947 TS_ENDT {{UNIWISC,  ".*"},{NONE,  
> "SIG=89c21dc5a9e8337274f139738306f970"}}
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8787] NOTE: LDM-6 desired 
> product-class: 20150108203305.947 TS_ENDT {{CONDUIT,  "/ndfd/Y[CEF]U"},{NONE, 
>  "SIG=e0514522efd0999608055ae43bb17569"}}
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8789] NOTE: LDM-6 desired 
> product-class: 20150108203305.949 TS_ENDT {{NEXRAD2,  
> "KFTG|KCYS|KGLD|KLNX|KAMA|KFDX|KLBB"},{NONE,  
> "SIG=d8709c4eba5558050ebb400a687890dc"}}
> Jan  8 21:33:05 longs 192.168.10.35[8779] NOTE: LDM-6 desired product-class: 
> 20150108203305.951 TS_ENDT {{EXP,  ".*"},{NONE,  
> "SIG=e3fd8a4170e654905ba20347c2ab782d"}}
> Jan  8 21:33:05 longs 192.168.10.35[8779] ERROR: Disconnecting due to LDM 
> failure; Couldn't connect to LDM on 192.168.10.35 using either port 388 or 
> portmapper; : RPC: Program not registered
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8776] ERROR: Disconnecting due to 
> LDM failure; nullproc_6 failure to idd.unidata.ucar.edu; RPC: Unable to 
> receive; errno = Connection reset by peer
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8787] ERROR: Disconnecting due to 
> LDM failure; nullproc_6 failure to idd.unidata.ucar.edu; RPC: Unable to 
> receive; errno = Connection reset by peer
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8789] ERROR: Disconnecting due to 
> LDM failure; nullproc_6 failure to idd.unidata.ucar.edu; RPC: Unable to 
> receive; errno = Connection reset by peer
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8790] NOTE: LDM-6 desired 
> product-class: 20150108203305.975 TS_ENDT {{IDS|DDPLUS,  ".*"},{NONE,  
> "SIG=0965f8d626482f3c762c8709e89e9c1b"}}
> Jan  8 21:33:05 longs idd.unidata.ucar.edu[8790] ERROR: Disconnecting due to 
> LDM failure; nullproc_6 failure to idd.unidata.ucar.edu; RPC: Unable to 
> receive; errno = Connection reset by peer

This log output seems to indicate that there is a network problem that your 
machine 'longs'
is on.  I say this because I see a problem connecting to the LDM at address 
192.168.10.35
before seeing the errors disconnecting from idd.unidata.ucar.edu.

Question:

- does 'longs' have a REQUEST to 192.168.10.35 or is the REQUEST to a machine 
name?

  I ask because a failure when the REQUEST is to a name rather than IP may
  indicate that there is some sort of DNS problem.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: KAR-675101
Department: Support IDD
Priority: Normal
Status: Open