[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 17:00:44 -0600
Hi,

re:
> The connection to iddb worked. I've updated my ldmd.conf and restarted
> ldm. Thanks!

I'm glad to hear that you are able to feed from iddb.unidata.ucar.edu!

I looked through the LDM log files on the backend node of 
the idd.unidata.ucar.edu cluster, and I found that your machine was
able to connect, but for some reason data was not flowing.  Here
is a snippet of the log file showing what I am referring to
(mostly "for the files"):

Starting Up(6.13.11/6): 20200709160002.809335 TS_ENDT {{CONDUIT, 
"gfs.*pgrb2"}}, SIG=612cd25cc0af17be9dbd6a7aafa6ae95, Primary
20200709T170003.954461Z ldm.cicsnc.org(feed)[22379] up6.c:up6_run:448           
        NOTE  topo:  ldm.cicsnc.org {{CONDUIT, (.*)}}
20200709T170004.447884Z ldm.cicsnc.org(feed)[22378] up6.c:up6_run:445           
        NOTE  Starting Up(6.13.11/6): 20200709160002.809331 TS_ENDT {{NOTHER, 
".*"}}, SIG=45df6a430d3f23930b279c1c993913ac, Primary
20200709T170004.447995Z ldm.cicsnc.org(feed)[22378] up6.c:up6_run:448           
        NOTE  topo:  ldm.cicsnc.org {{NOTHER, (.*)}}
20200709T170004.452616Z ldm.cicsnc.org(feed)[22380] up6.c:up6_run:445           
        NOTE  Starting Up(6.13.11/6): 20200709160002.809824 TS_ENDT 
{{IDS|DDPLUS, ".*"}}, SIG=54fd31947e9f88b99e5ab3bcff1e25c0, Primary
20200709T170004.452724Z ldm.cicsnc.org(feed)[22380] up6.c:up6_run:448           
        NOTE  topo:  ldm.cicsnc.org {{IDS|DDPLUS, (.*)}}
20200709T170005.585356Z ldm.cicsnc.org(feed)[22393] error.c:err_log:236         
        NOTE  Data-product with signature a1345ac8206b5929e02c9918371d2e04 
wasn't found in product-queue
20200709T170005.585714Z ldm.cicsnc.org(feed)[22393] up6.c:up6_run:445           
        NOTE  Starting Up(6.13.11/6): 20200709160004.488946 TS_ENDT {{CONDUIT, 
"nam.*awip12"}}, SIG=a1345ac8206b5929e02c9918371d2e04, Primary
20200709T170005.585807Z ldm.cicsnc.org(feed)[22393] up6.c:up6_run:448           
        NOTE  topo:  ldm.cicsnc.org {{CONDUIT, (.*)}}
20200709T170104.726064Z ldm.cicsnc.org[22621]       ldmd.c:cleanup:192          
        NOTE  Exiting
20200709T170204.872044Z ldm.cicsnc.org[23849]       ldmd.c:cleanup:192          
        NOTE  Exiting
20200709T170305.050639Z ldm.cicsnc.org[23976]       ldmd.c:cleanup:192          
        NOTE  Exiting
20200709T192412.939287Z ldm.cicsnc.org(feed)[22378] ldmd.c:cleanup:192          
        NOTE  Exiting
20200709T192414.879159Z ldm.cicsnc.org(feed)[22380] ldmd.c:cleanup:192          
        NOTE  Exiting
20200709T192542.297574Z ldm.cicsnc.org(feed)[8454]  up6.c:up6_run:445           
        NOTE  Starting Up(6.13.11/6): 20200709182541.199528 TS_ENDT {{NOTHER, 
".*"}}, SIG=d265302c0adf729b4da0652645d2a1ef, Primary
20200709T192542.297632Z ldm.cicsnc.org(feed)[8454]  up6.c:up6_run:448           
        NOTE  topo:  ldm.cicsnc.org {{NOTHER, (.*)}}
20200709T192542.298079Z ldm.cicsnc.org(feed)[8453]  up6.c:up6_run:445           
        NOTE  Starting Up(6.13.11/6): 20200709182541.199824 TS_ENDT 
{{IDS|DDPLUS, ".*"}}, SIG=bae1a36f7671a6c339f2defad2902b40, Primary
20200709T192542.298117Z ldm.cicsnc.org(feed)[8453]  up6.c:up6_run:448           
        NOTE  topo:  ldm.cicsnc.org {{IDS|DDPLUS, (.*)}}
20200709T193205.951367Z ldm.cicsnc.org(feed)[8453]  error.c:err_log:236         
        NOTE  Couldn't flush connection; flushConnection() failure to 
ldm.cicsnc.org: RPC: Unable to receive; errno = Connection reset by peer
20200709T193205.962453Z ldm.cicsnc.org(feed)[8453]  ldmd.c:cleanup:192          
        NOTE  Exiting
20200709T193209.634885Z ldm.cicsnc.org(feed)[8454]  error.c:err_log:236         
        NOTE  Couldn't flush connection; flushConnection() failure to 
ldm.cicsnc.org: RPC: Unable to receive; errno = Connection reset by peer

re:
> Here's the results of the traceroute idd.unidata.ucar.edu:
> 
> traceroute to idd.unidata.ucar.edu (128.117.135.3), 30 hops max, 60
> byte packets
>  1  fw2.cicsnc.org (10.0.1.1)  0.095 ms  0.073 ms 0.067 ms
>  2  gb-gw-to-noaa-cics-gw.ncren.net (128.109.7.129) 0.783 ms  0.783
> ms  0.811 ms
>  3  128.109.9.13 (128.109.9.13)  6.091 ms  6.135 ms 6.230 ms
>  4  rtp-gw-to-ws-gw.ncren.net (128.109.9.33)  8.472 ms 8.440 ms 
> 8.906 ms
>  5  et-3-3-0.613.rtsw.rale.net.internet2.edu (198.71.46.185)  9.470
> ms  9.430 ms  9.389 ms
>  6  ae-1.4079.rtsw.wash.net.internet2.edu (162.252.70.121)  14.464
> ms  14.410 ms  14.402 ms
>  7  ae-0.4079.rtsw2.ashb.net.internet2.edu (162.252.70.137)  28.332
> ms  17.992 ms  17.987 ms
>  8  ae-2.4079.rtsw.ashb.net.internet2.edu (162.252.70.74)  15.152
> ms  15.063 ms  15.010 ms
>  9  ae-20.4079.rtsw.clev.net.internet2.edu (162.252.70.129)  23.208
> ms  23.116 ms  23.081 ms
> 10  ae-3.4079.rtsw3.eqch.net.internet2.edu (162.252.70.131)  39.321
> ms  39.417 ms  39.453 ms
> 11  ae-5.4079.rtsw.eqch.net.internet2.edu (162.252.70.162)  31.694
> ms  41.289 ms  41.236 ms
> 12  ae-0.4079.rtsw.star.net.internet2.edu (162.252.70.111)  31.566
> ms  31.533 ms  31.486 ms
> 13  core-1850-ptr.frgp.net (192.43.217.223)  52.407 ms 52.375 ms 
> 54.304 ms
> 14  ml2core-corel3-i2.unet.ucar.edu (128.117.243.140) 53.965 ms 
> 53.893 ms  54.256 ms
> 15  ml1core-ml2core.unet.ucar.edu (128.117.243.98) 53.694 ms  54.195
> ms  54.104 ms
> 16  wymule-ml1core.unet.ucar.edu (128.117.243.153) 56.763 ms  57.239
> ms  56.828 ms
> 17  idd.unidata.ucar.edu (128.117.135.3)  55.958 ms 55.962 ms  55.948 ms

Thanks.  The traceroute shows that the path between the up and downstream
machines is not completely blocked.  I don't know why data didn't flow;
I'll ask Steve if he has any ideas.

re:
> Thanks again for your help,

No worries.

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: Closed
===================
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.