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.
Hi Justin, re: >CONDUIT team, > >Overnight at around 6:00Z there was a disk failure with our servers in >Boulder that stopped our ability to send data to ftpprd, NOMADS, and >CONDUIT. Our system administrators are working to rebuild the failed disks >but it could take several days until the system is back online. Our servers >here in College Park at NCWCP are still available and the >conduit.ncep.noaa.gov LDM connection is not affected by the outage. > >Just wanted to give you a heads up in case you noticed you're no longer >getting data from Boulder. I just ran a 'notifyme' to ncepldm4.woc.noaa.gov from a UPC machine, and it shows that the newest CONDUIT data available was from about 19:57 (it is currently 20:02). The other interesting thing I see from real-time stats plots is a new source of CONDUIT: vm-lnx-conduit1.ncep.noaa.gov I am assuming that the advice is to re-activate feed REQUESTs to conduit.ncep.noaa.gov to make sure that data keeps flowing. I have just done this at the UPC. re: >We'll send a note once Boulder is back online. Thanks for the update! Cheers, Tom -- +----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/* +----------------------------------------------------------------------------+