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

Re: 19990210: DIFAX not processing

On Wed, 10 Feb 1999, Mark Tucker wrote:

> On Wed, 10 Feb 1999, Robb Kambic wrote:
> 
> > 
> > > many duplicate entries that we've had.  The old pqact.conf file handles 
> > > the incoming DIFAX correctly; the new one does not.  There are only two 
> > > entries that deal with DIFAX (listed below).
> > > 
> > > # DIFAX feed from Alden
> > > DIFAX   ^(....).*       FILE    -overwrite      -close

DIFAX   ^(....).*
        FILE    -overwrite      -close

> > > /usr/local/ldm/data/apollo/rawdifax/\1.g3
> > > #DIFAX  ^(....).*       EXEC    /usr/local/ldm/scripts/remote.difax \1
> > > DIFAX   ^(....).*       EXEC    /usr/local/ldm/scripts/process.difax \1

DIFAX   ^(....).*
        EXEC    /usr/local/ldm/scripts/process.difax \1

> > 
> > As use ldm, run your new script from ldm home. ie
> > 
> > % cd ~
> > % /usr/local/ldm/scripts/process.difax <difaxName>
> > 
> > This will probably show the problem. 
> > 
> Robb,
> 
> The script "process.difax" works correctly when the difax products are
> being processed. With the updated pqact.conf the previous entry that
> outputs the rawdifax to a file was not writing either.

Mark,

This is strange, so it makes me believe that something is wrong with the
pqact.conf file.  I will modify  the above entries, use these as a
template for you mods. It could be an extra space at the end of a line or
something small causing the problem. This type of error would not show up
in the ldmadmin pqactcheck because it's not a syntax error.

Robb...


  In looking things
> over from this weekend I found that there were several products that were
> not being processed although they were coming in (I could see them using
> the "ldmadmin watch" command).   
> 
> > > I believe that the duplicate entries may have been creating some minor
> > > problems so I don't want to restore the old version if at all possible.
> > > For reference, I've kept the last pqact.conf to work with the DIFAX as
> > > "pqact.conf.keep" in the same directory.  I know I'm missing something
> > > here but I'm at a loss at to what it might be. I couldn't find anything
> > > in the archives that mention a similar problem.
> 
> Because we were missing so much data over this past weekend I had to
> restore the original pqact.conf from pqact.conf.keep (we were missing
> products that still had a pqact.conf entry). I kept a copy of
> the cleaned up version as pqact.conf.new.  I still need to get this
> corrected at some point.  
> 
> Thanks. 
> 
> Mark Tucker
> Information Technology
> Lyndon State College
> address@hidden
> 
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================