Hi John,
re: testing ALLOWs on two upstream relays for NEXRAD2
> So far so good:
>
> [ldm@adiabat nordlie]$ notifyme -vl- -f NEXRAD2 -h idd.tamu.edu
> Mar 30 00:45:47 notifyme[16278] NOTE: Starting Up: idd.tamu.edu:
> 20140330004547.544 TS_ENDT {{NEXRAD2, ".*"}}
> Mar 30 00:45:47 notifyme[16278] NOTE: LDM-5 desired product-class:
> 20140330004547.544 TS_ENDT {{NEXRAD2, ".*"}}
> Mar 30 00:45:47 notifyme[16278] INFO: Resolving idd.tamu.edu to
> 128.194.76.175 took 0.142035 seconds
> Mar 30 00:45:47 notifyme[16278] NOTE: NOTIFYME(idd.tamu.edu): OK
> Mar 30 00:45:48 notifyme[16278] INFO: 15356 20140330004547.576 NEXRAD2
> 150016 L2-BZIP2/KLSX/20140330004241/150/16/I/V06/0
> Mar 30 00:45:48 notifyme[16278] INFO: 10413 20140330004547.632 NEXRAD2
> 461019 L2-BZIP2/KDTX/20140330004201/461/19/I/V06/0
> <snip>
>
> and:
>
> [ldm@adiabat ~/etc]$ notifyme -vl- -f NEXRAD2 -h idd.unidata.ucar.edu
> Mar 30 00:49:06 notifyme[16288] NOTE: Starting Up: idd.unidata.ucar.edu:
> 20140330004906.605 TS_ENDT {{NEXRAD2, ".*"}}
> Mar 30 00:49:06 notifyme[16288] NOTE: LDM-5 desired product-class:
> 20140330004906.605 TS_ENDT {{NEXRAD2, ".*"}}
> Mar 30 00:49:06 notifyme[16288] INFO: Resolving idd.unidata.ucar.edu to
> 128.117.140.3 took 0.061164 seconds
> Mar 30 00:49:06 notifyme[16288] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK
> Mar 30 00:49:07 notifyme[16288] INFO: 11392 20140330004906.759 NEXRAD2
> 550024 L2-BZIP2/KGGW/20140330004702/550/24/I/V06/0
> Mar 30 00:49:07 notifyme[16288] INFO: 5888 20140330004906.877 NEXRAD2
> 940001 L2-BZIP2/KPAH/20140330004904/940/1/S/V06/0
Excellent, this verifies that you are ALLOWed to REQUEST NEXRAD2 on both
idd.tamu.edu and idd.unidata.ucar.edu.
re:
> I changed our ldmd.conf to include:
>
> # CRAFT radar data:
> # request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 129.15.194.231
> # request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 129.15.194.232
> # request ANY-GEM-EXP-NEXRAD2-GPS-CONDUIT ".*" 129.15.194.233
>
> request NEXRAD2 ".*" idd.tamu.edu
> request NEXRAD2 ".*" idd.unidata.ucar.edu
Very good.
re:
> The load factor is spiking around 16, but that's probably a problem
> on our end (just need more computational horsepower, all it takes
> is time and money, right? :-).
The question is what is hammering your machine? The processing for
data that has been missing for awhile is one possibility, but the
typical way to process Level II data is to FILE it to disk, and this
typically takes very little CPU.
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: KOV-575304
Department: Support IDD
Priority: Normal
Status: Closed