[LDM #DFM-474732]: New LDM entry

Hi Carissa,

re:
> Okay. The product comes in once an hour...annoying to troubleshoot.

Yes, this would be annoying indeed.

re:
> But this is what I just had:
> 
> 1. Changed the ldmd.conf to:
> 
> request EXP ".*" 198.122.199.134
> 
> 2. notifyme -v -l - -h 198.122.199.134 showed the product in question did
> show
> 
> Jan 31 16:59:23 notifyme[25972] INFO:    24977 20130131165902.450     EXP
> 000  /usr/people/ldm/data/airs/airsTotalOzone/AIRSO3_20130131_1300.gz

OK, good.

re:
> 3. The notifyme -vl- -p "AIRSO3_" had nothing at all

So, the pattern is not matching.  My first guess is that the 'O' (oh) in
the pattern is a '0' (zero) (or the exact opposite).

re:
> 4. The notifyme -vl- had nothing with that name come through at that time:
> 
> Jan 31 16:59:17 notifyme[15478] INFO:  1959842 20130131165926.329 NEXRAD3 000 
>  wsr88d16592.tbz2
> Jan 31 16:59:27 notifyme[15478] INFO:  2002589 20130131165935.991 NEXRAD3 000 
>  wsr88d16593.tbz2
> Jan 31 16:59:37 notifyme[15478] INFO:  1459153 20130131165945.790 NEXRAD3 000 
>  wsr88d16594.tbz2
> Jan 31 16:59:47 notifyme[15478] INFO:  1559753 20130131165956.253 NEXRAD3 000 
>  wsr88d16595.tbz2

Hmm...

re:
> Does the notifyme -vl- ignore the pqact.conf?

Yes.  'notifyme' invocations have _nothing_ to do with actions in
actions in pattern-action files.

re:
> I confirmed with
> a pqactcheck that the tabs are in place correctly. I have a tab after EXP,
> after the expression and after FILE

OK, but there still is a mismatch in the extended regular expression in
the pattern-action file and the product ID.

re:
> There is no "null" in the pqact.conf that is grabbing this data first.
> There is no other EXP with "air" in the name.

OK.

re:
> So am I concluding that the LDM is not recognizing this product?

This is doubtful (actually, it is unheard of).  The key must be that
there is a character in the product ID that is not matching the
extended regular expression pattern, OR, as Steve pointed out, the
upstream my have restricted which EXP products you are allowed to
REQUEST.  'notifyme' invocations will show everything that the
upstream has in the datastream ALLOWed regardless of their ALLOW
restrictions by pattern.

re:
> Should I loosen up the regular expression for the AIRS in the pqact?

I would create a new pattern-action file action that simply writes
all of the products to disk.  That way you can easily see that they did
arrive and what their product IDs were.  Here is an example:

EXP<tab>(.*)
<tab>FILE
<tab>data/NASA\1

Again, after editing a pattern-action file, check the edits and
then send a pqactHUP as before.

Comments:

- I have been in the same situation as you are now, and have thought
  that there must be something wrong with the LDM because I felt
  certain that my action(s) were correct.  In every case, I found
  that I had some, typically small problem in my action that was
  telling 'pqact' to do something that I did not want.

- you can see what products you received and are still in your
  LDM queue using the LDM 'pqcat' utility.  Here is an example:

<as 'ldm'>
pqcat -vl- -f EXP -o 3600 > /dev/null

This will list out the product IDs for all EXP products received
in the past 3600 seconds.  The redirection to /dev/null is needed
since 'pqcat' will write the product out to STDOUT and you don't
want that.

re:
> So nice to have you both on the case!

That's what we are here for :-).  However, I will be unavailable
for the rest of the day today.  I will check things later this
evening, however.

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: DFM-474732
Department: Support IDD
Priority: Normal
Status: Open