Clean rpi install of OH4 failing

  • Platform information:
  • Issue of the topic: I am trying to do a completely clean install of OH4, based on the openHabian image. I flashed the image onto the sd card using Etcher, placed in the RPI, powered on and waited.
    The :8080 website is never reachable.
    Connecting via ssh logs in ok, but it seems that install failed at some point.
###############################################################################
###############  openhabian  ##################################################
###############################################################################
##        Ip = 192.168.1.151
##   Release = Raspbian GNU/Linux 11 (bullseye)
##    Kernel = Linux 6.1.21-v8+
##  Platform = Raspberry Pi 4 Model B Rev 1.1
##    Uptime = 0 day(s). 1:1:21
## CPU Usage = 0% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
##  CPU Load = 1m: 0.15, 5m: 0.03, 15m: 0.01
##    Memory = Free: 3.48GB (93%), Used: 0.27GB (7%), Total: 3.75GB
##      Swap = Free: 2.99GB (100%), Used: 0.00GB (0%), Total: 2.99GB
##      Root = Free: 23.88GB (86%), Used: 3.87GB (14%), Total: 28.98GB
##   Updates = 0 apt updates available.
##  Sessions = 1 session(s)
## Processes = 125 running processes of 32768 maximum processes
###############################################################################
sed: can't read /var/lib/openhab/etc/version.properties: No such file or directory
sed: can't read /var/lib/openhab/etc/version.properties: No such file or directory

                          _   _     _     ____   _               
  ___   ___   ___   ___  | | | |   / \   | __ ) (_)  ____   ___  
 / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \ | | / _  \ / _ \ 
| (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )| || (_) || | | |
 \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/ |_| \__|_||_| | |
      |_|                  openHAB  -           

Looking for a place to get started? Check out 'sudo openhabian-config' and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhabian:8080
To interact with openHAB on the command line, execute: 'openhab-cli --help'

openhab-cli does not seem to exist, or is on the path for the openhabian user.

Looking at the setup log /boot/first-boot.log, the first sign of trouble is with:

ESC[90;01m$ apt-get install --yes -o DPkg::Lock::Timeout=60 openjdk-17-jre-headless ESC[39;49;00m
+ apt-get install --yes -o DPkg::Lock::Timeout=60 openjdk-17-jre-headless
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  ca-certificates-java java-common libavahi-client3 libcups2 libgraphite2-3
  libharfbuzz0b
Suggested packages:
  default-jre cups-common fonts-dejavu-extra fonts-ipafont-gothic
  fonts-ipafont-mincho fonts-wqy-microhei | fonts-wqy-zenhei fonts-indic
The following NEW packages will be installed:
  ca-certificates-java java-common libavahi-client3 libcups2 libgraphite2-3
  libharfbuzz0b openjdk-17-jre-headless
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/42.5 MB of archives.
After this operation, 178 MB of additional disk space will be used.
Selecting previously unselected package java-common.
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 50153 files and directories currently installed.)
Preparing to unpack .../0-java-common_0.72_all.deb ...
Unpacking java-common (0.72) ...
Selecting previously unselected package libavahi-client3:armhf.
Preparing to unpack .../1-libavahi-client3_0.8-5+deb11u2_armhf.deb ...
Unpacking libavahi-client3:armhf (0.8-5+deb11u2) ...
Selecting previously unselected package libcups2:armhf.
Preparing to unpack .../2-libcups2_2.3.3op2-3+deb11u2_armhf.deb ...
Unpacking libcups2:armhf (2.3.3op2-3+deb11u2) ...
Selecting previously unselected package libgraphite2-3:armhf.
Preparing to unpack .../3-libgraphite2-3_1.3.14-1_armhf.deb ...
Unpacking libgraphite2-3:armhf (1.3.14-1) ...
Selecting previously unselected package libharfbuzz0b:armhf.
Preparing to unpack .../4-libharfbuzz0b_2.7.4-1_armhf.deb ...
Unpacking libharfbuzz0b:armhf (2.7.4-1) ...
Selecting previously unselected package openjdk-17-jre-headless:armhf.
Preparing to unpack .../5-openjdk-17-jre-headless_1%3a17.0.7+7-1~deb11u1+rpt1_armhf.deb ...
Unpacking openjdk-17-jre-headless:armhf (1:17.0.7+7-1~deb11u1+rpt1) ...
Selecting previously unselected package ca-certificates-java.
Preparing to unpack .../6-ca-certificates-java_20190909_all.deb ...
Unpacking ca-certificates-java (20190909) ...
Setting up libgraphite2-3:armhf (1.3.14-1) ...
Setting up java-common (0.72) ...
Setting up libharfbuzz0b:armhf (2.7.4-1) ...
Setting up libavahi-client3:armhf (0.8-5+deb11u2) ...
Setting up libcups2:armhf (2.3.3op2-3+deb11u2) ...
Setting up ca-certificates-java (20190909) ...
head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory
Exception in thread "main" java.lang.InternalError: Error loading java.security file
        at java.base/java.security.Security.initialize(Security.java:106)
        at java.base/java.security.Security$1.run(Security.java:84)
        at java.base/java.security.Security$1.run(Security.java:82)
        at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
        at java.base/java.security.Security.<clinit>(Security.java:82)
        at java.base/sun.security.jca.ProviderList.<init>(ProviderList.java:178)
        at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96)
        at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94)
        at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
        at java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93)
        at java.base/sun.security.jca.Providers.<clinit>(Providers.java:55)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156)
        at java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193)
        at org.debian.security.KeyStoreHandler.<init>(KeyStoreHandler.java:50)
        at org.debian.security.UpdateCertificates.<init>(UpdateCertificates.java:65)
        at org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51)
