Re: [ldm-users] [External] Re: [noaaport] NOAAport/SBN outage as of 13:30Z

  • To: "Sebenste, Gilbert" <sebensteg@xxxxxxx>, Mike Zuranski <mzuranski@xxxxxxxx>
  • Subject: Re: [ldm-users] [External] Re: [noaaport] NOAAport/SBN outage as of 13:30Z
  • From: "Herzmann, Daryl E [AGRON]" <akrherz@xxxxxxxxxxx>
  • Date: Wed, 29 Mar 2023 15:00:01 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=iastate.edu; dmarc=pass action=none header.from=iastate.edu; dkim=pass header.d=iastate.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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=t1ELDXE6RVJskC5RIzxV2xsdv43K+FN681ddoEs62cY=; b=EP4bVxmnz8e4zPexw9CJr46fPbJIQm8MpWdGpxh0rrv0CAg6ZtKyqrRNgObbgWgj3LgNyCAsBZAaxlvyxBG6HJKL2k5d5SOmGEoOPCZDxoNerbHLKZ0D+KLGYLKT8gv0OJppf2bJ1mhvz55uQieUkLEOcMgOU2clz5O+LPBW5RLf9kONG5RryVxhABo7XNcJwmxw1U1wtK+ENL1zlOiieJA7JyzSAId3+TLDQC6shD/I970cchtvpauK++muJb5StGfsZ4mbG8AvnMNEylC/t/fMaHLdDNizsPS2T7VU71f6jmy3LCXH4WSFcsn6qxBM6z6MK93uiIW1Gfd3eDLA+A==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FX7lsQiM/e2Rk4rjAYasYJTYIUDJ6Oit3I6A4RWK+nTbhyWl/4CQ6lMyB28FdAuoGGtpfk5t3E0+3omUO6HmVdaqrps0H/M9R2QbiXe+80LwMwAUymBo8hFH0Q9uUeiFPiJeoWBt3Yk1yEgOPoAqlkeXzBY1m7dB7aC3CLQy78UjIIQeryTayAOD3f7JOywKY/EPhzyvUhUTHlsE2sUJRkksqEhacLOVfRrwL1XrhtVGpp4KALwQeZLku1DhX0c9wC/hq4THUMG7QrrAJ8MO3jCioC9EBiQG7aXdGyPzfIPxKYBj/CfYmIiPYZUzDIaELpRCv4cgQsn1NXbMqVeexA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=iastate.edu;
  • Msip_labels:
Howdy Gilbert,

I'm gonna sound like a grump again, but we need to be very careful about 
putting EMWIN data onto the IDD feed.  The reason is that the EMWIN and 
NOAAPort feeds are not byte-by-byte identical, so LDM has no chance to properly 
dedup these products.

For example, the ADMSDM product was duplicated twice:

      wmo_valid_at      |                product_origin                 |  
seqnum  | size
------------------------+-----------------------------------------------+----------+------
 2023-03-29 13:54:00+00 | exo.aggregatehail.com_v_idd.agron.iastate.edu |      
999 |  742
 2023-03-29 13:54:00+00 | np2.ssec.wisc.edu_v_idd.agron.iastate.edu     | 
73462429 |  743
 2023-03-29 14:07:00+00 | exo.aggregatehail.com_v_idd.agron.iastate.edu |      
999 |  742
 2023-03-29 14:07:00+00 | leno.unidata.ucar.edu_v_idd.agron.iastate.edu | 
73472992 |  743
(4 rows)

As a reminder, the LDM MD5 checksum ignores the first 11 bytes of a product, so 
the "sequence number" at the top of the product does not matter for the MD5 
calculation.  The most common difference between the two feeds is the presence 
or absence of CR or LF at the end of the product, but this does not account for 
all of the differences.  Another difference is the "Aviation Control Character" 
that gets stripped out.

In this case, and importantly to whomever wrote the EMWIN to IDD ingest, is the 
missing space character after the sequence number:

999^M^M  <-- missing space here
NOUS42 KWNO 291407^M^M
ADMSDM^M^M

This space needs to be there for the 11 byte ignore calculation to be correct.

It would be nice that we could turn on this level of redundancy full-time, but 
we'd likely need to condition the noaaport + EMWIN ingests to rectify these 
differences so that LDM can generate identical MD5 and properly dedup the feeds.

daryl

________________________________________
From: ldm-users <ldm-users-bounces@xxxxxxxxxxxxxxxx> on behalf of Sebenste, 
Gilbert <sebensteg@xxxxxxx>
Sent: Wednesday, March 29, 2023 9:18 AM
To: Mike Zuranski
Cc: LDM; NOAAPORT
Subject: Re: [ldm-users] [External] Re: [noaaport] NOAAport/SBN outage as of 
13:30Z

AllisonHouse just turned on a kludged EMWIN feed to at least get some 
IDS|DDPLUS products going again until this outage is over with. They are 
sending it to UNIDATA, so they hope it is getting through the system.

Gilbert Sebenste
Meteorology Support Analyst

[cid:image001.png@01D9621F.5C34C250]

From: Mike Zuranski <mzuranski@xxxxxxxx>
Sent: Wednesday, March 29, 2023 8:44 AM
To: Sebenste, Gilbert <sebensteg@xxxxxxx>
Cc: LDM <ldm-users@xxxxxxxxxxxxxxxx>; NOAAPORT <noaaport@xxxxxxxxxxxxxxxx>
Subject: [External] Re: [noaaport] NOAAport/SBN outage as of 13:30Z

CAUTION: This email originated from outside of COD’s system. Do not click 
links, open attachments, or respond with sensitive information unless you 
recognize the sender and know the content is safe.

Morning Gilbert,

I'm seeing the same and am investigating.  Thanks for your report.

Best,
-Mike


Mike Zuranski
Data Engineer II
Unidata Program Center
University Corporation for Atmospheric Research


On Wed, Mar 29, 2023 at 8:43 AM Sebenste, Gilbert 
<sebensteg@xxxxxxx<mailto:sebensteg@xxxxxxx>> wrote:
Getting a strong NOAAport/SBN signal here at the College of DuPage, but outside 
of literally 6 products since 13:30Z, the feed has been dead.

This as of 13:42Z.

Gilbert

Gilbert Sebenste
Meteorology Support Analyst
[cid:image001.png@01D9621F.5C34C250]

_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


noaaport mailing list
noaaport@xxxxxxxxxxxxxxxx<mailto:noaaport@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit: 
https://www.unidata.ucar.edu/mailing_lists/

Attachment: image001.png
Description: image001.png

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