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

[LDM #FPM-496740]: gempak decoders failing



Dave,

An exit status of 127 is unusual. I suspect that the pqact(1) process is able 
to successfully hand the program over to the operating system to be executed 
but that the operating system is unable to execute it for some reason.

It could be that the ld.so utility is unable to locate the necessary dynamic 
libraries. As the LDM user, what are the outputs of the commands
    ldd /home/gempak/GEMPAK7/os/linux64/bin/dctaf
    ldd /home/gempak/GEMPAK7/os/linux64/bin/dcgrib2

> I updated my LDM to 6.13.4, and my gempak to 7.3.0.  I am getting
> 'Deleting failed PIPE' errors for  my gempak decoders.  I saw a similar
> errors in the support archive number LDM #RQD-888533 but none of the
> steps in that ticket helped.  A snippet from ldmadmin tail is shown below:
> 
> 20160831T175728.386642Z pqact[28596] ERROR filel.c:425:fl_removeAndFree() 
> Deleting failed PIPE entry: pid=2561, 
> cmd="/home/gempak/GEMPAK7/os/linux64/bin/dctaf -d 
> /home/ldm/var/logs/dctaf.log -e GEMTBL=/home/gempak/NAWIPS/gempak/tables 
> /data/ldm/gempak/taf/YYYYMMDD00.taf"
> 20160831T175728.390133Z pqact[28596] ERROR filel.c:2769:reap() Child 2562 
> exited with status 127 20160831T175728.390156Z pqact[28596] ERROR 
> filel.c:425:fl_removeAndFree() Deleting failed PIPE entry: pid=2562, 
> cmd="/home/gempak/GEMPAK7/os/linux64/bin/dctaf -d 
> /home/ldm/var/logs/dctaf.log -e GEMTBL=/home/gempak/NAWIPS/gempak/tables 
> /data/ldm/gempak/taf/YYYYMMDD00.taf"
> 20160831T175728.393510Z pqact[28596] ERROR filel.c:2769:reap() Child 2563 
> exited with status 127
> 20160831T175728.393536Z pqact[28596] ERROR filel.c:425:fl_removeAndFree() 
> Deleting failed PIPE entry: pid=2563, 
> cmd="/home/gempak/GEMPAK7/os/linux64/bin/dctaf -d 
> /home/ldm/var/logs/dctaf.log -e GEMTBL=/home/gempak/NAWIPS/gempak/tables 
> /data/ldm/gempak/taf/YYYYMMDD00.taf"
> 20160831T175728.394682Z pqact[28596] ERROR pbuf.c:113:pbuf_flush() Broken pipe
> 20160831T175728.394706Z pqact[28596] ERROR pbuf.c:113:pbuf_flush() Couldn't 
> write to pipe: fd=1020, len=4096
> 20160831T175728.394720Z pqact[28596] ERROR filel.c:1670:pipe_put() Couldn't 
> write 49545-byte product to pipe
> 20160831T175728.394730Z pqact[28596] ERROR filel.c:1855:pipe_out() Couldn't 
> write product data to pipe
> 20160831T175728.394740Z pqact[28596] ERROR filel.c:1917:pipe_prodput() 
> Couldn't pipe product to decoder "/home/gempak/GEMPAK7/os/linux64/bin/dcgrib2 
> -v 1 -m 10000 -e ENSEXT=0 -d /home/ldm/var/logs/dcgrib2_CONDUITens.log -e 
> GEMTBL=/home/gempak/NAWIPS/gempak/tables 
> /data/ldm/gempak/model/ens/gefs_YYYYMMDDHH_gep08"
> 20160831T175728.394751Z pqact[28596] ERROR filel.c:1926:pipe_prodput() 
> Decoder terminated prematurely
> 20160831T175728.394768Z pqact[28596] ERROR filel.c:425:fl_removeAndFree() 
> Deleting failed PIPE entry: pid=2564, 
> cmd="/home/gempak/GEMPAK7/os/linux64/bin/dcgrib2 -v 1 -m 10000 -e ENSEXT=0 -d 
> /home/ldm/var/logs/dcgrib2_CONDUITens.log -e 
> GEMTBL=/home/gempak/NAWIPS/gempak/tables 
> /data/ldm/gempak/model/ens/gefs_YYYYMMDDHH_gep08"
> 20160831T175728.395658Z pqact[28596] ERROR filel.c:2769:reap() Child 2564 
> exited with status 127
> 20160831T175728.398049Z pqact[28596] ERROR filel.c:2769:reap() Child 2565 
> exited with status 127
> 20160831T175728.398079Z pqact[28596] ERROR filel.c:425:fl_removeAndFree() 
> Deleting failed PIPE entry: pid=2565, 
> cmd="/home/gempak/GEMPAK7/os/linux64/bin/dcgrib2 -v 1 -m 10000 -e ENSEXT=0 -d 
> /home/ldm/var/logs/dcgrib2_CONDUITens.log -e 
> GEMTBL=/home/gempak/NAWIPS/gempak/tables 
> /data/ldm/gempak/model/ens/gefs_YYYYMMDDHH_gep08"
> 20160831T175728.398174Z pqact[28596] ERROR filel.c:2769:reap() Child 2566 
> exited with status 127
> 
> I'm running on CentOS 6.8
> 
> Any ideas on how to solve this?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FPM-496740
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.