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

[LDM #WOM-274153]: Reproducible bug in LDM 6.13.10

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 #WOM-274153]: Reproducible bug in LDM 6.13.10
  • Date: Mon, 06 May 2019 10:59:58 -0600
Gilbert,

> OK, Steve, I have an issue.
> 
> I just restarted LDM's noaaport ingesters to log the way you and Tom
> suggested. Here's what I see, in part, after 5 minutes:
> 
> -rw-rw-r-- 1 ldm  ldm   828495 May  6 16:50 nother.log
> -rw-rw-r-- 1 ldm  ldm  8130209 May  6 16:50 nwstg2.log
> -rw-rw-r-- 1 ldm  ldm 10161349 May  6 16:50 nwstg.log
> -rw-rw-r-- 1 ldm  ldm  1500364 May  6 16:50 oconus.log
> -rw-rw-r-- 1 root ldm     5642 May  6 16:45 wxwire.log
> 
> 
> Holy cow, 100 MB after just 5 minutes of running? That's an awful lot. Can
> we cut that down somehow?

Are the NOAAPort ingesters logging every LDM data-product? If so, then you can 
delete the "-n" option on their EXEC entries to reduce the volume of log 
messages. You'll then need to restart the LDM.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WOM-274153
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.