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

[LDM #AYS-975649]: notifyme works for one server but not the other ...

Hi Evan,

re:
> I have two AWIPS 2 EDEX servers which are nearly clones of each other and
> are, by there very architecture, downstream LDM servers. They both have
> (what appear to be) identical configuration, pointing to the same upstream
> LDM server.
> 
> *  ldmd.conf* is identical on both downstream servers:
> 
> REQUEST   FSL2    "XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."
> fxnet-ldm2.fsl.noaa.gov
> REQUEST   CONDUIT "^data.*gfs.*1p00" fxnet-ldm2.fsl.noaa.gov
> 
> 
> *  pqact.conf* is identical on both downstream servers (with *tabs* though
> not shown here):
> 
> # GSD HRRR-Smoke
> FSL2   (XGSD.GRIB.HRRR.Smoke.wrf.*)  FILE   -overwrite   -log   -close
> -edex  /awips2/edex/data/manual/ZZHH00.\1
> 
> 
> # GFS384 1 degree (1p00)
> CONDUIT
> data/nccf/com/gfs/prod/gfs\.[0-9]{8}\/[0-9]{2}\/gfs\.t[0-9]{2}z\.pgrb2\.1p00\.f[0-9]{3}\
> \!(grib2)/ncep/(GFS)/\#(000)/([0-9]{4})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})(F[0-9]{3})/([^/]*)/.*
> FILE -overwrite   -log  -close  -edex
> /awips2/edex/data/manual/ZZHH00.\7\8Z_\9_\(10)-ZZHH00_KWB
> 
> 
> My problem is that although both downstream servers successfully receive
> the "GFS384 1 degree" data, only one of the downstream LDM server receives
> the "HRRR-Smoke" data.
> 
> When I run a *notifyme* to query the HRRR-Smoke data, it, of course, works
> for the good server and fails for the bad:
> 
> *Good Downstream LDM server:*
> [ldm@a2-edex-dssdmz etc]$  notifyme -v -l - -h fxnet-ldm2.fsl.noaa.gov -p
> *"XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."* -o 10800
> Apr 09 04:18:00 notifyme[4328] NOTE: Starting Up: fxnet-ldm2.fsl.noaa.gov:
> 20200409011800.016 TS_ENDT {{ANY, "XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."}}
> Apr 09 04:18:00 notifyme[4328] NOTE: LDM-5 desired product-class:
> 20200409011800.016 TS_ENDT {{ANY, "XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."}}
> Apr 09 04:18:00 notifyme[4328] INFO: Resolving fxnet-ldm2.fsl.noaa.gov to
> 137.75.11.93 took 0.00201 seconds
> Apr 09 04:18:00 notifyme[4328] NOTE: NOTIFYME(fxnet-ldm2.fsl.noaa.gov): *OK*
> Apr 09 04:18:01 notifyme[4328] INFO:    5734413 20200409033920.687    FSL2
> 000  XGSD.GRIB.HRRR.Smoke.wrfnat.FX.2010000000042
> 
> 
> *Bad Downstream LDM server:*
> [ldm@a2-edex-dss etc]$ notifyme -v -l - -h fxnet-ldm2.fsl.noaa.gov -p
> *"XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."* -o 10800
> Apr 09 03:45:10 notifyme[27932] NOTE: Starting Up: fxnet-ldm2.fsl.noaa.gov:
> 20200409004510.065 TS_ENDT {{ANY, "XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."}}
> Apr 09 03:45:10 notifyme[27932] NOTE: LDM-5 desired product-class:
> 20200409004510.065 TS_ENDT {{ANY, "XGSD\.GRIB\.HRRR\.Smoke\.wrf...\.FX\."}}
> Apr 09 03:45:10 notifyme[27932] INFO: Resolving fxnet-ldm2.fsl.noaa.gov to
> 137.75.11.93 took 0.002568 seconds
> *(Doesn't get an OK ... waits forever)*
> 
> Why can't the "bad" server see the upstream HRRR-Smoke data? It doesn't
> have any problem receiving the GFS384 data?

It seems that the LDM on the upsream machine, fxnet-ldm2.fsl.noaa.gov, is
configured to ALLOW REQUESTs for the CONDUIT feed from both downstream LDM
machines, but FSL2 is ALLOWed only for the "Good Downstream LDM".

Question:

Do you have login access to the upstream machine as the user 'ldm'? If
yes, you can check to see how its ALLOWs are configured.

re:
> Seeing as all my configuration appears to be identical, I am stumped as to
> why this one data flavor can't be detected via the notifyme utility.

The configurations on the downstreams are, as you say, identical, but the
ALLOWs on the upstream LDM are evidently not.


Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: AYS-975649
Department: Support IDD
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.