rdio-scanner
rdio-scanner copied to clipboard
chuot
Http Failure Response
Hello,
I keep getting errors anytime I save my config via the admin interface. Anytime I make any kind of change and hit save, the rdio-scanner service in the background locks up for around 20-30 seconds and will fail to play any calls during that time until I am presented with an error that reads "Http failure response for http://ubuntu-sdr:3000/api/admin/config: 0 OK". Once the error displays, any call that came in during the lock up time starts to play. During this lock up time, you can still open the native app or web app and go to the different screens like talk groups, calls, etc. I have looked at the terminal output in these instances a couple of times and it spits out a bunch of dirwatch.walkdir errors saying that no such file or directory is found for some of my systems (this is correct as some of my systems do not have a directory yet as nothing has been recorded for those systems yet). Is this issue related to that? If I had directories for all my systems would it eliminate these errors?
A separate possibly related but probably unrelated issue I am having is with the Delete After option. I have this enabled in the dir watch options but I've never actually seen rdio-scanner delete any files that trunk-recorder is recording. If I am understanding the option correctly, rdio-scanner should be deleting the files that trunk-recorder generates after they are ingested into rdio-scanner, right?
Here's some additional info on my setup: Using trunk-recorder and rdio-scanner on ubuntu 21.04. On the latest version of trunk-recorder and using the latest version of rdio-scanner (6.3.6).
How many (total) talkgroups have you defined on your Rdio Scanner instance?
Is it possible for you to send me by email a copy of your Rdio Scanner config (tools / export config)?
I have quite a few talkgroups (several hundred) but I am not sure that's the issue. I started my setup on a raspberry pi with the same number of talkgroups and that instance of rdio-scanner was working fine. It wasn't until I moved my setup to my home server on an Ubuntu VM running on unraid that the problem started. I'll send you a copy of my config json right now.
Unfortunately I wasn't able to reproduce the issue even with your config file. Is this reproducible every time on your end?
When it happens, try to force a reload (shift-reload) of the admin page, then try again.
I tried shift-reload of the admin page as well as updating to 6.4.0 and the issue remains. I guess I can live with it as things still work and I have my system pretty much all the way set up now. Its just an annoyance when saving the config at this point because it crashes for about 30 seconds and then starts up again.
Does it crash or did it freeze?
If it crashes, try to get the crash logs with journalctl -u rdio-scanner.service.
If it's frozen, try kill -3 on the process id. This will generate a crash log which can be helpful in identifying the root cause.
It freezes... Sorry, that's what I meant in my precious comment. I'll give that a shot. Thanks
I just tried on 6.4.5 and unfortunately its still doing it. It must be something with my config...
Its just a minor annoyance at this point since my system is all set up i'm not changing things very often anymore.
I tried to reproduced your issue but did not succeed to.
Please try with the v6.5.1 which is just out. If you still have the issue, please post all the logs with the error messages. Unfortunately, I can't help much without them.
Simplest way is to start rdio-scanner from the command line, let it run until it freezes or when it shows the HTTP 0 OK error on the administrative dashboard (which shouldn't anymore), then kill -3 the PID of rdio-scanner, grab all the stack trace and post it here (as an attachment).