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

[CONDUIT #AJR-640230]: Lost Boulder LDM

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: [CONDUIT #AJR-640230]: Lost Boulder LDM
  • Date: Mon, 05 Jan 2015 11:57:11 -0700
Hi Carissa,

re:
> 1 of the 3 (ncep-ldm2) Boulder CONDUIT LDM machines has been taken out
> permanently. It has been giving us grief and instead of putting resources
> into fixing it non-stop they have started the work of upgraded the entire
> Boulder infrastructure. Let me know if you have any issues with that.

This is not an issue for us as our machine that REQUESTs CONDUIT does so
redundantly from ncepldm4.woc.noaa.gov and conduit.ncep.noaa.gov.  I believe
that the same thing is (at least should be) true for the other Unidata
community top level CONDUIT relays.

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