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

[LDM #DFM-474732]: New LDM entry


> 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)
> 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

Our support-email system reformats email, so I can't tell if the pqact.conf 
entries are correct. There should be a tab character before the 
"airsTotalOzone/...", the "FILE", and the "data/satellite/..." strings. Is 

Make sure that that zeros and ohs aren't confused.

The period should be escaped (i.e., "\.gz"), but that shouldn't make any 

Verify that there are no such data-products in your product-queue via the 
command "pqcat -vl- -f EXP -p AIRS >/dev/null".

> 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?

Yes, UNLESS the upstream LDM has an upstream-filter in its configuration-file 
that prevents you from receiving the AIRS data, in which case you won't receive 
the data even though a notifyme(1) will show it. You should check on this.

> 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. Can you see anything
> obvious? This should be simple and I have done it dozens of times!!

> --
> Carissa Klemmer
> NCEP Central Operations
> Production Management Branch Dataflow Team
> 301-683-3835

Steve Emmerson

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.