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

[IDD #WED-630974]: Back with another problem...

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: [IDD #WED-630974]: Back with another problem...
  • Date: Wed, 22 May 2019 15:49:37 -0600
Hi Gerry,

re:
> I just knew there was something I was forgetting...

:-)

In looking through the actions in the copy of pqact.conf that you sent,
I note that there are only 6 entries that are using the PIPE action
to send products to script; the rest of the actions are all FILE ones.

I think that the easiest way to figure out which of the PIPE actions
is causing the problems indicated in the ldmd.log file you sent is
to:

- copy the PIPE actions into a new pattern-action file

- comment the PIPE actions in the existing pattern-action file

- add a new EXEC line in your LDM configuration file, ~ldm/etc/ldmd.conf
  that executes the PIPE actions you copied to the new pattern-action
  file

- restart your LDM

  You will need to do this since you are modifying the LDM configuration
  file

After you have reduced the things to look at, and assuming that there will
still be errors generated from one or more actions in the new pattern-action
file, you can try commenting out individual and then sets of actions in
the new pattern-action file until you have narrowed down which one(s)
are causing the problems.

Comments/observations:

- it appears that you have exactly the same pattern in two actions but your
  comment lines seem to indicate that you think that they are different:

  Here are the actions that I am referring to:

###
### GOES-R/GOES-16
###
NOTHER  (TIRC..) (....) (......) (PA.)
        PIPE    -close  python /usr/local/ldm/scripts/chomp.py 
/work/LDM/GOES16/CONUS/\1_\2_\3_\4.nc

###
### GOES-17
###
NOTHER  (TIRC..) (....) (......) (PA.)
        PIPE    -close  python /usr/local/ldm/scripts/chomp.py 
/work/LDM/GOES17/CONUS/\1_\2_\3_\4.nc

As you can see, the extended regular expressions in these two actions are 
identical,
so the contents in the GOES16/... and GOES17/... directories will be identical.

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: WED-630974
Department: Support IDD
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.