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

[LDM #HMA-788722]: LDM problem

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 #HMA-788722]: LDM problem
  • Date: Sun, 23 Dec 2007 10:37:39 -0700
John,

I found your downstream LDM that's receiving NEXRAD2 via the
command "fgrep NEXRAD2 `ls -rt ldmd.log*`".  Putting that
downstream LDM into verbose logging mode resulting in the
following:

$ fgrep '[4402]' `ls -rt ldmd.log*`
...
ldmd.log:Dec 23 17:09:01 adiabat idd.unidata.ucar.edu[4402] INFO: Ignoring 
too-old product:     3777 20071223160856.993 NEXRAD2 692010  
L2-BZIP2/KRAX/20071223160812/692/10 
ldmd.log:Dec 23 17:09:01 adiabat idd.unidata.ucar.edu[4402] INFO: Ignoring 
too-old product:     5718 20071223160857.199 NEXRAD2 550004  
L2-BZIP2/KDVN/20071223160758/550/4 
...

The arriving data-products are over one hour old, so the 
downstream LDM is ignoring them.  This is consistent with
the "rtstats" plot of the NEXRAD2 latencies for you system
(they grow until they disappear) and also with log messages
on our end about sending old data.

I suspect, therefore, that the mean bandwidth between 
idd.unidata.ucar.edu and adiabat.rwic.und.edu is insufficient
for the amount of data requested.  Can you reduce the amount
of requested data?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HMA-788722
Department: Support LDM
Priority: Normal
Status: On Hold