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

[LDM #MZG-649767]: LDM errors



Ajayram,

> Please help me to resolve the below errors.
> 
> Sep 17 14:31:13 ramxtxls1153 pqact[38607] ERROR: [filel.c:305] Deleting 
> failed PIPE entry: pid=9216, cmd="decoders/dcgrib2 -d 
> data/gempak/logs/dcgrib2_NAM242.log -e 
> GEMTBL=/local/tools/gempak/GEMPAK7/gempak/tables"
> Sep 17 14:31:13 ramxtxls1153 pqact[38607] ERROR: child 9214 exited with 
> status 1
> Sep 17 14:31:13 ramxtxls1153 pqact[38607] ERROR: child 9216 exited with 
> status 1
> Sep 17 14:31:13 ramxtxls1153 pqact[9219] ERROR: No such file or directory
> Sep 17 14:31:13 ramxtxls1153 pqact[9219] ERROR: [filel.c:1423] Couldn't 
> execute decoder "decoders/dcgrib2"
> Sep 17 14:31:13 ramxtxls1153 pqact[9219] NOTE: Exiting
> Sep 17 14:31:13 ramxtxls1153 pqact[38607] ERROR: child 9219 exited with 
> status 1 (PIPE decoders/dcgrib2 -d data/gempak/logs/dcgrib2_NAM242.log -e 
> GEMTBL=/local/tools/gempak/GEMPAK7/gempak/tables)
> Sep 17 14:31:13 ramxtxls1153 pqact[38607] ERROR: [filel.c:305] Deleting 
> failed PIPE entry: pid=9219, cmd="decoders/dcgrib2 -d 
> data/gempak/logs/dcgrib2_NAM242.log -e 
> GEMTBL=/local/tools/gempak/GEMPAK7/gempak/tables"

You appear to be using the GEMPAK decoders. The pqact(1) configuration-files 
that come with the GEMPAK decoders assume that the current working directory of 
the pqact(1) processes has a "decoders/" subdirectory. This assumption is not 
necessarily true. The pqact(1) program sets its current working directory to 
the value of the "/pqact/datadir-path" parameter of the LDM registry (you can 
check this value with the command "regutil /pqact/datadir-path"). If the LDM 
user's home directory has a "decoders" subdirectory, then you could set this 
parameter to the home directory with the command "regutil -s $HOME 
/pqact/datadir-path" to get things working. Alternatively, you could remove the 
"decoders/" prefix in all the GEMPAK pqact(1) configuration-files and ensure 
that the directory that contains the GEMPAK decoders is in the PATH environment 
variable. In either case, you will have to restart your LDM.

> Thank you
> Ajayram Gopu

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: MZG-649767
Department: Support LDM
Priority: Normal
Status: Closed