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

[LDM #ORN-677013]: missing NOTHER feed

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 #ORN-677013]: missing NOTHER feed
  • Date: Thu, 08 Feb 2018 13:02:01 -0700
Dave,

Either your network or your computer can't keep up with the data.

I logged onto edex.esci and executed the following:

    [awips@edex logs]$ fgrep '[12049]' ldmd.log | head
    20180208T172750.148491Z idd.meteo.psu.edu[12049] NOTE 
ldm_config_file.c:733:requester_exec() Starting Up(6.13.6): 
idd.meteo.psu.edu:388 20180208162750.148408 TS_ENDT {{NOTHER, 
    "^TI[PRS]... KNES.*"}}
    20180208T172750.148570Z idd.meteo.psu.edu[12049] NOTE 
ldm_config_file.c:552:getPreviousProdInfo() Previous product-information file 
".fd3e80215981829af2e98521d472d7b9.info" doesn't 
    exist
    20180208T172750.293965Z idd.meteo.psu.edu[12049] NOTE 
requester6.c:588:req6_new() LDM-6 desired product-class: 20180208162750.293889 
TS_ENDT {{NOTHER, "^TI[PRS]... KNES.*"}}
    20180208T172753.460648Z idd.meteo.psu.edu[12049] NOTE 
requester6.c:311:make_request() Upstream LDM-6 on idd.meteo.psu.edu is willing 
to be a primary feeder
    20180208T174605.226294Z idd.meteo.psu.edu[12049] INFO error.c:236:err_log() 
Ignoring too-old product:    1369967 20180208164320.065316 NOTHER 219541  
TIRE02 KNES 081642 PBO
    20180208T174607.250339Z idd.meteo.psu.edu[12049] INFO error.c:236:err_log() 
Ignoring too-old product:    1318516 20180208164320.603505 NOTHER 219542  
TISI02 KNES 081642 PAB
    20180208T174608.040993Z idd.meteo.psu.edu[12049] INFO error.c:236:err_log() 
Ignoring too-old product:     410896 20180208164320.833864 NOTHER 219543  
TISI13 KNES 081642 PAA
    20180208T174608.506942Z idd.meteo.psu.edu[12049] INFO error.c:236:err_log() 
Ignoring too-old product:     291330 20180208164321.064233 NOTHER 219544  
TISI04 KNES 081642 PAA
    20180208T174608.959957Z idd.meteo.psu.edu[12049] INFO error.c:236:err_log() 
Ignoring too-old product:     314612 20180208164321.102453 NOTHER 219545  
TISI08 KNES 081642 PAA
    20180208T174610.806699Z idd.meteo.psu.edu[12049] INFO error.c:236:err_log() 
Ignoring too-old product:     981714 20180208164321.614459 NOTHER 219546  
TISI02 KNES 081642 PAD
    [awips@edex logs]$ 

This shows that, starting about 19 minutes after connecting to 
idd.meteo.psu.edu, products started arriving too late. Their latency increased 
as time went on -- leading to no products being inserted into the 
product-queue. I suspect something similar is happening with edex-test.esci 
based on its latency plot 
<http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NOTHER+edex-test.esci.millersville.edu>.

The log-file timestamps indicate that products are arriving at an approximate 
rate of one per second. This is during the "catch up" phase, when the last 
hour's worth of products are being transmitted. At that time, products should 
arrive much, much faster (10's or 100's of products per second).

Either your computer is trying to do too much (its 15 minute load-average is 
only 2, however) or the bandwidth capacity of your network is too low.

I suggest using awips-test.esci to just request the NOTHER data (don't even 
file the products: just receive them) and see if the problem persists. If it 
does, then the problem is your network.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ORN-677013
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.