Re: [conduit] NCEP CONDUIT Services Fully Restored

Hi Pete,

Thanks for bringing this to our attention! I checked vm-lnx-conduit2 and confirmed that it was about 6 minutes ahead for its' system time. It seems the NTP that was enabled on this system to keep its' time synced is not functioning properly so I've opened a ticket to have our sys admins look at that. For now we've had the system rebooted which brought its' system time back in line with what it should be. Thanks again.

On Thu, Sep 22, 2022 at 4:33 PM Pete Pokrandt <address@hidden> wrote:

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

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 - address@hidden

From: conduit <address@hidden> on behalf of Dustin Sheffler - NOAA Federal via conduit <address@hidden>
Sent: Wednesday, September 21, 2022 5:07 PM
To: address@hidden <address@hidden>
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: address@hidden

Google Voice: (301) 683-3827