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

[Support #RJC-228311]: RE: writing files in the product queue



Larry,

> Thanks, for asking, Jeff.
> 
> Still no luck.
> 
> I modified the pqact.conf file so that the ERE's of the items to be
> files were exactly the same as the ERE's of the items requested in the
> ldmd.conf file (both are attached).  I figured this would solve the
> problem if the regular expressions weren't matching anything in the
> product queue.

Please send me the relevant entry in the LDM configuration-file, etc/ldm.conf, 
that starts the pqact(1) process in question.

> It's not exactly clear to me how I would view the contents of the
> product queue,

You can list the contents of the product queue via the command "pqcat -vl-".  
The "-o", "-f", and "-p" options are also useful.  Execute the command "man 
pqcat" for more information.

> but when I type "ldmadmin watch", things stream by that
> look like the following:
> 
> Apr 08 14:46:40 pqutil INFO:     3024 20100408144623.058 CONDUIT 011
> data/nccf/com/nam/prod/nam.20100408/nam.t12z.awip3d69.tm00_icwf.grib2 !
> grib2/ncep/NMM_89/#000/201004081200F069/POPZ03/0 - NONE! 000011
> 
> When I clip out this line and test it against one of the ERE's in my
> pqact.conf file, like:
> 
> nccf/com/nam.*awip3d.*grib2
> 
> I get a match.
> 
> ?Is it possible that pqact is not being executed,

You can verify that the relevant pqact(1) process is running via the ps(1) 
utility.  Match the process identifier, PID, against the PIDs in the LDM log 
file, logs/ldmd.log.

> or that it's not
> reading from the pqact.conf file?  I'm not sure how to test for this.

If you use a "-f" option with the above-mentioned ps(1) command, then all its 
options and arguments will also be printed.  The last argument (if it exists) 
specifies the pqact(1) configuration-file.

> Any help would be appreciated.
> 
> Larry

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RJC-228311
Department: Support LDM
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.