BClark09
commented
1 month ago I've not had this myself, but I have seen many talk about this issue. Is the openHAB process restarting (i.e. Karaf) or is the loop happening within openHAB's functions. If the former, then we can do a lot if an exit code is issued.
Add
openhab-cli clean-cache, too ? (I think it's done on package install so may not help to do again but not 100% sure)
It is done on package install or on update..
Or add a systemd timer to do a regular health check maybe ?
There are things we can test by polling the activeness of core bundles: https://github.com/openhab/openhab-linuxpkg/issues/138
I came to think if we can supervise startup, detect and break these loops ?
I've been wondering if it's related to the amount of time that openHAB takes to shut down or restart. If it takes more than 120 seconds, then the openHAB service is killed with a SIGTERM, and I wonder if this has any effect on the quality of the update.
mstormi
ecdye
miloit
At times, after updating the openHAB package, startup is stuck in a loop, spitting lots of java component errors. I came to think if we can supervise startup, detect and break these loops ? Unsure how, though.
Maybe if detected,
pkill -9 javamaybe add that to the update script option ? Addopenhab-cli clean-cache, too ? (I think it's done on package install so may not help to do again but not 100% sure) Or add a systemd timer to do a regular health check maybe ? Note that can be a dangerous sword should it mistakenly detect OH to be down. It should only be active for say some hours after openhab service startup time.