[CONDUIT #PGY-808322]: Upcoming NCEP CONDUIT maintenance

Hi Justin,

re:
> I've bringing Kyle into the loop on this, can you do a traceroute to
> ncepldm4.woc.noaa.gov?

traceroute from atm.ucar.edu to ncepldm4.woc.noaa.gov:

% traceroute ncepldm4.woc.noaa.gov
traceroute: Warning: Multiple interfaces found; using 128.117.12.35 @ igb0
traceroute to ncepldm4.woc.noaa.gov (140.172.17.205), 30 hops max, 40 byte 
packets
 1  ml-mr-j1-es-n12 (128.117.12.251)  5.925 ms  1.568 ms  1.555 ms
 2  mlra-ml-mr-j1-es-net (128.117.243.55)  0.303 ms  4.688 ms  1.475 ms
 3  tcom-gs-1-n243-72 (128.117.243.77)  2.637 ms  0.529 ms  0.476 ms
 4  xe-0-1-2.873.core-l3.frgp.net (128.117.243.9)  1.207 ms  1.216 ms  1.221 ms
 5  noaa-i2.frgp.net (128.117.243.11)  3.280 ms  1.527 ms  1.684 ms
 6  2001-mlx8-eth-1-2.boulder.noaa.gov (140.172.2.18)  1.641 ms  1.568 ms  
1.583 ms
 7  mdf-mlx8-ve-703.boulder.noaa.gov (140.172.2.21)  11.171 ms  1.527 ms  1.518 
ms
 8  * * *
 9  * * *
10  * * *
 ...
30  * * *

traceroute from daffy.unidata.ucar.edu to ncepldm4.woc.noaa.gov:

% traceroute ncepldm4.woc.noaa.gov
traceroute to ncepldm4.woc.noaa.gov (140.172.17.205), 30 hops max, 60 byte 
packets
 1  flra-n140.unidata.ucar.edu (128.117.140.253)  0.336 ms  0.481 ms  0.553 ms
 2  noaa-nlr.frgp.net (128.117.243.19)  3.471 ms  3.467 ms  3.449 ms
 3  mdf-mlx8-eth-2-6.boulder.noaa.gov (140.172.2.30)  0.491 ms  0.480 ms  0.489 
ms
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
 ...
30  * * *


Here is an example message being generated in the LDM log file on
daffy.unidata.ucar.edu:

Jun  5 13:41:38 daffy ncepldm4.woc.noaa.gov[29549] ERROR: Disconnecting due to 
LDM failure; Couldn't connect to LDM on ncepldm4.woc.noaa.gov using either port 
388 or portmapper; : RPC: Remote system error - Connection timed out

The Connection timed out messages repeat every minute or so (when
the LDM on daffy retries to connect to ncepldm4.woc.noaa.gov).

A review of the LDM log files on daffy show that the inability to connect
to ncepldm4.woc.noaa.gov has been going on since at least early May (but I
did not check to see if this has been a constant failure since May 4).

We didn't notice the REQUEST failure because daffy is redundantly REQUESTing
CONDUIT data from ncepldm4.woc.noaa.gov and conduit.ncep.noaa.gov.  Plus, our
top level IDD relay node for CONDUIT (and LOTS of other feeds) is redundantly
REQUESTing from other top level CONDUIT relays.  The redundant REQUESTs are
working as they should: CONDUIT data continues to flow into idd.unidata.ucar.edu
and out to machines that are REQUESTing CONDUIT from idd.unidata.ucar.edu.

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: PGY-808322
Department: Support CONDUIT
Priority: Normal
Status: Closed