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

[LDM #JXP-631388]: No longer able to ldmping idd.unidata.ucar.edu

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: [LDM #JXP-631388]: No longer able to ldmping idd.unidata.ucar.edu
  • Date: Fri, 10 Jul 2020 08:19:36 -0600
Hi,

re:
> My server, ldm.cicsnc.org, 198.85.226.20, is no longer able to receive
> the IDS|DDPLUS feed from idd.unidata.ucar.edu. When I run "ldmping
> idd.unidata.ucar.edu" I get the following:
> 
> 20200710T135438.481891Z ldmping[9923] INFO
> ldmping.c:51:print_label()      State    Elapsed Port
> Remote_Host           rpc_stat
> 20200710T135438.482988Z ldmping[9923] INFO error.c:236:err_log()
> Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.000646 seconds
> 20200710T135448.483186Z ldmping[9923] ERROR
> ldmping.c:75:print_hstat() SVC_UNAVAIL  10.000959    0
> idd.unidata.ucar.edu  h_clnt_create(idd.unidata.ucar.edu): Timed out
> while creating connection
> 20200710T135513.483392Z ldmping[9923] ERROR
> ldmping.c:75:print_hstat()  ADDRESSED   0.000001    0
> idd.unidata.ucar.edu  h_clnt_create(idd.unidata.ucar.edu): Timed out
> while creating connection
> 20200710T135548.494483Z ldmping[9923] ERROR
> ldmping.c:75:print_hstat()      NAMED  10.010936    0
> idd.unidata.ucar.edu  can't contact portmapper: RPC: Timed out
> 
> We ran normal updates last night, but nothing changed as far as server
> name or IP is concerned. I have another ldm server I support and both
> idd.unidata.ucar.edu and ldm.cicsnc.org respond to it.
> 
> Any suggestions?

There were no ALLOW or firewall changes made on any of the real-server
backend machines of the idd.unidata.ucar.edu cluster, so our first thought
is that there is some firewall/security perimeter block that is at/near
your machine.

Can you try running the following:

<as 'ldm'>
notifyme -vl- -f ANY -h idd.unidata.ucar.edu

and send us the output.  We will use the information from the listing
to see if the connection REQUEST actually is making it to any of the
backend machines of the idd.unidata.ucar.edu cluster.

Thanks in advance...

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: JXP-631388
Department: Support IDD
Priority: Normal
Status: Open
===================
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.