Error updating to OH4

1

Hello everyone,

when updating to OH4 i get this error:

There was an error or interruption during the execution of "03 | Install openHAB" Please try again. If the error persists, please read /opt/openhabian/docs/openhabian-DEBUG.md or https://github.com/openhab/openhabian/blob/main/docs/openhabian-DEBUG.md how to proceed.

I followed the tips from the github page and got following out of the logfile.

$ apt-get update
+ apt-get update
Get:1 http://davesteele.github.io/comitup/repo comitup InRelease [4,659 B]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:6 https://packages.grafana.com/oss/deb stable InRelease
Hit:7 https://deb.nodesource.com/node_16.x bullseye InRelease
Get:8 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
Hit:9 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
Err:8 https://repos.influxdata.com/debian bullseye InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
Reading package lists... Done
W: GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
E: The repository 'https://repos.influxdata.com/debian bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
+ return 100
+ echo 'FAILED (update apt lists)'
FAILED (update apt lists)
+ return 1
+ '[' 1 -ne 0 ']'
+ whiptail --msgbox 'There was an error or interruption during the execution of:\n  "03 | Install openHAB"\n\nPlease try again. If the error persists, please read /opt/openhabian/docs/openhabian-DEBUG.md or https://github.com/openhab/openhabian/blob/main/docs/openhabian-DEBUG.md how to proceed.' 14 80
+ return 0

It seems like the influxDB errors during the update process. I tried so many things already. Always with the same error.

sudo apt-get upgrade
I followed this: Update: Linux Package Signing Key Rotation | InfluxData
rebooted multiple times. I am still getting the same error. When doing sudo apt-get update I get the same error again. This stops me from updating to OH4. Please help :frowning:

2

Doing
sudo nano /etc/apt/sources.list.d/influxdb.list and manually adding

deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian bullseye stable

did the trick. But now i am getting a new error:

$ apt-get update
+ apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Get:3 http://davesteele.github.io/comitup/repo comitup InRelease [4,659 B]
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://packages.grafana.com/oss/deb stable InRelease
Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:7 https://repos.influxdata.com/debian stable InRelease
Hit:8 https://repos.influxdata.com/debian bullseye InRelease
Hit:9 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
Fetched 4,659 B in 2s (2,407 B/s)
Reading package lists... Done
+ return 0
++ apt-cache madison openhab
++ head -n 1
++ cut '-d|' -f2
++ xargs
+ openhabVersion=
+ cond_redirect apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout= --option Dpkg::Options::=--force-confnew openhab= openhab-addons=
+ [[ -n '' ]]
+ echo -e '\n\033[90;01m$ apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout= --option Dpkg::Options::=--force-confnew openhab= openhab-addons= \033[39;49;00m'

$ apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout= --option Dpkg::Options::=--force-confnew openhab= openhab-addons=
+ apt-get install --allow-downgrades --yes -o DPkg::Lock::Timeout= --option Dpkg::Options::=--force-confnew openhab= openhab-addons=
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Version '' for 'openhab' was not found
E: Version '' for 'openhab-addons' was not found
+ return 100
+ echo FAILED
FAILED
+ return 1
+ '[' 1 -ne 0 ']'
+ whiptail --msgbox 'There was an error or interruption during the execution of:\n  "03 | Install openHAB"\n\nPlease try again. If the error persists, please read /opt/openhabian/docs/openhabian-DEBUG.md or https://github.com/openhab/openhabian/blob/main/docs/openhabian-DEBUG.md how to proceed.' 14 80
+ return 0
3

Using menu 40 (openHAB Related) and then menu 41 (openHAB Release) updated my system without any errors.

4

Hey everyone,

I had the same problem: Brocken upgrade process · Issue #1802 · openhab/openhabian · GitHub
As you can see in the log, the upgrade could not fetch the right versions for openhab openhab= openhab-addons= because the repository of openhab is missing. I solved this problem by manually adding the right version to the openhabian script and execute it again.

I don’t know why I got this error, but now the system works.

Regards,
Tim

5

Hi timl

What exactly did you add in which file/script?
I’m not sure where the file is located.

regards
Levin

6

Hey Levin,

/opt/openhabian/functions/openhab.bash

The problem was “openhab_setup” in my case, because the function is called with invalid second parameter, if there is no valid repository configured.
I think I add this after the if-else block and execute the upgrade via openhabian-config again:

introText="Manually..."
successText="..."
repo="deb [signed-by=/usr/share/keyrings/${keyName}.gpg] https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable main"

Regards,
Tim

7

Thank you timl for this.
In the meantime, I tried to update using menu option 40/41 and got a Java Error.
I did a fresh install and restored the config which worked without problems
Unfortunately my inluxdb restore brakes the DB for some reason. After hours of analysis I gave up and accepted to lose my historic data.

8

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.