[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, 25 Mar 2019 09:16:01 -0600
Gilbert,

> > You mean that the pqact(1) processes stop writing to disk even though 
> > relevant products continue to arrive?
> 
> Yes.

OK.

> >> I had to do a killllall -9 to get rid of the
> >> processes, ldmadmin stop and then remake the queue, and then restart the
> >> ldm on nfs01 to get it to work. After that, all was well on nfs01. We are
> >> running the latest version of CentOS.

> All I have in my ldmd.conf is:
> 
> exec    "/home/ldm/bin/pqact -f ANY /home/ldm/etc/pqact.conf"
> exec    "/home/ldm/bin/pqact -f ANY /home/ldm/gre/pqact.blah.conf"

Odd. Those two entries should have resulted in only two pqact(1) processes -- 
yet you indicated there were six. Looking at their process identifiers, it 
appears they were from different LDM sessions.

Can you look into this? Try grep(1)ing the LDM log files for the process 
identifiers of the pqact(1) processes.

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.