30.10.2026, 13:58
Hello,
Just following up on rbourgeon’s posts with a few more details from our side
We’ve now seen the same behaviour on several LMs. As far as we can tell, it only started after we updated to firmware 20251204; we hadn’t encountered it before that
When it happens, there’s nothing in the LM error log
We haven’t tried swapping SD cards yet, as the affected devices are installed at customer sites
So far, we’ve tried:
- re-applying the firmware update
- removing the reactorra package — CPU usage drops — and then reinstalling the package
- rebooting the LM
All of these fix the issue temporarily, but the reactorra process eventually starts using excessive CPU again, for no obvious reason. (Note that we think re-applying the firmware only works because it triggers a reboot)
A reboot works temporarily, but it isn’t really a sustainable solution. Is there anything we should check or capture next time it happens, before rebooting?
Just following up on rbourgeon’s posts with a few more details from our side
We’ve now seen the same behaviour on several LMs. As far as we can tell, it only started after we updated to firmware 20251204; we hadn’t encountered it before that
When it happens, there’s nothing in the LM error log
We haven’t tried swapping SD cards yet, as the affected devices are installed at customer sites
So far, we’ve tried:
- re-applying the firmware update
- removing the reactorra package — CPU usage drops — and then reinstalling the package
- rebooting the LM
All of these fix the issue temporarily, but the reactorra process eventually starts using excessive CPU again, for no obvious reason. (Note that we think re-applying the firmware only works because it triggers a reboot)
A reboot works temporarily, but it isn’t really a sustainable solution. Is there anything we should check or capture next time it happens, before rebooting?