Skip to content
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

Open
mstormi opened this issue Nov 14, 2024 · 3 comments
Open

Karaf cache not cleaned after upgrade #1696

mstormi opened this issue Nov 14, 2024 · 3 comments
Labels
bug An unexpected problem or unintended behavior

Comments

@mstormi
Copy link
Contributor

mstormi commented Nov 14, 2024

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.

@mstormi mstormi added the bug An unexpected problem or unintended behavior label Nov 14, 2024
@BClark09
Copy link
Member

BClark09 commented Nov 14, 2024

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 without condition. (Note that Linuxpkg does this in a similar way). 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?

@mstormi
Copy link
Contributor Author

mstormi commented Nov 14, 2024 via email

@mike-bike
Copy link

mike-bike commented Nov 14, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants