-
-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some addons restart after uninstalling an unrelated addon #1354
Comments
Interesting, and also possibly the cause of this for bindings that have thing actions. |
I believe the root cause is here: #1322 (comment) Refreshing bundles where we do use declarative services (as far I know) is not needed.. |
I think I see the same strange beahviour last week when I uninstalled the Freebox binding, meaning other bindings were restarted. I can't say if all or only a part of the other bindings were restarted. |
It is a major bug, and critical issue imho. |
It seems that when multiple features install the same bundle it may cause Karaf to refresh bundles when (un)installing features. When the (redundant) openhab-core-automation feature is removed and the serial dependencies are merged into the openhab-transport-serial feature these restarts due these bundle refreshes no longer occur. Fixes openhab#1322, openhab#1354 Signed-off-by: Wouter Born <[email protected]>
It seems that when multiple features install the same bundle it may cause Karaf to refresh bundles when (un)installing features. When the (redundant) openhab-core-automation feature is removed and the serial dependencies are merged into the openhab-transport-serial feature these restarts due these bundle refreshes no longer occur. Fixes #1322, #1354 Signed-off-by: Wouter Born <[email protected]>
Signed-off-by: Jerome Luckenbach <[email protected]>
…ab#1709) It seems that when multiple features install the same bundle it may cause Karaf to refresh bundles when (un)installing features. When the (redundant) openhab-core-automation feature is removed and the serial dependencies are merged into the openhab-transport-serial feature these restarts due these bundle refreshes no longer occur. Fixes openhab#1322, openhab#1354 Signed-off-by: Wouter Born <[email protected]> GitOrigin-RevId: 76f5102
I believe this is a symptom of issues reported in the forum, where zigbee or zwave are no longer working after upgrading to 2.5. Logs show cyclic binding uninstalls, which is what I am seeing too. When uninstalling an addon, there are other addons being stopped and started. Included in these are zigbee and zwave. Zigbee does not behave well to binding restarts and usually requires an OH restart to get it working properly. Zwave handles binding restarts OK, but it is a resource hog and responsiveness in the zwave network will be much reduced. If this happens repeatedly, then I can understand why people think 2.5 is broken.
I was recently looking into the new icalendar binding and needed to remove the 1.x caldav-command to test something. I noticed in the log and figured it was time to report this. I suspect that zwave and zigbee are restarting due to org.openhab.core.config.serial being restarted. Here is the log...
The text was updated successfully, but these errors were encountered: