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

[LDM #CHX-269374]: NEXRAD3 feed did not fail over to backup when upstream LDM had an issue



Gilbert,

Was the NEXRAD3 feed part of a larger request (i.e., what are the relevant 
REQUEST entries in the LDM configuration-file)?

> Hello Steve,
> 
> Here at AllisonHouse, at 5:18Z last night, Texas A&M (hereafter TAMU)'s LDM
> stopped sending NEXRAD3 data; all other feeds, including the rest of
> NOAAport. was up and running fine. But, Wisconsin's NEXRAD3 feed was up. We
> have TAMU as primary; WISC as secondary. Based on the Skype discussion we
> had, we only had this one primary and one backup feed uncommented/active at
> the time. Unfortunately, the LDM (6.12.14) did not flip over the NEXRAD3
> feed to Wisconsin, which did have data. This is what we saw:
> 
> address@hidden root]$ notifyme -vl- -f NEXRAD3 -h ldm.tamu.edu
> 
> Jul 18 05:32:26 notifyme[11158] NOTE: Starting Up: ldm.tamu.edu:
> 20150718053226.880 TS_ENDT {{NEXRAD3, ".*"}}
> 
> Jul 18 05:32:26 notifyme[11158] NOTE: LDM-5 desired product-class:
> 20150718053226.880 TS_ENDT {{NEXRAD3, ".*"}}
> 
> Jul 18 05:32:26 notifyme[11158] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.001229 seconds
> 
> Jul 18 05:32:26 notifyme[11158] NOTE: NOTIFYME(ldm.tamu.edu): OK
> 
> Jul 18 05:37:53 notifyme[11158] NOTE: LDM-5 desired product-class:
> 20150718053226.880 TS_ENDT {{NEXRAD3, ".*"}}
> 
> Jul 18 05:37:53 notifyme[11158] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.005137 seconds
> 
> Jul 18 05:37:53 notifyme[11158] NOTE: NOTIFYME(ldm.tamu.edu): OK
> 
> --
> 
> address@hidden root]$ notifyme -vl- -f NEXRAD3 -h idd.aos.wisc.edu
> 
> Jul 18 05:41:10 notifyme[886] NOTE: Starting Up: idd.aos.wisc.edu:
> 20150718054110.678 TS_ENDT {{NEXRAD3, ".*"}}
> 
> Jul 18 05:41:10 notifyme[886] NOTE: LDM-5 desired product-class:
> 20150718054110.678 TS_ENDT {{NEXRAD3, ".*"}}
> 
> Jul 18 05:41:10 notifyme[886] INFO: Resolving idd.aos.wisc.edu to
> 144.92.130.88 took 0.00092 seconds
> 
> Jul 18 05:41:10 notifyme[886] NOTE: NOTIFYME(idd.aos.wisc.edu): OK
> 
> Jul 18 05:41:11 notifyme[886] INFO:      57916 20150718054110.707 NEXRAD3
> 380095859  SDUS81 KAKQ 180538 /pN0XDOX !nids/
> 
> Jul 18 05:41:11 notifyme[886] INFO:     143185 20150718054110.767 NEXRAD3
> 380095860  SDUS83 KDDC 180539 /pN0CDDC !nids/
> 
> Jul 18 05:41:11 notifyme[886] INFO:       6005 20150718054110.768 NEXRAD3
> 380095861  SDUS81 KAKQ 180538 /pN0MDOX !nids/
> 
> Jul 18 05:41:11 notifyme[886] INFO:       9595 20150718054110.769 NEXRAD3
> 380095862  SDUS81 KAKQ 180538 /pN0HDOX !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:       6005 20150718054110.770 NEXRAD3
> 380095863  SDUS82 KTBW 180537 /pN2MTBW !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:       6534 20150718054110.770 NEXRAD3
> 380095864  SDUS81 KAKQ 180538 /pN0KDOX !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:      16491 20150718054110.787 NEXRAD3
> 380095865  SDUS22 KCHS 180539 /pN3UCLX !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:      12929 20150718054110.789 NEXRAD3
> 380095866  SDUS56 KLOX 180540 /pNAQVBX !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:       5007 20150718054110.790 NEXRAD3
> 380095867  SDUS32 KCHS 180539 /pN3SCLX
> 
> Jul 18 05:41:12 notifyme[886] INFO:      11694 20150718054110.791 NEXRAD3
> 380095868  SDUS23 KTOP 180537 /pN3QTWX !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:       6668 20150718054110.791 NEXRAD3
> 380095869  SDUS33 KTOP 180537 /pN3STWX
> 
> Jul 18 05:41:12 notifyme[886] INFO:       4394 20150718054110.792 NEXRAD3
> 380095870  SDUS33 KLBF 180535 /pNSTLNX
> 
> Jul 18 05:41:12 notifyme[886] INFO:      35379 20150718054110.810 NEXRAD3
> 380095871  SDUS53 KMPX 180540 /pNAQMPX !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:       1019 20150718054110.810 NEXRAD3
> 380095872  SDUS33 KLBF 180535 /pNMDLNX
> 
> Jul 18 05:41:12 notifyme[886] INFO:      18502 20150718054110.827 NEXRAD3
> 380095873  SDUS24 KOUN 180539 /pN1QFDR !nids/
> 
> Jul 18 05:41:12 notifyme[886] INFO:      18903 20150718054110.830 NEXRAD3
> 380095874  SDUS53 KABR 180537 /pNCRABR
> 
> ^CJul 18 05:41:12 notifyme[886] NOTE: exiting
> 
> When we commented out TAMU for the NEXRAD3 feed in ldmd.conf, and restarted
> the LDM, NEXRAD3 data finally flowed. Why did automatic failover not
> happen? Is it because they are running older LDM versions? If one aspect of
> the feed fails (IDS|DDPLUS, or NEXRAD3, or HRS, etc), I expect the LDM to
> fail over to a different site...if not just for that feed, then for the
> whole thing. What say you?
> 
> Gilbert
> 
> --
> ----
> 
> Gilbert Sebenste
> Chief Meteorologist
> AllisonHouse, LLC

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: CHX-269374
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.