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

[LDM #DFM-474732]: New LDM entry

Hi Carissa,

> I setup a new dataflow from NASA but only one of the entries is working and
> I just can't figure it out. The sport data is successfully coming in, the
> AIRS isn't.
> The ldmd.conf:
> # NASA SPoRT server (primary and backup)
> request EXP "(sport|AIRS)"
> The pqact.conf:
> # NASA-SPoRT (POC Rita Edwards)
> EXP 
> airsTotalOzone/(AIRSO3_[0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9]_[0-2][0-9][0-5][0-9].gz)
> FILE    data/satellite/POLAR_ORBITERS/AIRSO3/\1
> EXP     (AIRSO3_........_....\.gz)
> PIPE    -close  /usr1/ldm/bin/w2gunzip.sh
> data/satellite/POLAR_ORBITERS/AIRSO3/\1
> Using a notifyme I can see the data I am looking for:
> address@hidden: notifyme -v -l - -h
> Jan 31 01:58:40 notifyme[9789] NOTE: Starting Up: 
> 20130131015840.391 TS_ENDT {{ANY,  ".*"}}
> Jan 31 01:58:40 notifyme[9789] NOTE: LDM-5 desired product-class: 
> 20130131015840.391 TS_ENDT {{ANY,  ".*"}}
> Jan 31 01:58:40 notifyme[9789] NOTE: NOTIFYME( reclass: 
> 20130131015840.391 TS_ENDT {{EXP,  ".*"}}
> Jan 31 01:58:40 notifyme[9789] NOTE: NOTIFYME( OK
> Jan 31 01:59:11 notifyme[9789] INFO:    19370 20130131015902.625     EXP 000  
> /usr/people/ldm/data/airs/airsTotalOzone/AIRSO3_20130130_2200.gz


> Does the notifyme ensure that the LDM on NASA's side is setup correctly?

The 'notifyme' invocation demonstrates that the LDM on the NASA side
has an ALLOW for any product in the EXP datastream.  Since you are
requesting specific products from EXP alone, then yes, the 'notifyme'
invocation demonstrates that the NASA side is setup correctly for
what you are trying to do.

> We are not seeing anything being written to the ldmd.log file. Not even an
> error. That leads us to think that the ldmd.conf is wrong, but we have
> modified it for several different tests to no avail.

The most common errors experienced by users are when the ldmd.conf file
is configured correctly, and the products are being received, but the
pattern-action file action is not matching the products being received.

> Can you see anything
> obvious? This should be simple and I have done it dozens of times!!

In a situation like this, we recommend that you do the following
additional steps in your troubleshooting:

- verify that the products are, in fact, being received by your LDM

  This is accomplished in either of two ways:

<as 'ldm'>
notifyme -vl-


<as 'ldm'>
ldmadmin watch

- if you are receiving the products you are expecting to receive,
  use 'notifyme' to verify the extended regular expression being
  used in the pattern-action file action.  For example:

notifyme -vl- -p 

notifyme -vl- -p "AIRSO3_........_....\.gz"

NB: there may be characters you have to escape in your extended regular
expression so that they won't being interpreted by the shell you are
running your 'notifyme' invocation from.  Example:

notifyme -vl- -p 

Once you get the hang of how to specify the extended regular expression
in a 'notifyme' invocation from the command line, you can vary the expression
to match on what you want.  You would then use that expression (without escapes)
in your pattern action file.

NB: After making a change to an action in a pattern action file, you
should verify the editing changes and then inform the LDM to reread
the file patterns:

<as 'ldm'>
-- edit the pattern action file(s)
ldmadmin pqactcheck
-- if you do not get warnings/errors then
ldmadmin pqactHUP


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: DFM-474732
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.