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

[LDM #FPM-496740]: gempak decoders failing

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 #FPM-496740]: gempak decoders failing
  • Date: Fri, 02 Sep 2016 15:33:16 -0600
Dave,

Found the problem (I was off-base).

The GEMPAK decoders require a Python shared library:

    [ldm@twister etc]$ ldd /home/gempak/GEMPAK7/os/linux64/bin/dcgrib2
            ...
            libpython2.7.so.1.0 => /usr/local/miniconda/lib/libpython2.7.so.1.0 
(0x00007f92f1435000)
            ...

and won't work it it can't be found:

    [ldm@twister etc]$ LD_LIBRARY_PATH= ldd 
/home/gempak/GEMPAK7/os/linux64/bin/dcgrib2
            ...
            libpython2.7.so.1.0 => not found
            ...

and the pqact(1) process doesn't have LD_LIBRARY_PATH set:

    [ldm@twister etc]$ ps -p 13761 -ww e | fgrep LD_LIBRARY_PATH
    [ldm@twister etc]$ 

Probably because ldmadmin(1) is a Perl script and the perl(1) utility deletes 
that environment variable.

A solution might be to use yum(8) to install the native Python library. It 
would likely be installed in /usr/lib64 and, consequently, found by the dynamic 
loader.

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.