I can’t read the error log, print to small.
You can alway’s roll back to an earlier stable version of OH with.
sudo apt-get update
apt-cache showpkg openhab2
Pick the version you want then fill in the xxxx with the version number.
sudo apt-get install openhab2=2.xxxx
Back in business. Thanks. For whatever reason I already went back earlier today without success. Now it worked after reinstalling all bindings.
@frankie.delure Glad to see your back up and running.
Sometimes when changing versions you have to delete /var/lib/openhab2/config/org/openhab/addons.config and restart so OH can install everything from a clean slate.
If you would please mark the topic solved by clicking the square box (lower right corner) on the post that provided the solution. This helps other’s with a similar issue find a quick solution.
Thanks
My commands to Force reinstall were:
sudo apt-get -o Dpkg::Options::="--force-confask" -o Dpkg::Options::="--force-confmiss" install --reinstall openhab2=2.5.0~S1512-1
sudo apt-get -o Dpkg::Options::="--force-confask" -o Dpkg::Options::="--force-confmiss" install --reinstall openhab2-addons=2.5.0~S1512-1
I also had to get back to the #1512 addons. Otherwise the error still occurred.
#1519 doesn’t show this error anymore.
I had the same problems after OH2 build #1518 upgrade - no addons and scheduler errors on startup. I’ve stopped OH2, removed /var/lib/openhab2/config/org/openhab/addons.config and upgraded OH2 (yesterday #1521) with no issues and additional commands.
Firstly this is my first post so I would like to say thank you to all that contribute, it has helped me immensely. I have been playing around as a noob for some time now, I have a very limited coding background and wanted to put something here as someone starting out might trip up where I did.
This all started when I updated my network adaptor (/etc/network/interfaces) and failed to add dns-nameservers. The Pi was fine on my network internally but obviously was powerless when trying to discover the outside world, page 1 mistake on my part for not checking this 1st when noticing my cloud service had gone wonky. Anyway before I discovered this I had managed to break everything else and couldn’t install any releases. Once I fixed the DNS I could roll version and restore a backup.
If using ZRAM, RTFM! I didn’t and it cost me a day. When rolling back/upgrading/cleaning the cache on ZRAM.
My file system was forced to Read-Only in the end “EXT4-fs error (device zram1): ext4_journal_check_start:61: Detected aborted journal” but you can still follow these steps to recover.
sudo systemctl stop openhab2sudo rm -rf /var/lib/openhab2/tmp/* /var/lib/openhab2/tmp/.??* /var/lib/openhab2/cache/*/var/lib/openhab2/cache and …/tmp): sudo systemctl stop zram-configsudo systemctl start openhab2sudo systemctl stop openhab2/etc/ztab and assign more RAM to the affected share while you can.sudo systemctl start zram-configsudo systemctl start openhab2I hope this saves someone some time
VIVA OH!
Thanks for publicly admitting. Most people aren’t that bold.
BTW there’s an upcoming change in openHABian, ZRAM will no longer include the cache but swap, logs and /var/lib/openhab2/persistence only.
You can also edit /etc/ztab to accomplish that yourself.
PS: and it’s actually If using OH, RTFM!
Thanks Markus, I’m from an engineering background so mistakes are sometimes required to learn. mistake>learn>move_on, the more we admit the quicker development happens!
Thanks for your work on ZRAM with OH I have been using it since the start of my OH quest with no problems (only on my part). Nice to hear about changes I will continue my exploration.
I also had this read-only filesystem error and failures from core.karaf saying it wouldn’t install bindings and Paper UI wouldn’t start, etc…all kinds of problems. Was going to revert to backup but turns out the overall OS update I did via openhab-config turned ZRAM OFF. Simple fix to turn it back on and reboot but damn, took me a few hours to play around until i realized in the release notes ZRAM is OPTIONAL by default.
D’OH!
Version I use
I use Openhab 2.5.12.-1 and all was working perfectly but now my error log is full of
Error I have
[ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-snmp1, openhab-action-mqtt, openhab-binding-mqtt1’
And MQTT binding is not working any longer…
=> I still see on the Panel that my mqtt-devices are turned on/off but no MQTT message is sent out
Also homematic binding is not working
What I tried
What is remote = set to in addons.cfg in /etc/openhab2/services/ is it set to false resp. put into a comment ? As far as I can see version 1 bindings are not included in the openhab-addons-2.5.12.kar file.
addons.cfg I put in:
remote = false
I red somewhere this needs to be added
Can it be that mqtt v1 binding is not in the .kar file I downloaded?
Thanks Wolfgang
So anyone knows how I can add the 1 bindings to the kar files? To use a “stable” version that is not stable and moving is kinda useless… 
The legacy add-ons are part of this openhab-addons-legacy-2.5.12.kar file.
Just add it to the /addons directory like that other KAR file. 
yeeee! many many thanks!
For others having the same issues
In /etc/openhab2/services/addons.cfg change remote = false
=> Check log file and see how the bindings get installed
Thanks for trying, but this is till not working (but thanks)
Seems I have a requirement for a few additional jar files that I used before (org.openhab.binding.lightwaverf-1.13.0-SNAPSHOT.jar) which is critical to my setup.
Is there a how-to for injecting this into the jar file?
I am running under docker on Ubuntu
Thanks - I already have this jar.
Does it need to be added into the jar file somehow? I used to download all the plugins normally and only needed the LightwaveRF jar file in my adding directory.
Since adding can’t come directly anymore, I tried also:
adding the kar file to the adding folder
Setting remote = false in addons.cfg
Clearing the cache and restarting
I still get :
==> /log/openhab.log <==
11-27 17:50:08.924 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-exec, openhab-misc-restdocs, openhab-misc-openhabcloud, openhab-binding-network, openhab-persistence-influxdb, openhab-binding-amazonechocontrol, openhab-misc-hueemulation, openhab-ui-habpanel, openhab-action-pushover, openhab-binding-mqtt1, openhab-ui-restdocs, openhab-action-prowl, openhab-ui-classic, openhab-binding-kodi, openhab-binding-systeminfo, openhab-ui-paper, openhab-binding-http1, openhab-binding-modbus, openhab-misc-market, openhab-binding-spotify, openhab-transformation-regex, openhab-binding-yamahareceiver, openhab-transformation-jsonpath, openhab-binding-mihome, openhab-ui-basic, openhab-binding-ntp, openhab-binding-astro, openhab-binding-globalcache, openhab-binding-onkyo’: Error:
Error downloading mvn:org.apache.commons/commons-pool2/2.4.3
11-27 17:51:09.061 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-exec, openhab-misc-restdocs, openhab-misc-openhabcloud, openhab-binding-network, openhab-persistence-influxdb, openhab-binding-amazonechocontrol, openhab-misc-hueemulation, openhab-ui-habpanel, openhab-action-pushover, openhab-binding-mqtt1, openhab-ui-restdocs, openhab-action-prowl, openhab-ui-classic, openhab-binding-kodi, openhab-binding-systeminfo, openhab-ui-paper, openhab-binding-http1, openhab-binding-modbus, openhab-misc-market, openhab-binding-spotify, openhab-transformation-regex, openhab-binding-yamahareceiver, openhab-transformation-jsonpath, openhab-binding-mihome, openhab-ui-basic, openhab-binding-ntp, openhab-binding-astro, openhab-binding-globalcache, openhab-binding-onkyo’: Error:
Error downloading mvn:org.apache.commons/commons-pool2/2.4.3
kar files contain a collection ( like an archive ) of jar files.
So kar files do not need to be injected into kar files.
As far as I understand your situation you need to put two kar files into the openhab addons folder ( the normal addons ( like for the exec, modbus, … bindings) , the leagacy addons ( like mqtt1, http1 bindings ) and the version 1 or version 2 bindings that are not contained in the kar files.