[SOLVED] First trial of OH3 on rPi4 fails from fresh OpenHABian image (with possible solution)

I think this might actually be a bug report, as I’ve done so very little beyond install a stock image on stock system.

I thought I’d give OH3 a trial as it’s been stable for a while now. I have an rPi4 4GB and I imaged a brand new 32GB SanDisk “Max Endurance” uSD card with the 32-bit release of openHABian v1.6.4

as per the documentation (sha256sum of the uncompressed image is 4d639aebe7061917e7ccb5ecbbe4f95ddfd53778e01d806effbf3a237c3df4df). I booted the board up, and left it alone while I ate dinner.

Watching the webpage during post-boot auto-setup shows a few errors, which I’ve highlighted below (this is a result of $(grep -C2 FAILED first-boot.txt)):

2021-01-11_13:09:24_GMT [openHABian] Waiting for dpkg/apt to get ready... OK
2021-05-05_21:10:03_BST [openHABian] Updating repositories and upgrading installed packages... OK
2021-05-05_21:10:03_BST [openHABian] Installing git package... FAILED
2021-05-05_21:10:03_BST [openHABian] Updating myself from https://github.com/openhab/openhabian, main branch... OK
2021-05-05_21:10:03_BST [openHABian] Starting execution of 'openhabian-config unattended'... OK
2021-05-05_22:12:52_CEST [openHABian] tailscale VPN installation... SKIPPED (no preauthkey defined)
2021-05-05_22:12:52_CEST [openHABian] Applying miscellaneous system settings... realpath: '': No such file or directory
FAILED (setcap java)
2021-05-05_22:12:52_CEST [openHABian] Downloading FireMotD... OK
2021-05-05_22:13:53_CEST [openHABian] Installing Java Zulu CEK to enable unlimited cipher strength... OK
2021-05-05_22:13:53_CEST [openHABian] Beginning install of latest openHAB3 release (stable)... OK
2021-05-05_22:13:54_CEST [openHABian] Adding required keys to apt... FAILED
2021-05-05_22:13:54_CEST [openHABian] Adding openHAB syntax to vim editor... OK
2021-05-05_22:13:55_CEST [openHABian] Adding openHAB syntax to nano editor... OK
2021-05-05_22:14:34_CEST [openHABian] Setting up Samba network shares... OK
2021-05-05_22:14:35_CEST [openHABian] Setting up Samba service... OK
2021-05-05_22:14:36_CEST [openHABian] Applying file permissions recommendations... FAILED (please execute after openHAB is installed)
2021-05-05_22:14:36_CEST [openHABian] Installing Frontail prerequsites (NodeJS)... FAILED

The failure to set permissions is, I believe, probably the important one. After the rPi rebooted, I tried accessing http://IP:8080 but it wasn’t working (connection refused, TCP port 8080 closed).

Believing this was a permissions-related problem, I logged in via ssh, ran openhabian-config, selected OpenHAB3-stable and then forced a re-install of OpenHAB. After that, OpenHAB3 still wasn’t accessible via port 8080, so I ran openhabian-config’s “Apply Improvements/Fix Permissions” and that seemed to sort it.

Am I right in thinking this should’ve worked “out of the box”?

Edit: Here’s the status of trying to start the openhab.service from an earlier attempt, which I believe also points to a permissions issue:

-- A stop job for unit openhab.service has finished.
-- 
-- The job identifier is 12086 and the job result is done.
May 05 21:30:13 openhabian systemd[1]: Started openHAB instance, reachable at http://openhabian:8080.
-- Subject: A start job for unit openhab.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit openhab.service has finished successfully.
-- 
-- The job identifier is 12086.
May 05 21:30:15 openhabian karaf[24686]: !SESSION 2021-05-05 21:30:15.726 -----------------------------------------------
May 05 21:30:15 openhabian karaf[24686]: eclipse.buildId=unknown
May 05 21:30:15 openhabian karaf[24686]: java.version=11.0.11
May 05 21:30:15 openhabian karaf[24686]: java.vendor=Azul Systems, Inc.
May 05 21:30:15 openhabian karaf[24686]: BootLoader constants: OS=linux, ARCH=aarch64, WS=gtk, NL=en_GB
May 05 21:30:15 openhabian karaf[24686]: !ENTRY org.eclipse.osgi 4 0 2021-05-05 21:30:15.809
May 05 21:30:15 openhabian karaf[24686]: !MESSAGE Error reading configuration: Unable to create lock manager.
May 05 21:30:15 openhabian karaf[24686]: !STACK 0
May 05 21:30:15 openhabian karaf[24686]: java.io.IOException: Unable to create lock manager.
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.storagemanager.StorageManager.open(StorageManager.java:698)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.storage.Storage.getChildStorageManager(Storage.java:1776)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.storage.Storage.getInfoInputStream(Storage.java:1793)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.storage.Storage.<init>(Storage.java:132)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:85)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:68)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31)
May 05 21:30:15 openhabian karaf[24686]:         at org.eclipse.osgi.launch.EquinoxFactory.newFramework(EquinoxFactory.java:24)
May 05 21:30:15 openhabian karaf[24686]:         at org.apache.karaf.main.Main.launch(Main.java:256)
May 05 21:30:15 openhabian karaf[24686]:         at org.apache.karaf.main.Main.main(Main.java:178)
May 05 21:30:15 openhabian systemd[1]: openhab.service: Main process exited, code=exited, status=255/EXCEPTION

Yes, more or less. The fix permissions routine is executed as part of the unattended install, too.

Please reinstall and provide a debug log this time else it’s guessing in the dark.

Ok, re-imaged, set debug=maximum, and the same symptoms occurred - the first-boot file is attached; are the terminal control cards normal and expected?
first-boot.log (173.8 KB)

I ‘think’ it has to do with the bintray sunset:

E: Failed to fetch https://dl.bintray.com/openhab/apt-repo2/dists/stable/InRelease  403  Forbidden [IP: 35.156.120.218 443]
E: The repository 'https://dl.bintray.com/openhab/apt-repo2 stable InRelease' is no longer signed.

which could make sense, since bintray was shutdown at may and the openHABian image is from march. Can you access openhabian-config and let it perform an update and fix the bintray problem?
Afterwards you should be able to install oh from openhabian-config.

Yeah, I said in the first post I managed to fix it with openhabian-config; my point was more that the release-tagged image didn’t appear to work out-of-the-box, which I think is likely to confuse new users looking to take the “easy route” by getting an rPi and using the image.

Markus already did create an issue for that, so thanks for reporting :wink:

1 Like

Please install this Release openHABian v1.6.5 · openhab/openhabian · GitHub and confirm it’s working.

2 Likes

Confirmed. Fixed, and OpenHAB is accessible on port 8080.

Thanks Markus!

Markus, that was supersonic bugfixing.
Thanks a lot for you hard work and effort!

Yeah, agreed. Thanks very much @mstormi for the extremely rapid response!