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

[LDM #XXT-101239]: gempak decoders not working with LDM



Hi Chris,

re:
> I have been monitoring our new LDM on the blizzard machine and we have not
> been getting data products produced by any GEMPAK programs.  The ldmd.log
> file has a lot of entries like this:
> 
> Aug 31 00:00:03 blizzard pqact[27388] ERROR: No such file or directory
> Aug 31 00:00:03 blizzard pqact[27388] ERROR: Couldn't execute decoder
> "decoders/dcgrib2" [filel.c:1425]
> Aug 31 00:00:03 blizzard pqact[27388] NOTE: Exiting
> Aug 31 00:00:03 blizzard pqact[26225] ERROR: pbuf_flush(): fd=882,
> cmd=(decoders/dcgrib2 -d data/gempak/logs/dcgrib2_AWC_TURB.log -e
> GEMTBL=/home/gempak/NAWIPS/gempak/tables
> data/gempak/model/awc/YYYYMMDD_turb.gem): Broken pipe
> Aug 31 00:00:03 blizzard pqact[26225] ERROR: pipe_put(): write error:
> pid=27388, cmd=(decoders/dcgrib2 -d data/gempak/logs/dcgrib2_AWC_TURB.log
> -e GEMTBL=/home/gempak/NAWIPS/gempak/tables
> data/gempak/model/awc/YYYYMMDD_turb.gem)
> 
> I have attached the pqact.conf file from blizzard.  Ideas?

I believe that this has to do with a setting in ~ldm/etc/registry.xml
that makes the current working directory for routines run as part
of the LDM suite in ~ldm/var/data.  Previous versions of the LDM
would make the current working directory ~ldm.  In the previous
incantation, a reference to a decoder like indicated by the log
messages above (e.g., decoders/dcgrib2) would work fine.  In
the new LDM with the default configuration in registry.xml
these references do not work.

There are two options for a "solution":

- change all GEMPAK pattern-action file actions from decoders/...
  to ... and util/... to ... (where ... is the name of a decoder)

- OR, edit ~ldm/etc/registry.xml and set the current working
  directory to ~ldm (e.g., /home/ldm) instead of ~ldm/var/data

I just tried logging onto blizzard, but I was unsuccessful because
the temporary password we used before is no longer valid.  If
you change the password back to what it was or provide us with
the new one, we could login and make appropriate changes.

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: XXT-101239
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.