Closed sentry-io[bot] closed 1 year ago
these were removed in https://github.com/NebraLtd/hm-pktfwd/commit/4d5526244045b89f39b97e764dd7c3ddf4b05d29
Maybe we should add them back in as fallbacks?
I mean these ones:
"region_as923_1": "AS923-1-global_conf.json",
"region_as923_2": "AS923-2-global_conf.json",
"region_as923_3": "AS923-3-global_conf.json",
"region_as923_4": "AS923-4-global_conf.json",
"region_au915": "AU-global_conf.json",
"region_cn470": "CN-global_conf.json",
"region_eu433": "EU433-global_conf.json",
"region_eu868": "EU-global_conf.json",
"region_in865": "IN-global_conf.json",
"region_kr920": "KR-global_conf.json",
"region_ru864": "RU-global_conf.json",
"region_us915": "US-global_conf.json"
Not sure if you think #116 is a reasonable solution @pritamghanghas ?
@MuratUrsavas Are any fleets using REGION_OVERRIDE with old value at device level or fleet level. This should not happen if our fleets are updated and there is no REGION_OVERRIDE.
@pritamghanghas No, I've not seen that in our current fleets. Checked while moving to open/commercial fleets.
Could it be that they were running some old miner code or something?
check the miner with the error. On this device the miner info command returns undefined. The file has some old value. This is just one device. I will just override it for the time being.
/opt/miner # /opt/miner/bin/miner info region undefined
Sentry Issue: HM-PKTFWD-7