Thanks, Dustin.
Just a quick note to let you know that it looks like the time on one of the
main CONDUIT ingest machines (vm-lnx-conduit2.ncep.noaa.gov) is drifting. We
aren't losing any data right now, but that should probably be fixed sometime.
Pete
[cid:d2ddae8c-4674-4ad8-a300-0a9f8019ccef]
https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+thredds.aos.wisc.edu
Pete Pokrandt - System Engineer IV
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx
________________________________
From: conduit <conduit-bounces@xxxxxxxxxxxxxxxx> on behalf of Dustin Sheffler -
NOAA Federal via conduit <conduit@xxxxxxxxxxxxxxxx>
Sent: Wednesday, September 21, 2022 5:07 PM
To: support-conduit@xxxxxxxxxxxxxxxx <conduit@xxxxxxxxxxxxxxxx>
Subject: [conduit] NCEP CONDUIT Services Fully Restored
Conduit Users,
An overnight network issue had caused problems for many of our dataflows
lasting into this afternoon as data caught back up. We had thought that CONDUIT
services were restored by late morning but didn't notice until this afternoon
that the grib insert process on our systems was continuing to fail. We finally
restored data to NCEP Conduit servers around ~5:30pm EDT (2130 UTC).
Unfortunately earlier model runs are not recoverable. We apologize for the
inconvenience.
--
Dustin Sheffler
NCEP Central Operations - Dataflow
Email: dustin.sheffler@xxxxxxxx<mailto:dustin.sheffler@xxxxxxxx>
Google Voice: (301) 683-3827<tel:%28301%29%20683-1400>
<tel:%28301%29%20683-1400>
![PNG image](pngojGyirwPVH.png)