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

[LDM #QJQ-182312]: LDM Data Issues

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 #QJQ-182312]: LDM Data Issues
  • Date: Sat, 12 Aug 2017 10:29:37 -0600
Ryan,

The last relevant entry in the Bird01 log file is

    20170812T003038.556670Z notifyme[30512] INFO 
notifyme.c:222:notifymeprog_5()     432412 20170812003038.556225 NOTHER 
10682547  TISG16 KNES 120029 PAA

The uldbutil(1) output on Bird01 shows the following relevant subscription from 
Ldm01:

    29630 6 feeder ldm01.allisonhouse.com 20170812000901.220375 TS_ENDT 
{{NOTHER, "TIRC[0-1][0-9] KNES"}} primary

The data-product was created before the begin-time of the subscription;
consequently, it wouldn't have been sent.

Can you provide an example of the problem where the data-product was created
within the time-window of the relevant subscription?

> We continue to lose data due to random drop-outs of single "request"
> entries.
> 
> Attached are logs from ldm01 and bird01. ldm01 feeds multiple NOTHER feeds
> from bird01. ldm01 has not received "TIRC[0-9][0-9] KNES" products since
> 19:37Z, when today's issues with NOAAPORT happened. bird01 has queue
> receipts for these products as well as a corresponding "uldbutil" entry for
> ldm01 and that particular request.
> 
> Multiple restarts have been invoked against both LDMs to no avail. LDM01's
> product queue was cleared at one point as well.


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: QJQ-182312
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.