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

[IDD #KSB-345648]: LDM Glider data. (notifyme)

Hi Chuan-Yuan,

re:
> I have received some glider data by put the following lines in the pqact.conf
> 
> IDS|DDPLUS      ^SOVD83 KWNB (..)(..)
> FILE    -strip data/ldm/SOVD83/%y%m\1\2.profiles

A question and a comment:

- what is the EXEC line in your LDM configuration file, ~ldm/etc/ldmd.conf,
  that will execute actions in ~ldm/etc/pqact.conf?

- after making the addition to ~ldm/etc/pqact.conf, did you remember to
  do a gross check for errors in the newly modified file?

  We strongly recommend running:

  <as 'ldm'>
  ldmadmin pqactcheck

  After making any change to any LDM pattern action file to check for
  gross errors.

  The reason for asking this question is that it is not clear that the
  syntax of your pqact.conf entry is correct.

re:
> However, when I tried to use notifyme to check it after, I received nothing.
> Here is the command I used for the notifyme.
> 
> notifyme -vx -l bufr.log -f ANY -o 3600 -p “48984"

Are you sure that the product ID for the glider products you are interested
in contain the character sequence “48984"?  I ran the same command pointing
to the top level IDD relay that we operate, idd.unidata.ucar.edu, for the
past 10000000 seconds (which is longer than the residency time in the LDM
queue on the real server backend machines that comprise idd.unidata.ucar.edu,
and I saw nothing that matched:

notifyme -vxl- -f ANY -p 48984 -o 10000000 -h idd.unidata.ucar.edu

-- no output

re:
> I think in this case, notifyme tried to seeking WMO id is “48984” and write
> the log file into bufr.log.

Correct.

re:
> But I obtained nothing on my screen,

You wouldn't see anything on your screen as you have directed all output
from 'notifyme' to the bufr.log file.

re:
> and I can’t find the bufr.log, too.

The log file should be written to directory you were in when you ran
'notifyme'.  For instance:

~: notifyme -vxl bufr.log -f ANY -p 48984 -o 10000000 -h idd.unidata.ucar.edu
^C~
: ls bufr.log
bufr.log

~: cat bufr.log
20170823T155129.188864Z notifyme[7779] NOTE notifyme.c:385:main() Starting Up: 
idd.unidata.ucar.edu: 20170429220449.188626 TS_ENDT {{ANY, "48984"}}
20170823T155129.188905Z notifyme[7779] NOTE ldm5_clnt.c:460:forn5() LDM-5 
desired product-class: 20170429220449.188626 TS_ENDT {{ANY, "48984"}}
20170823T155129.237294Z notifyme[7779] INFO error.c:236:err_log() Resolving 
idd.unidata.ucar.edu to 128.117.140.3 took 0.048336 seconds
20170823T155129.240562Z notifyme[7779] DEBUG ldm5_clnt.c:242:forn_signon() 
NOTIFYME(idd.unidata.ucar.edu) returns OK
20170823T155129.240592Z notifyme[7779] NOTE ldm5_clnt.c:294:forn_signon() 
NOTIFYME(idd.unidata.ucar.edu): OK
20170823T155141.694208Z notifyme[7779] NOTE notifyme.c:66:cleanup() exiting

re:
> I also trying to looking for the data with WMO id : 4801920, 4801939, 
> 4801938, and
> etc., but with the same output.

Since the common part of the WMO IDs you are looking for is 48019, I tried 
looking
for these:

~: notifyme -vl- -f ANY -o 10000000 -h idd.unidata.ucar.edu -p 48019
20170823T155611.325989Z notifyme[12210] NOTE notifyme.c:385:main() Starting Up: 
idd.unidata.ucar.edu: 20170429220931.325802 TS_ENDT {{ANY, "48019"}}
20170823T155611.326021Z notifyme[12210] NOTE ldm5_clnt.c:460:forn5() LDM-5 
desired product-class: 20170429220931.325802 TS_ENDT {{ANY, "48019"}}
20170823T155611.375408Z notifyme[12210] INFO error.c:236:err_log() Resolving 
idd.unidata.ucar.edu to 128.117.140.3 took 0.049328 seconds
20170823T155611.380727Z notifyme[12210] NOTE ldm5_clnt.c:294:forn_signon() 
NOTIFYME(idd.unidata.ucar.edu): OK

There was nothing listed after letting this run for a couple of minutes.

re:
> Could you please teach me where did I make it wrong?

It could be that the LDM/IDD product ID does not contain the values you are 
searching
for, or it could be the case that the products you are looking for are not being
relayed in the IDD.  The only want to know for sure is to let the 'notifyme' 
invocation
run for a day.  Here is what I would do:

<as 'ldm'>
cd ~ldm

notifyme -vl bufr.log -f ANY - h idd.unidata.ucar.edu -o 100000 -p 48019 &

The '&' at the end of the line will background the invocation, so
you will immediately be able to verify that the file ./bufr.log 
was created.  Let this run for a day and then check the contents
of the log file.  If you don't see any matches in the log file,
after this runs for a day, then the pattern you are using in your notifyme
does not exist in any of the datastreams being relayed by idd.unidata.ucar.edu.

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: KSB-345648
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.