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

20051221: 20051221: Question about ldmd and pqact.conf syntax



Dan,

The ldmd.conf lines you had previously would have been more general
in looking for the pattern anywhere within the product, so adding it
likely wouldn't solve the problem, but should be correct.

Whenever you modify your ldmd.conf file, you must restart your ldm
so that connections to the upstream can be made with the new pattern.

Other things to check are that the ldm has write permission into your
/usr1/incoming directory

Steve CHiswell
Unidata User SUpport



>From: Daniel Leins <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200512212033.jBLKXE7s005477

>Steve,
>
>Sorry, I should have mentioned that I was also looking for tiles 33 and 
>34 in addition to 24 and 25.  But even still, that 33 should have been 
>captured and sent to the /usr1/incoming directory which didn't happen. 
>  I made the changes so that BOTH my ldmd.conf and pqact.conf files have 
>a leading "^" before the nam.t..z...etc.........I'll need to wait until 
>tomorrow to see if anything makes it way in though - the 18z nam has 
>completed already.
>
>Dan
>
>Unidata Support wrote:
>> Dan,
>> 
>> Your notifyme output does show products that begin with "nam" so the
>> "^" character is OK. However, these prodcts are tiles 32 and 33, 
>> so wouldn't match the patterns for tiles 24 and 25 that you showed previousl
> y.
>> 
>> Other than that, you also should do an
>> "ldmadmin pqactcheck" to verify your pqact.conf syntax 
>> and then make sure you have run "ldmadmin pqactHUP" to re-read the
>> pqact.conf file if you have made any changes since starting up your LDM.
>> 
>> Steve Chiswell
>> 
>> 
>> 
>> 
>>>From: Daniel Leins <address@hidden>
>>>Organization: UCAR/Unidata
>>>Keywords: 200512211958.jBLJwj7s001424
>> 
>> 
>>>Hi Steve,
>>>
>>>Thanks for lending your support.  Do you suggest I eliminate the "^" 
>> 
>>>from my pqact file, or add it into my ldmd.conf file?  I eliminated it 
>>>from my pqact file, but haven't had any luck...
>> 
>>>This is the output from my notifyme command...
>>>
>>>Dec 21 19:57:10 notifyme[14372] INFO:  1780026 20051221195703.511 
>>>FSL5 000  nam.t18z.awip21836.32
>>>Dec 21 19:57:14 notifyme[14372] INFO:  1746446 20051221195708.959 
>>>FSL5 000  nam.t18z.awip21836.33
>>>
>>>Dan
>>>
>>>Unidata Support wrote:
>>>
>>>>Dan,
>>>>Your ldmd.conf pattern matched the substring nam.t....etc... anywhere in th
> e
>>>
>>> product
>>>
>>>>name.
>>>>
>>>>Your pqact.conf entry is useing the "^" character, which in regular express
> i
>>>
>>>on
>>>
>>>>syntax means that the name must begin starting with "nam.t...etc", so your
>>>>pqact.conf pattern is not equivalent to your ldmd.conf pattern- which may b
> e
>>>
>>> your
>>>
>>>>problem. 
>>>>
>>>>If not, please send the output of your notifyme command so I can see the
>>>>file names that your pave in your queue.
>>>>
>>>>Another brief comment... since your patterns for tiles 24 and 25 are
>>>>the smae otherwise, you could use a single pattern with "2[45]".
>>>>
>>>>Steve Chiswell
>>>>Unidata User Support
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>From: Daniel Leins <address@hidden>
>>>>>Organization: UCAR/Unidata
>>>>>Keywords: 200512211927.jBLJRA7s027857
>>>>
>>>>
>>>>>To whom,
>>>>>
>>>>>Quick question about the syntax of the ldmd and pqact.conf files.  I've 
>>>>>configured the LDM software in the past, but have usually requested 
>>>>>entire feeds (*) instead of just subsets of the feed. Now, I'm 
>>>>>attempting to download a series of nam tiles with the naming convention 
>>>>>of "nam.tCCz.awip218FF.TT"  CC is the cycle, FF forecast hour, and TT 
>>>>>tile number. This is what I have in my ldmd.conf file...
>>>>>
>>>>>request FSL5    "nam\.t..z\.awip218..\.24"      ldm.server.address
>>>>>request FSL5    "nam\.t..z\.awip218..\.25"      ldm.server.address
>>>>>
>>>>>
>>>>>With the following in my pqact.conf file - I intend to just dump the 
>>>>>files into my /usr1/incoming directory...
>>>>>
>>>>>
>>>>>FSL5    ^(nam\.t..z\.awip218..\.24)
>>>>>       FILE    -overwrite      /usr1/incoming/\1
>>>>>FSL5    ^(nam\.t..z\.awip218..\.25)
>>>>>       FILE    -overwrite      /usr1/incoming/\1
>>>>>
>>>>>Does the syntax above look correct? I'm yet to see any files get dumped 
>>>>>into the /usr1/incoming directory, however while watching the feed 
>>>>>through 'notifyme' - I see that the files are available.
>>>>>
>>>>>Thanks
>>>>>Dan Leins
>>>>>
>>>>
>>>>--
>>>>***************************************************************************
> *
>>>
>>>
>>>>Unidata User Support                                    UCAR Unidata Progra
> m
>>>
>>>
>>>>(303)497-8643                                                  P.O. Box 300
> 0
>>>
>>>
>>>>address@hidden                                   Boulder, CO 8030
> 7
>>>
>>>
>>>>---------------------------------------------------------------------------
> -
>>>
>>>
>>>>Unidata WWW Service              http://my.unidata.ucar.edu/content/support
>  
>>>
>>>
>>>>---------------------------------------------------------------------------
> -
>>>
>>>
>>>>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.
>>>
>> --
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8643                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service              http://my.unidata.ucar.edu/content/support 
>> ----------------------------------------------------------------------------
>> 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.
>
--
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.