Closed dwrobel closed 1 year ago
I extracted the Exec Binding JAR from the KAR in the RPM and the manifest is in it. So it is probably some local hiccup on your system. Maybe clean the cache or remove/install the openhab-addons package again?
Maybe clean the cache or remove/install the openhab-addons package again?
That was actually a complete fresh installation (including operating system), so no leftovers.
Moreover, rpm confirms that the installation is correct (file is intact):
# rpm -Va openhab-addons-4.0.0-1.noarch
#
For the record:
# rpm -ql openhab-addons
/usr/share/openhab/addons/openhab-addons-4.0.0.kar
# sha256sum /usr/share/openhab/addons/openhab-addons-4.0.0.kar
fec9aac5b6add6bcd388c9174ccf8bb402714bbeeef983e9f9a9aea7c3d38464 /usr/share/openhab/addons/openhab-addons-4.0.0.kar
# rpm -qv java-17-openjdk-headless
java-17-openjdk-headless-17.0.7.0.7-5.fc38.aarch64
I've tried to reproduce it, but I couldn't. So, I'll close it. I'm sorry for the trouble.
It looks like I can't close it.
Perhaps something went wrong while Karaf was extracting the add-ons from the KAR file.
I'm trying to do a fresh installation of
openhab-4.0.0
on a fully updated Fedora 38 Server on raspberry Pi 4 (4GB).The installation is done using ansible playbook and the scenario is as follows (the relevant part):
install openhab dependencies (e.g. openjdk-17, etc..)
install openhab and openhab-addons rpm packages
provision openhab (by installing all configuration in /etc/openhab), see addons.cfg:
start openhab.service
/var/log/openhab/openhab.log contains:
journalctl -b -u openhab excerpt:
FYI, similar worked for me last week for version
3.4.4
.Your Environment
Fully updated FedoraServer 38 on aarch64 architecture: