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

[LDM #AET-991057]: LDM 6.4.4: upstream connection closed for unknown reason

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 #AET-991057]: LDM 6.4.4: upstream connection closed for unknown reason
  • Date: Wed, 05 Apr 2006 16:41:15 -0600
Robert,

> I have had it in debug mode three times while CONDUIT was coming in.

Debug logging mode might be overkill (it certainly generates a large number of 
log messages).

> Each time the missing data in GEMPAK matched the missing data in the verbose 
> ldmd.log.

You might try running a simultaneous notifyme(1) with a tightly-constrained 
feedtype and pattern selection to see if the upstream LDM received the missing 
data-products.  This can be done after the fact (providing the products are 
still in the upstream LDM's product-queue) via the "-o offset" option.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: AET-991057
Department: Support LDM
Priority: High
Status: On Hold