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

[LDM #JHM-887622]: LDM product queue got corrupted, again...

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: [LDM #JHM-887622]: LDM product queue got corrupted, again...
  • Date: Fri, 04 Feb 2022 09:28:24 -0700
Hi Ryan,

> The information you were looking for: The products were not hitting the
> queue in the NEXRAD3 feedtype. Not hitting the queue obviously also means
> not hitting the disk, so confirmation that they're just not making it.
> NEXRAD3 was impacted this time but NEXRAD2 remained up and stable.

Ok. That sounds like the problem might lie with the program that ingests from 
the NOAAPort broadcast, noaaportIngester(1).

Is there anything relevant in the LDM log file (or any other log file) for when 
this happened?

> Also not mentioned was that I restarted a downstream LDM unrelated to those
> feedtypes (no "request") and then this happened. This is maybe the second
> or third time I've done a downstream LDM restart that has impacted our
> upstream LDM in this way.

Please elucidate. Was the downstream LDM started on the same host as the 
upstream LDM? What do you mean, exactly, by "no request"? What is the topology 
of the LDM network (i.e., who's requesting what from whom)?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JHM-887622
Department: Support LDM
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.