Closed ms4sman closed 5 months ago
@DSheirer thank you for the quick fix on this! I'm downloading the nightly now to test it out and will let you know if I still have any issues.
Polk County police scanner for all sites down since Saturday and wasn't able to contact you but this way
sdrtrunk Version 0.6.0
Describe the bug I'm running SDR-Trunk headless on a Raspberry Pi and it's been working great for several months now. But about a month or so ago, it suddenly started encountering some kind of fatal error almost every day that causes it to stop sending calls to my various servers. The Pi reboots every night, so after the reboot, it starts working again for a while, but most days, sometime during the day, it will encounter this error (I'll include below) and stop sending calls. Oddly, this error often appears in the log a couple of times BEFORE it stops sending calls. It's often not until the second or third time the error appears that it stops sending calls. Also, nothing appears in the logs folder about this. This information is from journalctl for the systemd service that I configured for SDR-Trunk.
To Reproduce Unfortunately I am not sure how to tell you to reproduce it, because I'm not sure why it suddenly started happening. I haven't touched the configuration of this pi in months, and it just suddenly started happening.
Expected behavior I'd expect it to not encounter this error, whatever it is, and continue sending calls without stopping.
Screenshots I do not have any screenshots relevant
Application Log
Desktop (optional - complete the following information): Raspberry Pi 4 Raspbian 2 GB memory
Additional context I know Raspberry Pi isn't recommended as the ideal platform for this, and 2 GB of memory is also pretty sparse, but I'm only monitoring a single system, using a single SDR stick. I've monitored the memory usage and it appears to not be even close to running out of memory or anything. The system doesn't seem to have any trouble keeping up with the one stick/one system I have it monitoring.