Suddenly unable to access openHAB

Hardware: Raspberry Pi 4 (I think)
OS: Raspbian
openHAB version:4.0.0

I went on vacation for a week, and when I came back could no longer access openHAB (not able to see anything via the web interface on port 8080). I tried just restarting the raspberry pi, and it didn’t help. I can log in to the raspberry pi remotely, so the pi itself is working.

Because of the problem I (maybe stupidly) decided to upgrade packages, and it looks like openHAB got upgraded to version 4.0.0, but I still can’t access it, and the raspberry pi is still accessible.

If I check the openHAB service status in linux command line, I get this (looks like the service is running but something is wrong):

openhab.service - openHAB - empowering the smart home
   Loaded: loaded (/lib/systemd/system/openhab.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2023-02-27 19:23:21 GMT; 3min 26s ago
     Docs: https://www.openhab.org/docs/
           https://community.openhab.org
 Main PID: 479 (java)
    Tasks: 38 (limit: 4915)
   CGroup: /system.slice/openhab.service
           └─479 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/share/openhab/runtime -Dopenhab.userdata=/var/lib/openhab -Dopenhab.logdir=/var/log/openha

Feb 27 19:24:10 raspberrypi karaf[479]:         ... 13 more
Feb 27 19:24:10 raspberrypi karaf[479]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core.storage.json/4.0.0.202302270306: missing requirement [org.openhab.core.storage.json/4.0
Feb 27 19:24:10 raspberrypi karaf[479]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Feb 27 19:24:10 raspberrypi karaf[479]:         ... 14 more
Feb 27 19:24:10 raspberrypi karaf[479]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core.config.core/4.0.0.202302270304: missing requirement [org.openhab.core.config.core/4.0.0
Feb 27 19:24:10 raspberrypi karaf[479]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Feb 27 19:24:10 raspberrypi karaf[479]:         ... 15 more
Feb 27 19:24:10 raspberrypi karaf[479]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee;
Feb 27 19:24:10 raspberrypi karaf[479]:         at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Feb 27 19:24:10 raspberrypi karaf[479]:         ... 16 more
~
~
~

and the openhab.log file contains this:

2023-02-27 19:28:22.371 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.venstarthermostat-3.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.venstarthermostat [26]
  Unresolved requirement: Import-Package: org.openhab.core.config.core.status

	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.7.4]
2023-02-27 19:28:22.373 [ERROR] [ternal.service.BootFeaturesInstaller] - Error installing boot features
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-runtime-ui; type=karaf.feature; version="[4.0.0.SNAPSHOT,4.0.0.SNAPSHOT]"; filter:="(&(osgi.identity=openhab-runtime-ui)(type=karaf.feature)(version>=4.0.0.SNAPSHOT)(version<=4.0.0.SNAPSHOT))" [caused by: Unable to resolve openhab-runtime-ui/4.0.0.SNAPSHOT: missing requirement [openhab-runtime-ui/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=openhab-core-ui-icon; type=karaf.feature [caused by: Unable to resolve openhab-core-ui-icon/4.0.0.SNAPSHOT: missing requirement [openhab-core-ui-icon/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=openhab-core-base; type=karaf.feature [caused by: Unable to resolve openhab-core-base/4.0.0.SNAPSHOT: missing requirement [openhab-core-base/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.core.automation; type=osgi.bundle; version="[4.0.0.202302270306,4.0.0.202302270306]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.core.automation/4.0.0.202302270306: missing requirement [org.openhab.core.automation/4.0.0.202302270306] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core)(version>=4.0.0)(!(version>=5.0.0)))" [caused by: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"]]]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:433) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:420) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:374) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257) ~[?:?]
	at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:399) ~[?:?]
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069) ~[?:?]
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:1004) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve openhab-runtime-ui/4.0.0.SNAPSHOT: missing requirement [openhab-runtime-ui/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=openhab-core-ui-icon; type=karaf.feature [caused by: Unable to resolve openhab-core-ui-icon/4.0.0.SNAPSHOT: missing requirement [openhab-core-ui-icon/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=openhab-core-base; type=karaf.feature [caused by: Unable to resolve openhab-core-base/4.0.0.SNAPSHOT: missing requirement [openhab-core-base/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.core.automation; type=osgi.bundle; version="[4.0.0.202302270306,4.0.0.202302270306]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.core.automation/4.0.0.202302270306: missing requirement [org.openhab.core.automation/4.0.0.202302270306] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core)(version>=4.0.0)(!(version>=5.0.0)))" [caused by: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"]]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve openhab-core-ui-icon/4.0.0.SNAPSHOT: missing requirement [openhab-core-ui-icon/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=openhab-core-base; type=karaf.feature [caused by: Unable to resolve openhab-core-base/4.0.0.SNAPSHOT: missing requirement [openhab-core-base/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.core.automation; type=osgi.bundle; version="[4.0.0.202302270306,4.0.0.202302270306]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.core.automation/4.0.0.202302270306: missing requirement [org.openhab.core.automation/4.0.0.202302270306] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core)(version>=4.0.0)(!(version>=5.0.0)))" [caused by: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"]]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve openhab-core-base/4.0.0.SNAPSHOT: missing requirement [openhab-core-base/4.0.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.core.automation; type=osgi.bundle; version="[4.0.0.202302270306,4.0.0.202302270306]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.core.automation/4.0.0.202302270306: missing requirement [org.openhab.core.automation/4.0.0.202302270306] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core)(version>=4.0.0)(!(version>=5.0.0)))" [caused by: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"]]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core.automation/4.0.0.202302270306: missing requirement [org.openhab.core.automation/4.0.0.202302270306] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core)(version>=4.0.0)(!(version>=5.0.0)))" [caused by: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core/4.0.0.202302270301: missing requirement [org.openhab.core/4.0.0.202302270301] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.17.200.jar:?]
	... 12 more
2023-02-27 19:28:22.411 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.verisure-3.2.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.verisure [27]
  Unresolved requirement: Import-Package: org.openhab.core.config.discovery

	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.17.200.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.7.4]

Any ideas how to fix it?

did you upgrade to Java 17? I think it is required
see: openHAB 4.0 SNAPSHOT discussion

How did you do the upgrade? Unless you are on the SNAPSHOTS repo an upgrade should not have moved you to 4.0. 4.0 is really rough with breaking changes being made left and right. Unless you are willing to dedicate yourself to lots of debugging and participating in reporting issues as they arise, I cannot recommend running 4.0 yet.

Change your repo to the release repo and install OH 3.4.2.

Amen to that! Running 4.0 snapshots right now is not for the faint of heart. I have two production systems running 4.0 snapshots, but I’m REALLY (and I mean REALLY) careful about which snapshots I decide to install. Unless you’re willing to endure a lot of pain, take Rich’s suggestion and go back to 3.4.2.

I have a similar issue. I am running the latest 3.4 release version via openhabian. I noticed quite a few things offline and haven’t updated for a while. So I went to openhabian-config and to upgrade system and now openHAB is dead. Unable to resolve openhab.org core/4 M1.

Blockquote

● openhab.service - openHAB instance, reachable at http://openhabian:8080
Loaded: loaded (/lib/systemd/system/openhab.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/openhab.service.d
└─override.conf
Active: active (running) since Sat 2023-03-11 11:23:06 GMT; 3min 37s ago
Docs: Introduction | openHAB
https://community.openhab.org
Main PID: 14235 (java)
Tasks: 38 (limit: 4915)
CGroup: /system.slice/openhab.service
└─14235 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/share/openhab/runtime -Dopenhab.userdata=/var/lib/openhab -Dopenhab.logdir=/var/log/openhab -Dfelix.cm

Mar 11 11:23:22 openhabian karaf[14235]: … 12 more
Mar 11 11:23:22 openhabian karaf[14235]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve openhab-core-base/4.0.0.M1: missing requirement [openhab-core-base/4.0.0.M1] osgi.identity; osgi.identity=org.openhab
Mar 11 11:23:22 openhabian karaf[14235]: at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Mar 11 11:23:22 openhabian karaf[14235]: … 13 more
Mar 11 11:23:22 openhabian karaf[14235]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core.config.core/4.0.0.M1: missing requirement [org.openhab.core.config.core/4.0.0.M1] osgi.wiring.packag
Mar 11 11:23:22 openhabian karaf[14235]: at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Mar 11 11:23:22 openhabian karaf[14235]: … 14 more
Mar 11 11:23:22 openhabian karaf[14235]: Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core/4.0.0.M1: missing requirement [org.openhab.core/4.0.0.M1] osgi.ee; filter:="(&(osgi.ee=JavaSE)(versi
Mar 11 11:23:22 openhabian karaf[14235]: at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
Mar 11 11:23:22 openhabian karaf[14235]: … 15 more

Blockquote

I am already on the release version in openhabian. What’s the best way to return to a functional system?

  • word “release” is refering to openhabian, right ?
  • it is your intend to go from OH 3.4.2 to a milestone release ( 4.0.0.M1 ) ?
  • what is the content of /etc/apt/sources.list.d/openhab.list ?
  • does it point to main or to testing ( the later installs the 4.0.0.M1 milestone release ) ?
  • in case you want to continue with milestone release you noted that you need to upgrade you Java version as well as stated in the release notes ?

Hi @Wolfgang_S ,

I had no intention of upgrading to Openhab 4. I was on a stable release of 3.4. I am using openhabian and that has always been set to release (most stable version).

So I don’t know why openhabian upgraded from 3.4 to 4 even though it was set to stable release. Sources.list below shows that testing has been set. Not sure how though.

My intention is to somehow return the installation to the latest stable version of 3.4.

I would appreciate some guidance on how to achieve this, can I simply change the sources.list from testing to stable?

deb https://openhab.jfrog.io/artifactory/openhab-linuxpkg testing main

If your on an openhabian system you should use one of the first two options of OPTION $! (i.e openHAB Release or openHAB Milestone). Most probably you did use the third option (inadvertendly).

The repository uses stable ( prodution releases ) , testing ( milestones ) , unstable ( snapshots ).
You can edit the file /etc/apt/sources.list.d/openhab.list but you also can use openhabian-config to do so using option 41.
Officially there is no way to downgrade a release which would be the case by downgrading from 4.0 to 3.4.2. In case the json database already was touched you most probably need to manually go back with your configuration files.

Thanks, @Wolfgang_S - I have some config file backups from a few months ago. So as far as I understand it, even though the sources.list was set to testing (milestone) on Ver 3.4.2, openhabian should never have upgraded the system to openhab 4. Is that correct? Just want to make sure so that I don’t make the same mistake again.

To prevent that from happening pinning for a specific version would have to be done. Which is not done. This is why this kind of updates/upgrades are happening.
In case you manually call the update, upgrade procedure you can do a try run and will see what will happen in case the upgrade command is executed. As openhabian-config is some kind of UI for non linux experts this is not being shown and just executed as the software ‘assumes’ everything that is requested will be done.
This also will happen for users that are in stable release at this moment. Once OH4 will be made a stable version the upgrade from OH3 to OH4 will take place as well.

So I have managed to recover by changing the openhab version from testing to stable. I did this in openhabian-config. Openhab was then re-installed and after a couple of reboots the system is back without needing to restore config files. It looks like Openhab 3 Milestone release option is now pointing to Openhab 4 M1. Hence when I used Openhabian to upgrade the system it partly upgraded to 4M1.

Is that how it should be? Are all new milestone releases on Ver.4 and no longer on Ver.3?

To reiterate what @Wolfgang_S said, each repo always points to the most recent release of that type. That’s the way it is, has been and is supposed to be.

The most recent release is 3.4.2.
The most recent testing release is 4.0.0 M1.
The most resent snapshot is 4.0.0 SNAPSHOT #33?? (I don’t know the latest number).

1 Like

Liebe Gemeinde,
Leider ist mein Englisch nicht ausreichend um meiner Kritik Luft zu machen.
Nach einem sudo openhabian-config mal wieder ein abgeschossenes System mit der Meldung
2023-03-17 13:11:13.142 [ERROR] [ternal.service.BootFeaturesInstaller] - Error installing boot features

org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-runtime-ui; type=karaf.feature; version=“[4.0.0.M1,4.0.0.M1]”; filter:=“(&(osgi.identity=openhab-runtime-ui)(type=karaf.feature)(version>=4.0.0.M1)(version<=4.0.0.M1))” [caused by: Unable to resolve openhab-runtime-ui/4.0.0.M1: missing requirement [openhab-runtime-ui/4.0.0.M1] osgi.identity; osgi.identity=org.openhab.ui.iconset.classic; type=osgi.bundle; version=“[4.0.0.M1,4.0.0.M1]”; resolution:=mandatory [caused by: Unable to resolve org.openhab.ui.iconset.classic/4.0.0.M1: missing requirement [org.openhab.ui.iconset.classic/4.0.0.M1] osgi.wiring.package; filter:=“(osgi.wiring.package=org.openhab.core.i18n)” [caused by: Unable to resolve org.openhab.core/4.0.0.M1: missing requirement [org.openhab.core/4.0.0.M1] osgi.ee; filter:=“(&(osgi.ee=JavaSE)(version=17))”]]]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:433) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:420) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:374) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:256) ~[?:?]

at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:399) ~[?:?]

at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069) ~[?:?]

at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:1004) ~[?:?]

at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]

at java.lang.Thread.run(Thread.java:829) ~[?:?]

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve openhab-runtime-ui/4.0.0.M1: missing requirement [openhab-runtime-ui/4.0.0.M1] osgi.identity; osgi.identity=org.openhab.ui.iconset.classic; type=osgi.bundle; version=“[4.0.0.M1,4.0.0.M1]”; resolution:=mandatory [caused by: Unable to resolve org.openhab.ui.iconset.classic/4.0.0.M1: missing requirement [org.openhab.ui.iconset.classic/4.0.0.M1] osgi.wiring.package; filter:=“(osgi.wiring.package=org.openhab.core.i18n)” [caused by: Unable to resolve org.openhab.core/4.0.0.M1: missing requirement [org.openhab.core/4.0.0.M1] osgi.ee; filter:=“(&(osgi.ee=JavaSE)(version=17))”]]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

... 12 more

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.ui.iconset.classic/4.0.0.M1: missing requirement [org.openhab.ui.iconset.classic/4.0.0.M1] osgi.wiring.package; filter:=“(osgi.wiring.package=org.openhab.core.i18n)” [caused by: Unable to resolve org.openhab.core/4.0.0.M1: missing requirement [org.openhab.core/4.0.0.M1] osgi.ee; filter:=“(&(osgi.ee=JavaSE)(version=17))”]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

... 12 more

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core/4.0.0.M1: missing requirement [org.openhab.core/4.0.0.M1] osgi.ee; filter:=“(&(osgi.ee=JavaSE)(version=17))”

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

... 12 more

Macht einfach kein Spaß mehr. Die Folge der geschätzt fünfte Neuaufbau in drei Jahren…
Ich wünsche euch noch viel Spaß mit eurer Baustelle, produktiv kann man das nicht einsetzen.

Mfg
Rolf

The version you installed is not yet intended to be used in a production environment…
Installing 4.0.0M1 requires Java 17 to be installed which seems not to be the case for your environment.

4 Likes

dear I upgrade OH from 3.4 to 4 milestone
first i upgrade java version

result oh java and javac version are the following

OH:~$ java --version
java 17.0.6 2023-01-17 LTS
Java™ SE Runtime Environment (build 17.0.6+9-LTS-190)
Java HotSpot™ 64-Bit Server VM (build 17.0.6+9-LTS-190, mixed mode, sharing)
OH:~$

OH:~$ javac --version
javac 17.0.6

the result of echo $JAVA_HOME is

/usr/lib/jvm/jdk-17/bin/

the log reports

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.openhab.core/4.0.0.M1: missing requirement [org.openhab.core/4.0.0.M1] osgi.ee; filter:=“(&(osgi.ee=JavaSE)(version=17))”

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.0.jar:?]

… 12 more

I have changed also setted the path with the following commands

sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/YOUR_JAVA_VERSION/bin/java 1
sudo update-alternatives --install /usr/bin/java javac /usr/lib/jvm/YOUR_JAVA_VERSION/bin/javac 1

but i noticed that if i reboot the system, after the $JAVA_HOME returns the old one related to zulu11
where I’m wrong?

I have no problem because I have anoter VM with OH4 latest snapshot that is running wonderful without error, but i prefer to mantain also a second one in case that the one with the latest snapshot crashes

Looks like the environment variable is set in a profile which is sourced during login.
Check the if it is defined in the users home directory in .* files or files located in /etc/.

Try to find the file using:

find ${HOME} /etc -type f -exec grep -l JAVA_HOME {} \; 2>/dev/null

This will look into the logged in user’s home directory and in /etc/.

Hello, I have suddenly the same Problem, but I’m not sure why…
I did today the usual update with openhabian-config and after that I got that problems running openhab, I got the same problem with apache as written above.
I’m on the OH3 stable branch:


but I have absolutely no Idea what it means with “custom version” or “some other version”, I always did updates through openhabian-config and I always was on this branch.
Before the Update today morning, I was on the version 3.4.2 but after the update, it seems I’m on the version 4.0.0:
grafik
How could that happen? How can I return back to latest 3.4.2?
I don’t think that I can run 4.0.0, as I have still Debian 10 (buster) and OpenJDK 17 is not able to install on this system:

In my openhab.list I have:
grafik
Is this right or wrong for OH3.4.2?
Thanks for help!

It means you are not running the release version of openHABian. You are running some other branch. If you want to keep up with development of openHABian, I recommend sticking with “release”.

You are configured to run the latest release of OH. OH 4.0 was release this weekend. If you did not want to upgrade when OH releases new versions you would need to fix the version number. I don’t know if that can be done in openHABian which is always going to give you the latest version of whatever branch of OH you are running: release, testing, snapshot.

sudo apt-mark hold openhab-3.4.2 
sudo apt upgrade

I think that’s how it’s listed. You should do an apt-cache search openhab if that doesn’t work.

That does seem to be the case for most.

It’s definitely right. It’s just 3.4.2 isn’t the latest release any more. It’s been replaced (three times over, the latest OH 3 is 3.4.4, and as I said OH 4.0.0 was release this weekend).

3 Likes