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

[LDM #UOW-671313]: LDM6.13.6 product not be written to ldmd.log

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 #UOW-671313]: LDM6.13.6 product not be written to ldmd.log
  • Date: Thu, 02 Nov 2017 09:07:41 -0600
Simon,

> Setting option -v  to ldmadmin start, is work

Good!

> When i use command "ldmsend" to localhost, i can find the product info
> in ldmd.log

This is expected behavior.

> But i use command  "pqinsert" to localhost, the product info not be
> written to ldmd.log

This is also expected behavior. ldmsend(1) transmits the data-product to the 
ldmd(1) process; consequently, the ldmd(1) process logs the data-product's 
arrival. pqinsert(1), however, inserts the data-product directly into the LDM 
product-queue -- bypassing the ldmd(1) process; consequently, no message is 
logged. You can use the options "-v" and "-l" of pqinsert(1) to have that 
process log a message.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UOW-671313
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.