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

[IDD #RTY-317977]: Recent troubles with delayed 18 UTC METAR data over the IDD

Hi Daryl,

On the system in question, would you please send me the output of the following 
commands:

    regutil /server/max-latency
    pqmon -S

I would also like to see the graph titled "Age" from the command "ldmadmin 
plotmetrics".

> For the past week or so, I have been noticing a puzzling issue with ~18Z 
> METAR data (perhaps other data that I am unaware of) being delivered ~an hour 
> late or not at all.  Take for instance this product:
> 
> 20200305T191840.713081Z pqcat[17633]                pqcat.c:writeprod:80      
>           INFO        3689 20200305190516.351133 IDS|DDPLUS 27121946  SAUS80 
> KWBC 051800 RRB
> 
> So the LDM insert time is 1905z, which is an hour later than is should have 
> been.
> 
> The Oklahoma mesonet has a site with these files timestamped, and there it 
> appears to show some files received at the right time and others delayed
> 
> http://www.mesonet.org/data/public/noaa/text/archive/2020/03/05/18/SA/
> 
> see: 202003051800.KWBC_SAUS80_KWBC.925.txt
> vs: 202003051800.KWBC_SAUS80_KWBC.262.txt
> 
> Additonally, I have a fancy pants audit logger of the IDD and can find some 
> more detail.  Here's some telemetry for the product above for today:
> 
> SAUS80 KWBC 051800 RRB mistral.srcc.lsu.edu_v_iem-idd0.local entered LDM 
> queue at 1825z
> 
> SAUS80 KWBC 051800 RRB leno.unidata.ucar.edu_v_iem-idd0.local entered LDM 
> queue at 1905z
> 
> and yesterday
> 
> SAUS80 KWBC 041800 RRB leno.unidata.ucar.edu_v_iem-idd0.local entered at 1850z
> SAUS80 KWBC 041800 RRB chico.unidata.ucar.edu_v_iem-idd0.local entered at 
> 1906z
> 
> There are two products with different byte sizes with that same RRB header 
> (AUGH), anyway....
> 
> So maybe the troubles are at Unidata as the LSU one was more timely?  Shrug.  
> Any known issues afoot?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RTY-317977
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.