[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[CONDUIT #PGY-808322]: Upcoming NCEP CONDUIT maintenance
- Subject: [CONDUIT #PGY-808322]: Upcoming NCEP CONDUIT maintenance
- Date: Thu, 05 Jun 2014 12:17:55 -0600
Hi Justin,
re:
> Today our network team made the required configuration changes to our
> Boulder server to allow connections from 128.117.12.35. Can you test
> connecting from that system to ncepldm4.woc.noaa.gov?
It appears that the connection is still being blocked. Here is the output
from the LDM 'notifyme' invocation that I just tried:
on atm.ucar.edu:
% notifyme -vl- -f CONDUIT -h ncepldm4.woc.noaa.gov
Jun 05 18:13:32 notifyme[2876] NOTE: Starting Up: ncepldm4.woc.noaa.gov:
20140605181332.843 TS_ENDT {{CONDUIT, ".*"}}
Jun 05 18:13:32 notifyme[2876] NOTE: LDM-5 desired product-class:
20140605181332.843 TS_ENDT {{CONDUIT, ".*"}}
Jun 05 18:13:32 notifyme[2876] INFO: Resolving ncepldm4.woc.noaa.gov to
140.172.17.205 took 0.09562 seconds
Jun 05 18:14:22 notifyme[2876] NOTE: LDM-5 desired product-class:
20140605181332.843 TS_ENDT {{CONDUIT, ".*"}}
Jun 05 18:14:22 notifyme[2876] INFO: Resolving ncepldm4.woc.noaa.gov to
140.172.17.205 took 0.000982 seconds
...
As a reality check, I followed-up the test from atm.ucar.edu with a
test on our long-existing CONDUIT ingest machine, daffy.unidata.ucar.edu:
% notifyme -vl- -f CONDUIT -h ncepldm4.woc.noaa.gov
Jun 05 18:15:20 notifyme[14397] NOTE: Starting Up: ncepldm4.woc.noaa.gov:
20140605181520.434 TS_ENDT {{CONDUIT, ".*"}}
Jun 05 18:15:20 notifyme[14397] NOTE: LDM-5 desired product-class:
20140605181520.434 TS_ENDT {{CONDUIT, ".*"}}
Jun 05 18:15:20 notifyme[14397] INFO: Resolving ncepldm4.woc.noaa.gov to
140.172.17.205 took 0.006105 seconds
Jun 05 18:16:13 notifyme[14397] NOTE: LDM-5 desired product-class:
20140605181520.434 TS_ENDT {{CONDUIT, ".*"}}
Jun 05 18:16:13 notifyme[14397] INFO: Resolving ncepldm4.woc.noaa.gov to
140.172.17.205 took 0.002781 seconds
...
As you can see, neither machine can reach ncepldm4.woc.noaa.gov now.
Question:
- is it possible that the firewall change went completely awry?
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