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

[GEMPAK #OYU-916141]: Can not get decoders to run

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: [GEMPAK #OYU-916141]: Can not get decoders to run
  • Date: Mon, 23 Mar 2015 13:00:23 -0600
Hi Fabian,

re:
> I am getting the attached errors in my ldmd.log files.

The errors indicate that the GEMPAK decoders that are referenced
via the decoders/dc... part of the LDM pattern-action file actions can
not be found.  This might indicate one or more of the following:

- the ~ldm/decoders directory does not exist OR this directory is
  not in the PATH of the user running the LDM

  If the directory does not exist, create it as the user that runs
  the LDM and then copy the GEMPAK decoders (all GEMPAK decoders
  begin with 'dc') to the directory.

  If ~ldm/decoders is not in the PATH of the user running the LDM,
  you need to add it.  This should be done to the shell-specific
  definition file (e.g., ~ldm/.bash_profile if running BASH; ~ldm/.cshrc
  if running Csh/Tcsh, etc.) and the settings need to be made active
  (e.g., log off and then log back in as 'ldm'; source the shell-definition
  file; etc.) before the LDM is started.

- the GEMPAK decoders were not copied to the ~ldm/decoders directory

  If this is the case, the LDM administrator needs to copy the GEMPAK
  decoders to the ~ldm/decoders directory

- the permissions on the GEMPAK decoders in the ~ldm/decoders directory
  do not indicate that they are executable

- you have a new LDM installation and have not adjusted the effective
  HOME directory in the ~ldm/etc/registry.xml file

  This is the most likely cause of your problems if you are a long time
  GEMPAK user that is bringing up a new LDM installation on a new machine.
  There are a number of ways to fix the problem.  I recommend the following:

  <as 'ldm'>
  edit ~ldm/etc/registry.xml and:

  change the value for the <datadir-path></datadir-path> in both the
  <pqact> and <pqsurf> blocks to be the HOME directory of the user
  running your LDM.

  For example, if HOME for 'ldm' is /home/ldm, then the setting for 
<datadir-path>
  settings will be:

  <datadir-path>/home/ldm</datadir-path>

  etc.

  Changing <datadir-path> will set the current working directory used when
  the LDM is running.  After this, relative references like 'decoders/dctaf'
  will be interpreted to mean ~ldm/decoders/dctaf and so on.

Please let us know if you run into any problems when implementing the change(s)
listed above.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: OYU-916141
Department: Support GEMPAK
Priority: Normal
Status: Closed