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

Re: No CONDUIT data since ~20 UTC?

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: Re: No CONDUIT data since ~20 UTC?
  • Date: Wed, 23 Mar 2005 19:15:10 -0700
To slide things along,

I manually inserted the rest of the 18Z ETA, 1 degree GFS and 2.5 degree GFS
files just before 00Z. I also inserted the 00Z nam up to 18 hours when
the queue restarted.

Steve

On Wed, 23 Mar 2005, Brent Gordon wrote:

> All,
>
> There was a system crash at NWS/TOC late today.  When the server came
> back up it was not able to send data to the conduit server for some
> reason.  I restarted the software that feeds the conduit server and I
> have noticed 00 UTC NAM data starting to flow to conduit.  We will
> investigate what caused this outage.  Sorry for the inconvenience.
>
> Brent gordon
> NCO
>
>
> Steve Chiswell wrote:
>
> >On Wed, 2005-03-23 at 15:43, David Ovens wrote:
> >
> >
> >>All,
> >>
> >>We're seeing the same effects here.
> >>
> >>David
> >>
> >>
> >
> >David and Pete,
> >
> >The CONDUIT server is up, however the machines at NWS that
> >insert the products aren't queueing anything since 19:55Z.
> >
> >The following message was sent by NWS a short while ago.
> >
> >845
> >NOUS71 KNCF 232220
> >ADANCF
> >PLEASE PASS TO MIC, HIC, ESA, SOO, ITO
> >~
> >DUE TO SERVER PROBLEMS AT NCEP MODEL DATA ORIGINATING
> >THERE IS DELAYED.  FURTHER INFORMATION WILL BE PROVIDED
> >AS IT BECOMES AVAILABLE.
> >~
> >NCF/BB
> >
> >
> >We'll let you know what we find out.
> >
> >Steve Chiswell
> >Unidata User SUpport
> >
> >
>
>