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

[LDM #JZT-172247]: Ignoring too-old product for Only CONDUIT

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 #JZT-172247]: Ignoring too-old product for Only CONDUIT
  • Date: Mon, 12 Oct 2020 09:03:44 -0600
Hi Robert,

https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+wxldm.db.erau.edu>,
it looks like some LDM that's upstream of wxldm is having problems
delivering CONDUIT data. Do you know the name of the host that's feeding
wxldm CONDUIT data?

Regards,
Steve Emmerson


> Package Version:
> Operating System: RHEL 7
> Hardware: ldm-6.13.11 and ldm-6.13.12
> Description of problem: A couple weeks ago one of our LDMs,
> gale.db.erau.edu, stopped filing CONDUIT but all other feed types are
> working.  This system's upstream LDM is wxldm.db.erau.edu.
>
> gale.db.erau.edu's logs show "WARN  Ignoring too-old product".  The
> clocks are in sync to less than a second.  I've tried connecting to
> wxldm.db.erau.edu via two different networks, one 10 Gbps, with no change
> in behavior.  The system load is pretty reasonable, though I do have some
> concerns about I/O Wait hovering around 2%.
>
> Here's a quick snapshot of the system load:
> load average: 4.61, 4.28, 3.70
> Tasks: 445 total,   1 running, 444 sleeping,   0 stopped,   0 zombie
> %Cpu(s): 13.1 us,  3.0 sy,  0.0 ni, 81.7 id,  2.0 wa,  0.0 hi,  0.2 si,
> 0.0 st
>
> Any suggestions would be greatly appreciated, I'm stumped.  Thanks!
>



Ticket Details
===================
Ticket ID: JZT-172247
Department: Support LDM
Priority: Normal
Status: Open
===================
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.