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

[LDM #GNJ-752174]: Need advice on hupping persistent daemons (pqinsert, pqing)

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 #GNJ-752174]: Need advice on hupping persistent daemons (pqinsert, pqing)
  • Date: Mon, 17 Sep 2018 13:53:56 -0600
Anne,

If all of the following are true:

1. You're running LDM version 6.13.6.
2. You're using pqing(1) to create LDM data-products and insert them into the 
LDM product-queue.
3. The pqing(1) process is *not* running within the LDM process group.
4. You periodically execute the command "ldmadmin newlog" to rotate the LDM log 
file.

then, in order to get the pqing(1) process to switch to a new log file, the 
script or chrontab(1) entry that's executing the "ldmadmin newlog" command 
should also send a USR1 (not HUP) signal to the pqing(1) process.

> So sorry, I was mixed up with our info.
> 
> We are running into this issue now that we have upgraded to 6.13.6 - 6.11
> wasn't doing this to us. I'm attaching the code that we use to make calls
> to pqing - here is how it is called within our code:
> 
> /ioddev/dbndev/ldm/bin/pqing -fHDS  /ioddev/dbndev/ldm_que_HDS
> 
> Can you take a look and let us know if you see anything we could improve?

Befire I do that, would you please see if sending a SIGUSR1 to the pqing(1) 
process solves the problem.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GNJ-752174
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.