-
-
Notifications
You must be signed in to change notification settings - Fork 391
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
Karaf cache not cleaned after upgrade #1696
Comments
When you mention Karaf cache, do you mean If If |
did not manually remove anything. Used `openhab-cli clean-cache`, can you compare what that does to those dirs you named?
Am 14. November 2024 19:40:44 MEZ schrieb Ben Clark ***@***.***>:
…When you mention Karaf cache, do you mean `cache` and `tmp` directories inside `${OPENHAB_USERDIR}`? or just the `karaf` dir?
If `cache` and `tmp`, these are indeed removed in the [distro's update scripts](https://github.com/openhab/openhab-distro/blob/main/distributions/openhab/src/main/resources/bin/update#L321C1-L324C43) without condition. (Note that [Linuxpkg does this in a similar way](https://github.com/openhab/openhab-linuxpkg/blob/main/resources/control-runtime/preinst#L84)). Have you tried completing an upgrade without openHAB running and then looking to see if the files still exist?
If `.karaf`, what is stored here? I thought it was just the console history?
|
Not sure if it helps. I do see sometimes start-up issues (Bindings not all initializing, etc) on the first start after an upgrade. Most of the time I do a stop, clean-cache, restart. However, I was also able to get a clean start after a stop and start without cache clean. Maybe there are sometimes timing issues in the first start after an upgrade. Unfortunately, this seems not to be reproducible. |
I noticed on various occasions that openHAB didn't start properly after a package upgrade.
On every of these, I had to manually clean the cache to make it finally start (or to proceed after start, actually - it starts in fact but keeps hanging).
@BClark09 I'd prefer if we sort this out before OH 4.3 release Dec 15.
The text was updated successfully, but these errors were encountered: