-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Describe the bug 🐞
When an asset starts and closes abruptly (due to bad configuration), the asset keeps it's feedback with Running. But the process has disappeared from the system.. If we try to stop it , it kills the broker and an exception appears in my System Log and the mqtt broker crashes.
If my config of the modbus asset is okay , this doesn't happen. Also, it doesn't happen if the asset stops normally. Only if the asset stops abruptly and keeps the feedback of RUNNING. This started to happen with the new HUB (with faster feedback).
To Reproduce 🔄
1- Open with the hub
2- Install a modbus asset
3- Start the asset with a configuration it will not work
4- Run the aset , try to pause the asset.
5 - A disconnect will appear
Expected behavior ✅
The asset would start and stop, and i could check in the log the issue. Central broker should not die.
Environment 🌐
Other (Please specify in 'Additional Info')
Additional Info ➕
Tested in all systems same behaviour - Raspian / Ubuntu / Windows / NixOS
Terms of Service
- I agree
AB#351
Metadata
Metadata
Assignees
Labels
Type
Projects
Status