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

Re: 20010220: pqact not working

Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >To: Unidata Support <address@hidden>
> >From: Wil Wollheim <address@hidden>
> >Subject: pqact not working
> >Organization: UCAR/Unidata
> >Keywords: 200102201538.f1KFcpL25433
> 
> Hi,  We have just gotten a Nexrad feed up and running and are recieving
> one data product (NTP) for three radar sites.  The problem we are having
> is that pqact is not transferring the files from the queue to their
> designated directories.  (the files are acumulating in the queue!)
> 
> The pqact line we have put in is as follows:
> 
> NNEXRAD ^SDUS5. (KBOX|KCAR|KGYX) (..)(....) /p(NTP)(BOX|CBW|GYX)
>         FILE    data/images/rad/\5/\4\5\2.(\2:dd)(\2:mmm)(\2:yy)
> 
> I run ldmadmin pqactcheck and the file is syntactically correct.
> 
> I check ldmadmin log and it succesfully reads the pattern file
> (pqact.conf)
> 
> If I run pqact -v -x from the command line it says segmentation
> violation(core dumped)
> 
> Can you tell me what I am doing wrong?
> 
> Thank you!
> 
> Wil Wollheim
> 
> Water Systems Analysis Group
> Complex Systems Research Center
> Morse Hall
> University of New Hampshire
> Durham NH 03824
> Voice: (603) 862-0812
> FAX: (603) 862-0587
> E-mail: address@hidden
> 
> ------- End of Forwarded Message

Hi Wil,

First, ldmadmin pqactcheck does not find all the possible problems in a
pqact.conf file.  It's useful mostly as a first pass debugging tool.

Your NEXRAD entry looks fine to me.  But, the fact that pqact dumps core
indicates to me that one of those yucky, invisible errors has been
introduced into pqact.conf.  pqact.conf requires that fields in a
pqact.conf entry be separated by tabs.  If an entry is continued over
two lines (as yours appears to be), then the first character on the
second line should be a tab.  I can't judge whether this is true from
what you sent me, as mailers often munge messages to 'improve' their
format.

Perhaps if you ran 'pqact -v -l -' or 'pqact -x -l -' it will show you
where the problem is.  (From your 'pqact -v -x' command, above, pqact
would write to the log file - did anything appear there?)

Sometimes with pqact it's necessary to do a painful, brute force
approach where you delete suspicious lines from the file, then add them
back in one at a time to pinpoint the problem.  Sad, but true.

Please let me know what you find out.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************