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

[LDM #WIW-895985]: pqact errors

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 #WIW-895985]: pqact errors
  • Date: Thu, 11 Apr 2019 08:14:00 -0600
Hi Dave,

> I’m seeing repeated errors of this sort in my ldm log file:
> 
> 20190411T061530.510766Z pqact[17664] ERROR filel.c:3032:reap() Child 20313 
> exited with status 1
> 20190411T061530.555128Z pqact[17664] ERROR filel.c:3032:reap() Child 20314 
> exited with status 1
> 20190411T061530.555898Z pqact[17664] ERROR filel.c:3032:reap() Child 20315 
> exited with status 1

Do the errors occur at the same time every day or are they scattered throughout 
the day?

> There isn’t any other, different information written to the log file to 
> illuminate the source of these errors, so I don’t know what product is 
> causing the problem. My pqact.conf file (and LDM configuration more 
> generally) hasn’t changed in many months, but I don’t think these errors have 
> been occurring for that long.

Because the error-message didn't have the string "EXEC" in it, I can say that 
the child processes were executed by PIPE entries.

> I’ve attached a copy of my pqact.conf file, in case it helps.

I see that the utility /usr/local/bin/STRIP is used. Does it log? If not, can 
you instrument it?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WIW-895985
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.