Re: [ldm-users] my data seems to be blackhole-ing

Donna:

This outputs exactly what I'd *expect* LDM to be doing, but what exactly
what it's NOT doing.


On Mon, Jul 15, 2013 at 4:57 PM, donna Cote <d-cote@xxxxxxxx> wrote:

> How about having your pqact include a
>         PIPE    echo-script.sh \2 \3
>
> where echo-script.sh simply takes two arguments and prints them to a tmp
> file. For example
>
> #!/bin/bash
> echo "filename and path will be /nasnrl1/data/radar/nexradII/**raw/ $1
> $2" > /tmp/note2me.log
>
>
>
> On 7/15/13 4:51 PM, Blair Trosper wrote:
>
>> I tried absolute paths, and the files failed to materialize then, too.
>>
>>
>> On Mon, Jul 15, 2013 at 4:46 PM, Frost, Mr. Michael
>> <Michael.Frost@xxxxxxxxxxxxxxx 
>> <mailto:Michael.Frost@nrlmry.**navy.mil<Michael.Frost@xxxxxxxxxxxxxxx>
>> >>
>>
>> wrote:
>>
>>     Do you want absolute or relative paths in your pqact entries?  I
>>     always have absolute.____
>>
>>     __ __
>>
>>     Also, does your expression pass the ‘regex’ test?____
>>
>>     __ __
>>
>>     My entry for level II is:____
>>
>>     __ __
>>
>>     ==____
>>
>>     NEXRD2
>>     ^L2-([^/]*)/(....)/([0-9][0-9]**[0-9][0-9][0-1][0-9][0-3][0-9]**
>> [0-2][0-9][0-5][0-9][0-9][0-9]**)/(.*)/(.*)/(.)/(V0[1-7])/(.)_**___
>>
>>              FILE    -close
>>     /nasnrl1/data/radar/nexradII/**raw/\2/\3.compress.raw____
>>
>>     ==____
>>
>>     __ __
>>
>>     And____
>>
>>     __ __
>>
>>     ==  For the E guy..____
>>
>>     NEXRD2
>>     ^L2-([^/]*)/(....)/([0-9][0-9]**[0-9][0-9][0-1][0-9][0-3][0-9]**
>> [0-2][0-9][0-5][0-9][0-9][0-9]**)/(.*)/(.*)/E/(V0[1-7])/(.)___**_
>>
>>             EXEC    /h/ldm/decoders/**processLevelII.ksh
>>     /nasnrl1/data/radar/nexradII/**raw/\2/ \2 \3____
>>
>>     ==____
>>
>>     __ __
>>
>>     Mike____
>>
>>     __ __
>>
>>
>>     Michael Frost
>>     Naval Research Laboratory
>>     Marine Meteorology Division
>>     7 Grace Hopper Avenue, Stop #2
>>     Monterey, CA 93940
>>     Phone: 831-656-4723 <tel:831-656-4723>
>>     Fax: 831-656-4017 <tel:831-656-4017>
>>     Email: mike.frost@xxxxxxxxxxxxxxx
>>     <mailto:mike.frost@nrlmry.**navy.mil <mike.frost@xxxxxxxxxxxxxxx>
>> >____
>>
>>     
>> *From:*ldm-users-bounces@**unidata.ucar.edu<ldm-users-bounces@xxxxxxxxxxxxxxxx>
>>     
>> <mailto:ldm-users-bounces@**unidata.ucar.edu<ldm-users-bounces@xxxxxxxxxxxxxxxx>
>> >
>>     
>> [mailto:ldm-users-bounces@**unidata.ucar.edu<ldm-users-bounces@xxxxxxxxxxxxxxxx>
>>     
>> <mailto:ldm-users-bounces@**unidata.ucar.edu<ldm-users-bounces@xxxxxxxxxxxxxxxx>>]
>> *On Behalf Of *Karen
>>     Cooper - NOAA Affiliate
>>     *Sent:* Monday, July 15, 2013 2:42 PM
>>     *To:* Blair Trosper
>>     *Cc:* LDM Users
>>     *Subject:* Re: [ldm-users] my data seems to be blackhole-ing____
>>
>>     __ __
>>
>>
>>     And of course what I really meant was the exec line in your
>> ldmd.conf...
>>
>>     exec    "pqact "____
>>
>>     __ __
>>
>>
>>     On Mon, Jul 15, 2013 at 4:40 PM, Karen Cooper - NOAA Affiliate
>>     <karen.cooper@xxxxxxxx <mailto:karen.cooper@xxxxxxxx>**> wrote:____
>>
>>     Blair,____
>>
>>
>>     First a sanity check. -- Are you sure that pqact is uncommented in
>>     your ldmadmin.pl <http://ldmadmin.pl>? ____
>>
>>
>>     You can set pqact to verbose mode and then you should see what it's
>>     trying to do, as it will log to your ldmd.log files.  I often use
>>     this when I'm testing out new pqact entries that aren't working as I
>>     expect. ____
>>
>>     __ __
>>
>>
>>     On Mon, Jul 15, 2013 at 4:35 PM, Blair Trosper
>>     <blair.trosper@**updraftnetworks.com<blair.trosper@xxxxxxxxxxxxxxxxxxx>
>>     
>> <mailto:blair.trosper@**updraftnetworks.com<blair.trosper@xxxxxxxxxxxxxxxxxxx>>>
>> wrote:____
>>
>>
>>         I'm receiving several feeds as proven by ldmadmin watch...and
>>         the logs all look fine.  However, my data isn't being saved to
>>         disk.____
>>
>>         __ __
>>
>>          From *registry.xml*:____
>>
>>
>>                <pqact>
>>                  <config-path>/mnt/data/ldm/**
>> etc/pqact.conf</config-path>
>>                  <datadir-path>/mnt/data/ldm/**var/data</datadir-path>
>>                </pqact>____
>>
>>         __ __
>>
>>          From */mnt/data/ldm/etc/pqact.conf***:____
>>
>>
>>             # L2 data
>>             NEXRAD2
>>             ^L2-BZIP2/(....)/([0-9]{8})([**0-9]{4})[0-9]{2}/([0-9]{1,4}) .
>> ***/[SI]
>>                      FILE    nexrad2/\1/\1_\2-\3.part
>>             NEXRAD2
>>             ^L2-BZIP2/(....)/([0-9]{8})([**0-9]{4})[0-9]{2}/([0-9]{1,4}) .
>> ***/E
>>                      FILE    -close nexrad2/\1/\1_\2-\3.part
>>             (snip)____
>>
>>         __ __
>>
>>
>>         However, following those two things, here's a directory listing
>>         of */mnt/data/ldm/var/data*:____
>>
>>
>>             ldm@chicago-il-1:~/data$ ls -lsha
>>             total 8.0K
>>             4.0K drwxr-xr-x 2 ldm ldm 4.0K Jul 15 16:09 .
>>             4.0K drwxr-xr-x 5 ldm ldm 4.0K Jul 13 23:19 ..____
>>
>>         __ __
>>
>>
>>         Nothing.  The same is true of other feeds which should be
>>         stashed in other subdirectories.____
>>
>>         __ __
>>
>>
>>         The bandwidth is certainly registering, which I have verified at
>>         the router, so I'm definitely receiving the data...so...____
>>
>>         __ __
>>
>>         Where are my files going?  Any way to track this down?____
>>
>>         __ __
>>
>>
>>         (I've also done "du -ksh" from the home directory of the ldm
>>         user over the last few hours, and it's not increasing.
>>           Definitely nothing being written to hard disk.  And still no
>>         errors in the LDM or system logs.)____
>>
>>         __ __
>>
>>         -- ____
>>
>>         Blair Trosper____
>>
>>         Weather Data / Updraft Networks____
>>
>>         
>> blair.trosper@updraftnetworks.**com<blair.trosper@xxxxxxxxxxxxxxxxxxx>
>>         <mailto:blair.trosper@updraft.**us <blair.trosper@xxxxxxxxxx>
>> >____
>>
>>         NOC: 512-666-0536 <tel:512-666-0536>____
>>
>>         __ __
>>
>>         ______________________________**_________________
>>         ldm-users mailing list
>>         ldm-users@xxxxxxxxxxxxxxxx 
>> <mailto:ldm-users@unidata.**ucar.edu<ldm-users@xxxxxxxxxxxxxxxx>
>> >
>>
>>         For list information or to unsubscribe,  visit:
>>         
>> http://www.unidata.ucar.edu/**mailing_lists/<http://www.unidata.ucar.edu/mailing_lists/>____
>>
>>
>>
>>
>>
>>     --
>>     “Climate is what you expect, weather is what you get."
>>       -- Robert A. Heinlein
>>
>>     ------------------------------**-------------
>>     Karen.Cooper@xxxxxxxx <mailto:Karen.Cooper@xxxxxxxx>
>>
>>     Phone: 405-325-6982 <tel:405-325-6982>
>>     Cell: 405-834-8559 <tel:405-834-8559>
>>     INDUS Corporation
>>     National Severe Storms Laboratory____
>>
>>
>>
>>
>>
>>     --
>>     “Climate is what you expect, weather is what you get."
>>       -- Robert A. Heinlein
>>
>>     ------------------------------**-------------
>>     Karen.Cooper@xxxxxxxx <mailto:Karen.Cooper@xxxxxxxx>
>>
>>     Phone: 405-325-6982 <tel:405-325-6982>
>>     Cell: 405-834-8559 <tel:405-834-8559>
>>     INDUS Corporation
>>     National Severe Storms Laboratory____
>>
>>
>>
>>
>>
>> --
>> Blair Trosper
>> Weather Data / Updraft Networks
>> blair.trosper@updraftnetworks.**com 
>> <blair.trosper@xxxxxxxxxxxxxxxxxxx><mailto:
>> blair.trosper@updraft.**us <blair.trosper@xxxxxxxxxx>>
>>
>> NOC: 512-666-0536
>>
>>
>> ______________________________**_________________
>> ldm-users mailing list
>> ldm-users@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe,  visit:
>> http://www.unidata.ucar.edu/**mailing_lists/<http://www.unidata.ucar.edu/mailing_lists/>
>>
>>
> ______________________________**_________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
> http://www.unidata.ucar.edu/**mailing_lists/<http://www.unidata.ucar.edu/mailing_lists/>
>



-- 
Blair Trosper
Weather Data / Updraft Networks
blair.trosper@xxxxxxxxxxxxxxxxxxx <blair.trosper@xxxxxxxxxx>
NOC:  512-666-0536
  • 2013 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: