Anyone else having issues with SDRTrunk (or other software) unable to download the State Trunked Systems: Allied Radio Matrix for Emergency Response (ARMER) for Minnesota? It just hangs when I click on that tab. The other tabs (like County Agencies, National Agencies, etc.) do produce some frequencies, so I'm suspecting a back-end database and/or API issue.
SDRTrunk & Minnesota State Trunked Systems ARMER List Issues
- Thread starter KD0KZE
- Start date
I wouldn't call it an issue on the RR side. There is a tremendous amount of information to pull in for any statewide system (I know from experience with Ohio MARCS). I run SDRTrunk. Even if you are running it on a very fast computer, there will be a lag pulling in all of that information. If you're running SDRTrunk on a PI or a Chromebook, or a 15 year old computer, it is likely going to take forever and a day for it to pull it all in. And then, when it does and you go to manage the alias list to add/delete stuff, you'll encounter it over and over.
Pretty normal if you ask me, if you are running it on lower end devices and trying to pull in all the information for a statewide system.
I've done it several times for the past 6-7 years or so, same PC, and not seen these issues. I think it normally takes < 5 minutes. I believe I most recently did it in May of this year. I wouldn't expect too many frequency changes, but I like to inspect it on occasion.
I'll check again, but I still do suspect some sort of back-end DB issue. It would be nice if I could run the API manually, like an XML/REST or curl/wget type lookup and see if anything is coming out of the pipe. If so, then I'd suspect a problem with SDRTrunk, parsing, permissions, an API Java library or some such. If even a native wget/curl API call also hangs, then I would suspect an issue w/RadioReference.
I have mixed feelings about "AI", but Google's answer included this (snippet) while I searched for issues regarding SDRTrunk and downloading from RadioReference:
"...Database Errors: Occasionally, errors within the RadioReference database itself (such as incomplete or unknown county IDs) can cause import failures.
- Solution: This typically requires a fix by the database administrators or the SDRTrunk developer. Check the RadioReference forums for recent discussions on system-specific import issues."
I did some sleuthing at my end and found some network behavior that might be involved (I've worked in the IT field for 30 years). Namely, most all of the standard tabs in SDRTrunk do properly pull down the frequency lists: County Agencies, State Agencies and National Agencies. I can see my IP immediately hitting the API server/s and issuing the lookup for the XML data, which properly comes back to populate the appropriate screen in SDRTrunk.
However, County Trunked Systems and State Trunked Systems simply hang -- there is no traffic. But 1-2 times in the past couple days it actually did work for whatever reason. The traffic was quick, it involved several TCP/IP exchanges since the list is rather large, and then the screen gets populated within 1-3 minutes or so.
When it doesn't work, it's not that it's slow -- there's simply no traffic at all. I suspect that a cloudfare issue, firewall, or caching layer might be involved and it automatically stops the lookup from even starting. I could be barking up the wrong tree, but I can't debug any more at my end. I'm just throwing this out there in case anyone else sees similar issues, particularly on the larger XML/soap lookups. I couldn't hazard a guess what the solution is, maybe some config issue they need to adjust on cloudflare, to prevent it from being overly-aggressive at firewall protection, etc?
However, County Trunked Systems and State Trunked Systems simply hang -- there is no traffic. But 1-2 times in the past couple days it actually did work for whatever reason. The traffic was quick, it involved several TCP/IP exchanges since the list is rather large, and then the screen gets populated within 1-3 minutes or so.
When it doesn't work, it's not that it's slow -- there's simply no traffic at all. I suspect that a cloudfare issue, firewall, or caching layer might be involved and it automatically stops the lookup from even starting. I could be barking up the wrong tree, but I can't debug any more at my end. I'm just throwing this out there in case anyone else sees similar issues, particularly on the larger XML/soap lookups. I couldn't hazard a guess what the solution is, maybe some config issue they need to adjust on cloudflare, to prevent it from being overly-aggressive at firewall protection, etc?
Similar threads
- Locked
