Upgrading from 3.2 to 3.3 (after several restarts and cache cleaning), I face the following infinite loop preventing openhab starting :
18:50:16.350 [WARN ] [.core.karaf.internal.FeatureInstaller] - Could not determine addons folder, its content or the list of installed repositories!
18:50:16.351 [INFO ] [.core.karaf.internal.FeatureInstaller] - Some .kar files are not installed yet. Delaying add-on installation by 15s.
What looks strange in your case is this error: “Could not determine addons folder, its content or the list of installed repositories!”
In my case, at first startup, I have to wait but I don’t thing I got this error.
I‘m pretty sure that using the search function either here or on GitHub will bring up the steps to fix that. I can‘t recall from memory, but I walked someone through that some time ago.
Better check config:list "(service.pid=org.apache.felix.fileinstall*)" as we have seen that ~deploy seems to be OS specific: Fix KAR installation check by J-N-K · Pull Request #2845 · openhab/openhab-core · GitHub. I guess we again an issue where there are different configurations and the first listed is an outdated one. This could also be the cause for the add-on jars not loading issue.
What precisely should I check ? /opt/openhab/addons does not exist but I’m pretty sure it never existed (I’m debian based)
root# ls -l /usr/share/openhab/addons
total 4
-rw-r--r-- 1 openhab openhab 70 Dec 20 2021 README
root# ls -l /opt/openhab/addons
ls: cannot access '/opt/openhab/addons': No such file or directory
If that directory does not exist, try config:delete org.apache.felix.fileinstall.1b253c7d-1033-4848-8708-c778e47abccc and restart. Did you restore the configuration from another system? That could explain why that configuration is there.
I neved restored from anywhere else, I’m using the same server since openhab 2 and I updated to every 3.x
Please also note that I first deleted the configuration on 3.2, then installed (with debian aptitude) the 3.3 and the configuration for /opt/openhab/addons came back again. It is only after deleting it on 3.3 and restarting that it began to work.
I suggest a bugfix on the released 3.3 because I think I won’t be the only user impacted.
This can‘t be fixed for everyone. It‘s an issue with the local configuration and it‘s impossible to detect which configuration is correct. There have also been reports in the past with two invalid (and one valid) configurations.
No file-install configuration is as bad as two configurations. Please check if there is any org.apache.felix.fileinstall*.cfg in /var/lib/openhab/etc and post the content if it is. If not, please create one with the content linked above by @wborn.
But it still doesn’t work. The following entry still comes up in the openhab.log:
2022-07-03 23:03:00.065 [WARN ] [core.karaf.internal.FeatureInstaller] - Could not determine addons folder, its content or the list of installed repositories!
2022-07-03 23:03:00.066 [INFO ] [core.karaf.internal.FeatureInstaller] - Some .kar files are not installed yet. Delaying add-on installation by 15s.