Re: [conduit] [Ncep.list.pmb-dataflow] NCEP CONDUIT Outage planned

  • To: Anne Myckow - NOAA Federal <anne.myckow@xxxxxxxx>
  • Subject: Re: [conduit] [Ncep.list.pmb-dataflow] NCEP CONDUIT Outage planned
  • From: Pete Pokrandt <poker@xxxxxxxxxxxx>
  • Date: Mon, 22 Jun 2020 17:42:18 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=aos.wisc.edu; dmarc=pass action=none header.from=aos.wisc.edu; dkim=pass header.d=aos.wisc.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=a/iHvmmsi7wcQfynnO/1dJkJjEZSIaJSP3pPnD6DMDI=; b=Jfi34/yy3WXZHCcEHZ72TcvP+abEi6bZW3GVltfaO0+/AJJ2YlxVwVdjxtwKuIjdml74uDf7A63OQZ6P8fxT+8/4j17w0ocN69mOe8jnjVohtSBIVgrQT7Q64j+Gz7Fr5DVpDlHTXBg3DO9kwpZEoqAaPBPjq1hqym+tSB5MezTRJlwhaSjFrwky9GIaqCFZ/2CWWRAlLeXZGdNMXD2cJ7hhIDpDr6eVQmwOUd2rE5pzfWYvPfvp+pZS85UZFkIcx5IE5q0PlMivl2eCrezqp+jgPGKuluDPhWVh3eEtQrQY3eGFw4oB6+WZRAJFGz/UJQ9emAnfqsEbIszjJojnfw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=W+u+g35+JqIrgw8z0X+h3FQh/m9mZ4bm/g9c4c+L3XYOIlIWEWtEw0BpZZ13FlM0TJ4D5jlJOAC9mRdggiZ0DUcBKT26faFlHSuIVxFedU8JmJfIeRwzt0wUa9++lBPh1B4DVck883x/UsTuYPrCh/6jwJXgipsBCQQU+gGgmtJPfLzmEyoXnZNsbSntfEBuduxxjwdGvPNSfwGoLa1HM6UmX/J9Ww9eyV+SfaJC8dlzr0M17XZr4eKR8fbsujG/rgygEqoMsMhXGahPibqZ4ekw5QijljyXoh7BYBnIl85hwAG06VLEAuJhYxZELSLphhr+udWK4FY/oljzr74Fkw==
For what it's worth, it appears to me that the machine conduit.ncep.noaa.gov is 
not running one of the services used to keep the time accurate (either ntp or 
chrony depending on the installation) or perhaps one of these services is 
running, but can't reach a server to sync with because of firewall rules.

Here are a few articles that might help you determine if ntp or chrony is 
running, and how to get one or the other set up and running if it's not.

https://www.tecmint.com/install-chrony-in-centos-ubuntu-linux/
https://www.cyberciti.biz/faq/linux-unix-bsd-is-ntp-client-working/
https://www.techbrown.com/sync-time-timezone-centos-7/

Thanks for looking into the issue, and good luck!
Pete




<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx

________________________________
From: Anne Myckow - NOAA Federal <anne.myckow@xxxxxxxx>
Sent: Monday, June 22, 2020 7:31 AM
To: Pete Pokrandt <poker@xxxxxxxxxxxx>
Cc: Dustin Sheffler - NOAA Federal <dustin.sheffler@xxxxxxxx>; Carissa Klemmer 
- NOAA Federal <carissa.l.klemmer@xxxxxxxx>; _NCEP.List.pmb-dataflow 
<ncep.list.pmb-dataflow@xxxxxxxx>; support-conduit@xxxxxxxxxxxxxxxx 
<conduit@xxxxxxxxxxxxxxxx>; Unidata CONDUIT Support 
<support-conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [Ncep.list.pmb-dataflow] [conduit] NCEP CONDUIT Outage planned

Thanks Pete.

We will look into it.

On Fri, Jun 19, 2020 at 3:40 PM Pete Pokrandt 
<poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>> wrote:
Just an FYI the CONDUIT latency times continue to slowly increase. Unidata is 
seeing the same slowly increasing lags, so that suggests to me it is an issue 
with the source. I don't think we're actually getting data that much later, I 
think the clock has a slow drift on 
conduit.ncep.noaa.gov<http://conduit.ncep.noaa.gov>.

We are not experiencing any real problems with this right now, but if the lag 
grows larger than 3600 seconds, I am concerned we will begin losing data, since 
(as I understand it) the ldm doesn't ask for data more than an hour old.

Can you please have someone look into this at some point?

Thanks,
Pete

[cid:172dc02655bcb971f162]



<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>

