Open alzuno opened 11 hours ago
@alzuno I'd seen some problems like this but was hoping that I'd fixed it.
Are you running on a Raspberry Pi or another platform? (I'm guessing by your machine name in the logs that it's a Raspberry Pi3.)
Is the software running as the user goveebttemplogger instead of root? (one of my recent changes was to avoid running as root)
Are you running anything else that uses Bluetooth? (Keyboard, Mouse, or any other program?)
Am I correct that the Bluetooth appears to not work at all after this problem occurs, and the only way to recover it is to reboot the entire machine?
I've seen this issue and am not sure what's happening. There may be something I'm not cleaning up in the DBus communication that is causing BlueZ to leak memory and stop responding. It seems wrong that a user mode program can crash a piece of system software..
You should be able to revert to the old hardware Bluetooth Hardware Control Interface by adding the --HCI option to the end of the command line, but that probably won't recover the Bluetooth after it's locked up. Using HCI took exclusive control of the Bluetooth interface and has been deprecated for several years.
@alzuno Commits I made today https://github.com/wcbonner/GoveeBTTempLogger/commit/c8e2cd16bce06fd4db5d36624addba28b6471faa and then https://github.com/wcbonner/GoveeBTTempLogger/commit/6b895c515abb1a28d4ec0a7aba391b6e14c7bcb8 bring the version up to 3.20241115.1 and I'm hoping will squash the issue you have for good.
I'm going to run this on my primary machines for a couple of days before creating a new release, but I'm interested if this fixes the issue on your platform.
Hi @wcbonner,
I've been experiencing recurring service interruptions. Over the past month, the system hasn't remained up for more than 24 hours. Previously, it would sometimes run for a month without any issues.
From the logs, I noticed this recurring error:
/org/bluez/hci0: org.bluez.Adapter1: StopDiscovery: Error: Operation already in progress /home/pi/GoveeBTTempLogger/goveebttemplogger.cpp(3918)
After this error appears, the logging stops entirely. The only way to get the system working again is to reboot the Raspberry Pi.
Here a piece of logs from the system:
I ran the system on the console and observed the same issue:
Additional Information:
Thanks for your help!