[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDD #KKC-827781]: idd.unidata does not appear to be reachable
- Subject: [IDD #KKC-827781]: idd.unidata does not appear to be reachable
- Date: Thu, 09 Jul 2020 11:20:27 -0600
Hi Daryl,
re:
> I've lost my connection with idd.unidata LDM, from metfs1.agron.iastate.edu
>
> $ notifyme -v -l - -h idd.unidata.ucar.edu
> 20200709T161505.278214Z notifyme[30751] notifyme.c:main:363
> NOTE Starting Up: idd.unidata.ucar.edu: 20200709161505.277411
> TS_ENDT {{ANY, ".*"}}
> 20200709T161505.278413Z notifyme[30751] ldm5_clnt.c:forn5:460
> NOTE LDM-5 desired product-class: 20200709161505.277411 TS_ENDT
> {{ANY, ".*"}}
> 20200709T161505.284850Z notifyme[30751] error.c:err_log:236
> INFO Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.006022
> seconds
> 20200709T161555.285250Z notifyme[30751] ldm5_clnt.c:forn5:460
> NOTE LDM-5 desired product-class: 20200709161505.277411 TS_ENDT
> {{ANY, ".*"}}
> 20200709T161555.326053Z notifyme[30751] error.c:err_log:236
> INFO Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.040652
> seconds
> 20200709T161645.326693Z notifyme[30751] ldm5_clnt.c:forn5:460
> NOTE LDM-5 desired product-class: 20200709161505.277411 TS_ENDT
> {{ANY, ".*"}}
> 20200709T161645.329415Z notifyme[30751] error.c:err_log:236
> INFO Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.00238
> seconds
> 20200709T161735.330870Z notifyme[30751] ldm5_clnt.c:forn5:460
> NOTE LDM-5 desired product-class: 20200709161505.277411 TS_ENDT
> {{ANY, ".*"}}
> 20200709T161735.368177Z notifyme[30751] error.c:err_log:236
> INFO Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.036779
> seconds
> ^C20200709T161737.936746Z notifyme[30751] notifyme.c:cleanup:68
> NOTE exiting
>
> I connected to iddb for now.
Service from idd.unidata.ucar.edu should be back now. There was a power
failure on a module at the NWSC (Wyoming Supercomputer Center) that
caused loss of connectivity for everything connected to it including
the Front Range GigaPop (FRGP). All of the real-server backend
machines for idd.unidata.ucar.edu were also cutoff, so now data could
flow to or from them. Based on the status emails that were provided
to us, we did not expect that the outage would last for as long as
it did, so we opted to not send a note of warning to, for instance,
address@hidden. Unfortunately, the module replacement
took longer than expected, so service was interrupted for a large
fraction of an hour.
Please let us know if your access to/feeds from idd.unidata.ucar.edu
have not returned like ours have.
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: KKC-827781
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.