________________________________
From: Dustin Sheffler - NOAA Federal 
<dustin.sheffler@xxxxxxxx<mailto:dustin.sheffler@xxxxxxxx>>
Sent: Friday, June 5, 2020 1:50 PM
To: Pete Pokrandt <poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>>
Cc: Carissa Klemmer - NOAA Federal 
<carissa.l.klemmer@xxxxxxxx<mailto:carissa.l.klemmer@xxxxxxxx>>; Anne Myckow - 
NOAA Federal <anne.myckow@xxxxxxxx<mailto:anne.myckow@xxxxxxxx>>; 
_NCEP.List.pmb-dataflow 
<ncep.list.pmb-dataflow@xxxxxxxx<mailto:ncep.list.pmb-dataflow@xxxxxxxx>>
Subject: Re: [Ncep.list.pmb-dataflow] [conduit] NCEP CONDUIT Outage planned

Hi Pete,

Thank you for passing along the information about the increasing lag times your 
seeing for CONDUIT ingest. That is a very interesting and telling graph for a 
slowly worsening issue. We will investigate and let you know what we find.

-Dustin


On Tue, Jun 2, 2020 at 5:15 PM 'Pete Pokrandt' via _NCEP list.pmb-dataflow 
<ncep.list.pmb-dataflow@xxxxxxxx<mailto:ncep.list.pmb-dataflow@xxxxxxxx>> wrote:
Carissa, Anne,

Thanks so much for keeping us updated on these outages.

FYI I think there is a slow clock drift on the CONDUIT source machine 
conduit.ncep.noaa.gov<http://conduit.ncep.noaa.gov>. I'm seeing the lags slowly 
increasing at my ingest site, and I see the same slow increase on 
conduit.unidata.ucar.edu<http://conduit.unidata.ucar.edu>. I don't see the same 
drift on data feeds from other sources.

Maybe the conduit.ncep.noaa.gov<http://conduit.ncep.noaa.gov> isn't running 
ntpd to keep the time accurate?

https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd-agg.aos.wisc.edu
https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+conduit.unidata.ucar.edu

[cid:172dc02655bcb971f161]

Thanks,
Pete




<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>

________________________________
From: conduit 
<conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx>> on 
behalf of Anne Myckow - NOAA Federal via conduit 
<conduit@xxxxxxxxxxxxxxxx<mailto:conduit@xxxxxxxxxxxxxxxx>>
Sent: Monday, June 1, 2020 1:00 PM
To: Carissa Klemmer - NOAA Federal 
<carissa.l.klemmer@xxxxxxxx<mailto:carissa.l.klemmer@xxxxxxxx>>
Cc: support-conduit@xxxxxxxxxxxxxxxx<mailto:support-conduit@xxxxxxxxxxxxxxxx> 
<conduit@xxxxxxxxxxxxxxxx<mailto:conduit@xxxxxxxxxxxxxxxx>>; 
_NCEP.List.pmb-dataflow 
<ncep.list.pmb-dataflow@xxxxxxxx<mailto:ncep.list.pmb-dataflow@xxxxxxxx>>
Subject: Re: [conduit] [Ncep.list.pmb-dataflow] NCEP CONDUIT Outage planned

Hello,

Wanted to let you know that the 6/3 outage has been moved to 6/8, same time .

Please let us know if you have any questions, thanks.
Anne

On Thu, May 28, 2020 at 8:23 PM Carissa Klemmer - NOAA Federal 
<carissa.l.klemmer@xxxxxxxx<mailto:carissa.l.klemmer@xxxxxxxx>> wrote:
Hello -

We have 2 dates of maintenance that I'd like to make you aware of, both of 
which may impact your ability to pull conduit data.

6/1 between 13-15Z
6/3 between 13-15Z

Expect that the outage will last the entire 2 hours. Data will be queued up to 
backfill anything that was missed during the outage. If you have any questions 
please ask the dataflow team.

Thanks,

Carissa Klemmer
NCEP Central Operations
IDSB Branch Chief
301-683-3835
_______________________________________________
Ncep.list.pmb-dataflow mailing list
Ncep.list.pmb-dataflow@xxxxxxxxxxxxxxxxxxxx<mailto:Ncep.list.pmb-dataflow@xxxxxxxxxxxxxxxxxxxx>
https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.pmb-dataflow


--
Anne Myckow
Dataflow Team Lead
NWS/NCEP/NCO
301-683-3825
_______________________________________________
Ncep.list.pmb-dataflow mailing list
Ncep.list.pmb-dataflow@xxxxxxxxxxxxxxxxxxxx<mailto:Ncep.list.pmb-dataflow@xxxxxxxxxxxxxxxxxxxx>
https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.pmb-dataflow


--
Dustin Sheffler
NCEP Central Operations - Dataflow
<tel:%28301%29%20683-1400>5830 University Research Court, Rm 1030
College Park, Maryland 20740
Office: (301) 683-3827<tel:%28301%29%20683-1400>
<tel:%28301%29%20683-1400>


--
Anne Myckow
Dataflow Team Lead
NWS/NCEP/NCO
301-683-3825

PNG image

PNG image

  • 2020 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the conduit archives: