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

[LDM #EPA-318197]: pqact PIPE problem



Bob,

First off, the PIPE entry in your email doesn't have a pattern (i.e.,
extended regular expression) field. Does the entry in the pqact(1)
configuration-file have one?

Second, can you be certain that the data-product piped to your decoder was
in the expected format? Is it possible that the entry piped a data-product
that you weren't expecting?

Third, pqact(1) decoders are daemon processes; consequently, they're
responsible for doing their own logging (writing to the standard output or
standard error stream won't work). Can you modify the Python script to log
the reason why it exited with status 1?

If you're confident about the first two issues, then I recommend immediately
working on the third.

Good luck and, please, keep us apprised.

> I'm having a problem using the PIPE action in pqact.conf.  This is the first 
> time I've tried using it, so I feel like I'm just missing something basic.
> 
> I have a small python program that reads lines of comma-separated values from 
> stdin, and writes those values to a database.
> 
> This works:
> more tafs.csv | /usr/local/ldm/util/tafdb.py
> 
> But this doesn't:
> EXP
> <tab>PIPE<tab>-close /usr/local/ldm/util/tafdb.py
> 
> LDM logs the following error:
> 20170825T141609.531562Z pqact[17583] ERROR filel.c:3032:reap() Child 17837 
> exited with status 1
> 20170825T141609.531634Z pqact[17583] ERROR filel.c:425:fl_removeAndFree() 
> Deleting failed PIPE entry: pid=17837, cmd="/usr/local/ldm/util/tafdb.py"
> 
> The program produces no log output and doesn't even create an empty log file. 
>  The program's owner:group are ldm:ldm, and permissions are set to 755.
> 
> Attached is my python code.  Any and all suggestions are welcome!

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EPA-318197
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.



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.