dpkg: error processing package ca-certificates-java (--configure):
 installed ca-certificates-java package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of openjdk-17-jre-headless:armhf:
 openjdk-17-jre-headless:armhf depends on ca-certificates-java (>= 20190405~); however:
  Package ca-certificates-java is not configured yet.

dpkg: error processing package openjdk-17-jre-headless:armhf (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for ca-certificates (20210119) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

/etc/ca-certificates/update.d/jks-keystore: 82: java: not found
E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
done.
Errors were encountered while processing:
 ca-certificates-java
 openjdk-17-jre-headless:armhf
Updating FireMotD available updates count ... 
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ return 100
+ echo FAILED
FAILED

later

+ rm -f /etc/apt/sources.list.d/openhab.list
+ echo 'deb [signed-by=/usr/share/keyrings/openhab.gpg] https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable main'
++ timestamp
++ printf '%(%F_%T_%Z)T\n' -1
+ echo -n '2023-08-13_07:33:05_CEST [openHABian] Installing selected openHAB version... '
2023-08-13_07:33:05_CEST [openHABian] Installing selected openHAB version... + apt-get clean --yes -o DPkg::Lock::Timeout=60
+ cond_redirect apt-get update
+ [[ -n '' ]]
+ echo -e '\n\033[90;01m$ apt-get update \033[39;49;00m'

ESC[90;01m$ apt-get update ESC[39;49;00m
+ apt-get update
Hit:1 http://davesteele.github.io/comitup/repo comitup InRelease
Hit:2 https://deb.nodesource.com/node_18.x bullseye InRelease
Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease
Reading package lists...
+ return 0
++ apt-cache madison openhab
++ head -n 1
++ xargs
++ cut '-d|' -f2
+ openhabVersion=4.0.1-1
+ [[ -n 4.0.1-1 ]]
+ installVersion='openhab=4.0.1-1 openhab-addons=4.0.1-1'
+ cond_redirect apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout=60 --option Dpkg::Options::=--force-confnew 'openhab=4.0.1-1 openhab-addons=4.0.1-1'
+ [[ -n '' ]]
+ echo -e '\n\033[90;01m$ apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout=60 --option Dpkg::Options::=--force-confnew openhab=4.0.1-1 openhab-addons=4.0.1-1 \033[39;49;00m'

ESC[90;01m$ apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout=60 --option Dpkg::Options::=--force-confnew openhab=4.0.1-1 openhab-addons=4.0.1-1 ESC[39;49;00m
+ apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout=60 --option Dpkg::Options::=--force-confnew 'openhab=4.0.1-1 openhab-addons=4.0.1-1'
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package openhab=4.0.1-1 openhab-addons
E: Couldn't find any package by glob 'openhab=4.0.1-1 openhab-addons'
E: Couldn't find any package by regex 'openhab=4.0.1-1 openhab-addons'
+ return 100
+ echo FAILED
FAILED

when did you try? There was a fix today.
Retry, eventually.

I tried again on Sunday and it had been fixed.