Upgrade has killed my install - desperate times

I’m running an install deployed on Ubuntu via apt-get.

All was wonderful and my config is relatively involved (circa 13 bindings and 100ish managed items)

But I’ve run an update and the world has fallen apart.
I am seeing this in the log:

14:30:03.659 [INFO ] [.internal.service.FeaturesServiceImpl] - Adding features: openhab-binding-nest/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-network/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-misc-hueemulation/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-ui-classic/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-kodi/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-systeminfo/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-ui-paper/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-http1/[1.12.0.SNAPSHOT,1.12.0.SNAPSHOT], openhab-binding-amazondashbutton/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-misc-ruleengine/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-yamahareceiver/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-mihome/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-astro/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-globalcache/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT], openhab-binding-onkyo/[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT]
14:30:03.697 [WARN ] [.url.mvn.internal.AetherBasedResolver] - Error resolving artifact org.openhab.binding:org.openhab.binding.systeminfo:jar:2.3.0-SNAPSHOT: [Could not find artifact org.openhab.binding:org.openhab.binding.systeminfo:jar:2.3.0-SNAPSHOT]
java.io.IOException: Error resolving artifact org.openhab.binding:org.openhab.binding.systeminfo:jar:2.3.0-SNAPSHOT: [Could not find artifact org.openhab.binding:org.openhab.binding.systeminfo:jar:2.3.0-SNAPSHOT]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:720) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47) [9:org.apache.karaf.features.core:4.1.3]
at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60) [9:org.apache.karaf.features.core:4.1.3]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
Suppressed: shaded.org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.openhab.binding:org.openhab.binding.systeminfo:jar:2.3.0-SNAPSHOT
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:434) [4:org.ops4j.pax.url.mvn:2.5.3]
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) [4:org.ops4j.pax.url.mvn:2.5.3]
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) [4:org.ops4j.pax.url.mvn:2.5.3]
at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:705) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567) [4:org.ops4j.pax.url.mvn:2.5.3]
at org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47) [9:org.apache.karaf.features.core:4.1.3]
at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60) [9:org.apache.karaf.features.core:4.1.3]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Error resolving artifact org.openhab.binding:org.openhab.binding.systeminfo:jar:2.3.0-SNAPSHOT
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) ~[?:?]
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) ~[?:?]
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) ~[?:?]
at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) ~[?:?]
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:705) ~[?:?]
… 12 more
14:30:03.705 [ERROR] [.core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-nest, openhab-binding-network, openhab-action-mqtt", openhab-misc-“restdocs, openhab-misc-hueemulation, openhab-ui-“basic, openhab-action-”, openhab-ui-habpanel”, openhab-ui-classic, openhab-binding-kodi, openhab-binding-mqtt1", openhab-binding-systeminfo, openhab-ui-paper, openhab-binding-http1, openhab-transformation-map", openhab-binding-amazondashbutton, openhab-transformation-“jsonpath, openhab-misc-ruleengine, openhab-binding-yamahareceiver, openhab-binding-mihome, openhab-misc-openhabcloud”, openhab-persistence-“mysql”, openhab-binding-astro, openhab-binding-globalcache, openhab-binding-", openhab-binding-onkyo’: Error:
Error downloading mvn:org.openhab.binding/org.openhab.binding.systeminfo/2.3.0-SNAPSHOT

Can anyone point me in the right direction - pretty please.

Sorry guys,

Forgot to mention I had already done this.
For now I have rolled back to 2.2 and am up and running - I have taken note and in future will include what I have already tried.

Tbh - my hardware is getting long in the tooth now and I probably have too many legacy / unofficial binding knocking about (lightwaverf / yeelight etc)

Thanks for responding and apologies for lack of info - have a great weekend

Hi,

I’ve got a very similar issue since yesterday evening, after I deleted my openhab/userdata directory.
I’m running OH2.2.0 in a docker environment and had some issues with my homematic binding, which I could mitigate by deleting the openhab/userdata directory when my thermostats stopped working with openhab from time to time.

This time openhab is not able to acquire the bindings, my error message mirror the one @bulletprooffool shows above.

==> /log/openhab2/logs/openhab.log <==
2018-01-06 11:12:08.629 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-hue, openhab-binding-yahooweather, openhab-persistence-influxdb, openhab-binding-weather1, openhab-ui-habpanel, openhab-persistence-mysql, openhab-transformation-regex, openhab-binding-yamahareceiver, openhab-binding-mqtt1, openhab-ui-basic, openhab-misc-homekit, openhab-binding-fritzboxtr0641, openhab-binding-astro, openhab-binding-icloud, openhab-ui-habmin, openhab-binding-homematic, openhab-ui-paper’: Error:
Error downloading mvn:org.openhab.io/org.openhab.io.transport.mqtt/1.11.0
Error downloading mvn:org.openhab.binding/org.openhab.binding.mqtt/1.11.0

The same configuration worked before, so it seems to me that the repositories are not available as they usually are.

Similar threads have come up since yesterday evening:


Does anybody have an idea what can cause this?
I’m pretty sure that I did not change anything since the last successful startup of my docker environment and this one…

Kind regards,
Simon

I found that despite rolling back, a few bindings still didn’t re-install (mqtt) - also, my persistence bindings (MySQL)

Simon - try till back and clear cache - then revisit your bindings (I just use Karaf or paperui for this)

The roll back did the trick

@bulletprooffool
Can you give a little bit more information how to clear the cache?

Hi Eugene,

You’ll need to stop the openhab service
Once you have done this, simply delete the contents of etc anc cache folders.

I have an apt- get install - in my case they are at:
/var/lib/openhab2/cache
and
/var/lib/openhab2/tmp

so from the cmdline I go sudo rm -R /var/lib/openhab2/tmp/*
or somehtingl like that.
If you have a GUI - just delete them.

Further to this - I am still getting the following every minute:

13:12:02.611 [ERROR] [.core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-package-"standard"': No matching features for openhab-package-"standard"/0.0.0

I have however just noticed that my addons.cfg has gone a but weird and looks like this:

package = "standard"
ui = \"basic,classic,paper,habpanel\",basic,habpanel
misc = "restdocs,hueemulation,ruleengine,openhabcloud"
legacy = B"true"
remote = B"true"
binding = \",http1,onkyo,globalcache,amazondashbutton,systeminfo,yamahareceiver,astro,kodi,network,mihome,nest,mqtt1\",mqtt1
persistence = \"mysql\",mqtt,mysql
action = ",mqtt"
transformation = \"jsonpath,map\",jsonpath,map

I’m about to clean this up - will feed back.

Right - this bug:

13:12:02.611 [ERROR] [.core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-package-"standard"': No matching features for openhab-package-"standard"/0.0.0

Is now fixed.
I am unsure where the extra punctuation came from. I think the initial failed install, followed by re-install of binding that were already installed, caused some punctuation and duplication of records in addons.cfg.

Hope this helps someone.

Here is my revised addons.cfg:

package = standard
ui = basic,classic,paper,habpanel
misc = restdocs,hueemulation,ruleengine,openhabcloud
legacy = true
remote = true
binding = http1,onkyo,globalcache,amazondashbutton,systeminfo,yamahareceiver,astro,kodi,network,mihome,nest,mqtt1
persistence = mysql
action = mqtt
transformation = jsonpath,map

Hi!
My addons.config looks messed up as well, as do all the other .config-files, the files look the same as yours do.
I remember an issue related to this, but had no time searching in Github for it.
Cleaning it up does not help me, as I’m configuring my openhab via the configuration files (addons.cfg et al) and openhab seems to update the .config-files at every startup…
Weird. I was sure that I did not change anything between the last startups and I now run into this issue with an installation, which was very stable and fun before.
I’ll try my best to make it work again. Maybe somebody has an idea?

Kind regards,
Simon

I found the issue!
Thanks to everybody for your help and ideas.

In the end it was my own fault and had to do with a seemingly unrelated change in my network.
I installed a pi-hole DNS server recently and got everything up and running again. I had not thought about my NUC server’s DHCP lease, which was only updated after a reboot on Friday.
Obviously the installation of bindings does not work behind the pi-hole. I did not check why this is yet, just changed the DNS for the NUC and everything works again.

Thanks again to everyone trying to help out!

Does anybody have some experience with the pi-hole and can offer advice on how to configure it correctly to serve the binding installation correctly?

I got a similar log file to the OP in this thread. My addons.config file is fine though.

I can’t remember quite what I did but my openHAB stopped working again (I put everything on an SSD last night and it was fine) but I did an upgrade then it wouldn’t start and I did a cache clear etc etc and got a log with this version:

openHAB Distribution Version Information
----------------------------------------
build-no        : Build #1188
online-repo     : https://openhab.jfrog.io/openhab/online-repo-snapshot/2.3

Repository        Version
----------------------------------------
openhab-distro  : 2.3.0-SNAPSHOT
smarthome       : 0.10.0-SNAPSHOT
openhab-core    : 2.3.0-SNAPSHOT
openhab1-addons : 1.12.0-SNAPSHOT
openhab2-addons : 2.3.0-SNAPSHOT
karaf           : 4.1.3
[09:57:18] root@openHABianPi:/home/openhabian#

log:

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) ~[?:?]
	at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) ~[?:?]
	at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:705) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:557) ~[?:?]
	at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123) ~[?:?]
	at java.net.URL.openStream(URL.java:1045) ~[?:?]
	at org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:86) ~[?:?]
	... 12 more

I then rolled back to the last stable release (openHAB 2.2.0-1 (Build #1188)
) via openhabian config and after a restart, I get the following and nothing else at all:

2018-01-24 10:07:38.995 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:07:50.992 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:07:52.043 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:07:57.308 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:06.728 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:17.093 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:27.441 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:37.807 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:48.149 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:49.265 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:08:58.475 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:09:08.855 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:09:10.001 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:09:19.411 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:09:29.751 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:09:40.194 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:09:50.594 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:00.944 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:02.231 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:11.601 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:12.640 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:22.021 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:32.368 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:42.742 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:53.107 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:10:54.209 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:03.446 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:13.837 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:24.238 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:34.630 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:44.992 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:46.104 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:11:55.343 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:05.741 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:16.074 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:26.430 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:36.809 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:47.209 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:48.404 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:12:57.831 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:13:08.199 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:13:18.593 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:13:28.996 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:13:39.386 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1
2018-01-24 10:13:40.547 [WARN ] [org.apache.karaf.main.Main          ] - Lock lost. Setting startlevel to 1

Has anyone seen this and got any suggestions other than another clean install and backup?

Thanks!

It’s working again.

sudo apt -y install openhab2=2.2.0-1 --force-yes

(warning: downgrading openhab2 from 2.3.0~20180124001658-1 to 2.2.0-1)

But I don’t know why and it was more ‘poke and hope’ than considered diagnosis.

I couldn’t open the console either.