Some .kar files are not installed yet - Fresh installation - Config backup

  • Platform information:

    • Hardware: Raspberry Pi 3 Model B Rev 1.2
    • OS: Debian GNU/Linux 11 (bullseye)
    • Java Runtime Environment:
      openjdk version “17.0.9” 2023-10-17
      OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb11u1)
      OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb11u1, mixed mode, sharing)
    • openHAB version: openHAB 4.1.1
  • Issue of the topic: after fresh installation via etcher and import of backed up of a the full configuration from openhab 3.x, the log shows
    [core.karaf.internal.FeatureInstaller] - Some .kar files are not installed yet.

  • If logs where generated please post these here using code fences:
    [core.karaf.internal.FeatureInstaller] - Some .kar files are not installed yet. Delaying add-on installation by 15s.

Any hints to avoid this / overcome this?
Currently no openhab is not running fully. Rules are not executed and some other stuff as well is not working now.
This happens always.
Also tried reinstalling the addons without success
apt install --reinstall openhab-addons

Additional log information

.apache.karaf.features/framework/4.3.7/xml/features
	at org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:121) ~[?:?]
	at org.apache.karaf.features.internal.service.RepositoryImpl.<init>(RepositoryImpl.java:51) ~[?:?]
	at org.apache.karaf.features.internal.service.RepositoryCacheImpl.create(RepositoryCacheImpl.java:51) ~[?:?]
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.registerListener(FeaturesServiceImpl.java:274) ~[?:?]
	at org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:194) ~[?:?]
	at org.apache.karaf.util.tracker.BaseActivator.start(BaseActivator.java:92) ~[?:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl$2.run(BundleContextImpl.java:818) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl$2.run(BundleContextImpl.java:1) ~[org.eclipse.osgi-3.18.0.jar:?]
	at java.security.AccessController.doPrivileged(AccessController.java:569) [?:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:810) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:767) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1032) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:371) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.Module.doStart(Module.java:605) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.Module.start(Module.java:468) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) [org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) [org.eclipse.osgi-3.18.0.jar:?]
Caused by: java.io.IOException: Error resolving artifact org.apache.karaf.features:framework:xml:features:4.3.7: [Could not find artifact org.apache.karaf.features:framework:xml:features:4.3.7 in openhab (https://openhab.jfrog.io/openhab/libs-release/)]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException(AetherBasedResolver.java:803) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:774) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:657) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:598) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:565) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:555) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123) ~[?:?]
	at java.net.URL.openStream(URL.java:1161) ~[?:?]
	at org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:114) ~[?:?]
java.lang.RuntimeException: Error resolving artifact org.apache.karaf.features:framework:xml:features:4.3.7: [Could not find artifact org.apache.karaf.features:framework:xml:features:4.3.7 in openhab (https://openhab.jfrog.io/openhab/libs-release/)] : mvn:org.apache.karaf.features/framework/4.3.7/xml/features

java.lang.RuntimeException: Error resolving artifact org.apache.karaf.features:framework:xml:features:4.3.7: [Could not find artifact org.apache.karaf.features:framework:xml:features:4.3.7 in openhab (https://openhab.jfrog.io/openhab/libs-release/)] : mvn:org.apache.karaf.features/framework/4.3.7/xml/features

java.lang.RuntimeException: Error resolving artifact org.apache.karaf.features:standard:xml:features:4.3.7: [Could not find artifact org.apache.karaf.features:standard:xml:features:4.3.7 in openhab (https://openhab.jfrog.io/openhab/libs-release/)] : mvn:org.apache.karaf.features/standard/4.3.7/xml/features

Often errors like these can be addressed through Clear the Cache.

You have to be careful when restoring a backup from a different OH version. If it was a full backup, it means you got the cache and tmp folders too. As a result you overwrote the 4.1 stuff with 3.x stuff and they of course the 3.x stuff can’t run on 4.1.

Also note that most people have reported that restoring a 3.x backup to a 4.0/4.1 does work, this is not always guaranteed to work.

Don’t forget to run the upgrade tool before running OH for the first time after restoring the backup.

The normal most likely to work approach is to:

  1. Backup the old full system, upgrade the old to 4.1, take the backup, then restore the 4.1 backup to the 4.1 instance; if you run into trouble restore the backup you took at the beginning.
  2. Backup OH, install 3.4 on the new machine, restore the OH backup, then do an in place upgrade to 4.1.
1 Like

Indeed Rich, this does the trick!
Thanks so much.
Solved & can be closed