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

[CONDUIT #CYE-443810]: Re: GFS and GRIB1 in CONDUIT?

Christian,

I ran a notifyme command to kepler.sca.uqam.ca and you certainly have the
.status files in your queue on that machine. I also witnessed the gefs data 
arriving on your machine. There are then two possibilities why the FILE action 
you have below is not producing the file output to disk since the regex does 
match the products currently in your queue:

1) You have a typo in your pqact.conf file that is preventing pqact from
reading past a certain point in your file. That would be evidenced if you
had other lines following this FILE action that were also failing.

Check your pqact.conf using the "ldmadmin pqactcheck -p pqact_conf"
as well since it might show any errors, though you should also look for
any blank lines that are not commented out in your conf file.

Also, double check the FILE line to ensure it begins with a <TAB> character, and
has <TAB>s before -close and the output file name.


2) Ensure that you have run "ldmadmin pqactHUP" or restarted your LDM since the 
last
time you modified your conf file.


Steve Chiswell
Unidata User Support


> Steve,
> 
> I have run more tests, I and I am even more puzzled.
> Using this command, which uses the same regex as my ldmd.conf line (I
> copied it from my ldmd.conf):
> notifyme -vxl - -f CONDUIT -o 10000 -h idd.cise-nsf.gov -p
> "(status|prod/gfs.*PRMSL|prod/gfs.*HGT/500|prod/gfs.*HGT/1000|prod/gfs.*APCP|prod/gfs.*RH/2.m|prod/gfs.*TMP/2.m|prod/gfs.*TCDC/atmos_col|prod/gfs.*HGT/0C|prod/gfs.*UGRD/10_m_above_gnd|prod/gfs.*VGRD/10_m_above_gnd|prod/gefs.*TMPK/850)"
> 
> I do get all the products in INFO output. But I dont get any GRIB1
> status messages even with this pqact.conf action:
> #
> # CONDUIT STATUS
> #
> CONDUIT         ^.status\.(.*) [0-9][0-9][0-9][0-9][0-9][0-9]
> FILE    -close  data/models/conduit/status/\1
> 
> Quite strange... any idea what's wrong??
> 
> Christian
> 
> 2007/3/28, Steve Chiswell <address@hidden>:
> > Christian,
> >
> > GFS is available in GRIB1 format at present for the 1 degree (F000-F180)
> > and 2.5 degree (F193-F384) grids. Grib2 format for the 0.5 degree grid
> > (F000-F180).
> >
> > The file names follow the naming conventions on:
> > http://www.unidata/data/conduit/ldm_idd/gfs_files.html
> >
> > The GEMPAK pqact actions I use and provide for the GRIB1 data are:
> > # 1.0 degree GFS data
> > # 2.5 degree GFS data
> > CONDUIT prod/gfs.*pgrb[^2]
> >         PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUITgfs.log
> >         -e GEMTBL=/home/gempak/NAWIPS/gempak/tables
> >
> > The [^2] pattern above restricts the above to just the grib2 products and
> > note the grib2 0.5 degree products.
> >
> > If you aren't seeing these products, be sure to check your ldmd.conf 
> > request line
> > to ensure you have an appropeiate pattern for the data you are expecting,
> > as well as any pattern used in your exec line for pqact.
> >
> > Steve Chiswell
> > Unidata User Support
> >
> >
> >
> >
> > On Wed, 2007-03-28 at 20:56 +0200, Christian Pag� wrote:
> > > Hello all,
> > >
> > > I have had network problems in the past few months with our ldm
> > > server, which turns out to be related to the firewall and --state NEW
> > > arguments in the iptables configuration. Now that it is fixed, I am
> > > reactivating CONDUIT data flow. However, I don't receive anymore GFS
> > > GRIB1 CONDUIT data: I am asking for status data, and no GRIB1 data is
> > > showing up for GFS. Has something changed in the meantime ?
> > >
> > > Many thanks
> > >
> > --
> > Steve Chiswell <address@hidden>
> > Unidata
> >
> 
> 


Ticket Details
===================
Ticket ID: CYE-443810
Department: Support CONDUIT
Priority: Normal
Status: Closed