Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HASS.IO addon upgrade to 6.1.1 error #1487

Closed
andysaab opened this issue Jul 21, 2020 · 45 comments
Closed

HASS.IO addon upgrade to 6.1.1 error #1487

andysaab opened this issue Jul 21, 2020 · 45 comments
Labels
add-on: deconz wontfix

Comments

@andysaab
Copy link

andysaab commented Jul 21, 2020 •
edited
Loading

After upgrade addon got error - deCONZ: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
Deconz error
Restore from backup and work again sucsessefully.
@frenck
Copy link
Member

frenck commented Jul 21, 2020

Could you provide details on your setup? Hardware? 32 or 64 bits?

@andysaab
Copy link
Author

andysaab commented Jul 21, 2020 •
edited
Loading

Thx for your reply, Frenck!
My setup is Xpenology on HP Gen8
image

@ghost
Copy link

ghost commented Jul 21, 2020

same problem her with 6.1.1

@althaus
Copy link

althaus commented Jul 22, 2020

I've got the same error. System is Hassio running on a Synology DS via Docker.

System health is same as andysaab's one besides HA 0.112.4 and Python 3.7.7.

@og9gjz567
Copy link

og9gjz567 commented Jul 23, 2020 •
edited
Loading

I've got the same error. System is Hassio running on a Synology DS via Docker, too.
I'm currently running version 0.112.4 ;)

Is there a quick way to downgrade the deCONZ Add-on?
Edit: Quick downgrade: #1487 (comment)

@omersh82
Copy link

Same error for me, running hassio on Synology DS via docker.

2020-07-23 08:43:01 | stderr | [11:43:00] INFO: �[32mStarting VNC server...�[0m
2020-07-23 08:43:01 | stderr | [11:43:00] INFO: �[32mWaiting for device...�[0m
2020-07-23 08:43:01 | stderr | [08:43:00] INFO: �[32mRunning the deCONZ OTA updater...�[0m
2020-07-23 08:43:01 | stderr | [08:43:00] INFO: �[32mRunning the IKEA OTA updater...�[0m
2020-07-23 08:43:01 | stderr | [08:43:00] INFO: �[32mStarting udevd...�[0m
2020-07-23 08:43:00 | stderr | [08:43:00] INFO: �[32mRunning the OSRAM LEdvance OTA updater...�[0m
2020-07-23 08:43:00 | stdout | [services.d] done.
2020-07-23 08:42:59 | stdout | [services.d] starting services
2020-07-23 08:42:59 | stdout | [cont-init.d] done.
2020-07-23 08:42:59 | stdout | [cont-init.d] vnc.sh: exited 0.
2020-07-23 08:42:59 | stdout | [cont-init.d] vnc.sh: executing...
2020-07-23 08:42:59 | stdout | [cont-init.d] nginx.sh: exited 0.
2020-07-23 08:42:57 | stdout | [cont-init.d] nginx.sh: executing...
2020-07-23 08:42:57 | stdout | [cont-init.d] firmware.sh: exited 0.
2020-07-23 08:42:57 | stderr | [11:42:57] INFO: �[32m�[0m
2020-07-23 08:42:57 | stderr | /usr/bin/GCFFlasher_internal.bin: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
2020-07-23 08:42:56 | stdout | [cont-init.d] firmware.sh: executing...
2020-07-23 08:42:56 | stdout | [cont-init.d] executing container initialization scripts...
2020-07-23 08:42:56 | stdout | [fix-attrs.d] done.
2020-07-23 08:42:56 | stdout | [fix-attrs.d] applying ownership & permissions fixes...
2020-07-23 08:42:56 | stdout | [s6-init] ensuring user provided files have correct perms...exited 0.
2020-07-23 08:42:55 | stdout | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.

Thanks

@jlvandusen
Copy link

jlvandusen commented Jul 24, 2020 •
edited
Loading

I too have the same issue.. infuriating... as this is appears to be broken on delivery.
I am running Synology Docker image on my DS1517+

here is my errors (same as everyone else) - we need a way to revert this image back to last which I believe was 5.3.5.

`

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] firmware.sh: executing...
/usr/bin/GCFFlasher_internal.bin: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
[21:06:37] INFO:
[cont-init.d] firmware.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] vnc.sh: executing...
[cont-init.d] vnc.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[01:06:38] INFO: Running the deCONZ OTA updater...
[01:06:38] INFO: Running the OSRAM LEdvance OTA updater...
[21:06:38] INFO: Waiting for device...
[01:06:38] INFO: Running the IKEA OTA updater...
[01:06:38] INFO: Starting udevd...
[21:06:38] INFO: Starting the deCONZ gateway...
deCONZ: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
`

@jlvandusen
Copy link

I was able to use the snapshots within Synology,
Stopped Redrike+hassio synology package (Im using his package to run hass.io)
image

Stopped Docker
I then found the last good snapshot of my docker folder for hass.io
I restored and overwrote the current folder containing the deconz 6.11 which btw is located under /docker/hass.io/addons/data/core_deconz
(*where docker is the volume where I have the hass.io and other docker containers pointing to)
I then started docker
I went and stopped all hassio containers
I deleted all containers related to hassio
I then removed all images related to hassio
I started fredrike’s synology package - it did its part downloading and re-creating all the primary containers to run homeassistant
Once Home assistant was back up and running
I went into supervisor
I selected deconz
it showed I was originally running 5.3.6
I then went back to docker
downloaded homeassistant/addon_deconz 5.3.6
once downloaded, I mounted it
I named the container addon_core_deconz
I clicked on advance
I set its volume to the below path
/data = /docker/hass.io/addons/data/core_deconz
I did not start it
I went back to homeassistant UI and into supervisor
I then started deconz
It started…
after a few moments my sensors were back online!

@og9gjz567
Copy link

@jlvandusen I Tihink there is a simpler way: I use hassio on Synology Docker, too. I went to the ha supervisor tab and selected one of my last snapshots. There you can choose only to restore deCONZ. After a few minutes my deCONZ was up and running again (5.3.6)

@mpolivanov
Copy link

For those with an old snapshot like me:

docker container rm <id of deconz 6.1.1 container>
docker image rm homeassistant/amd64-addon-deconz:6.1.1 (use --force if necessary)
docker pull homeassistant/amd64-addon-deconz:5.3.6
docker tag homeassistant/amd64-addon-deconz:5.3.6 homeassistant/amd64-addon-deconz:6.1.1

Start addon from HA web interface. It is by far not the cleanest approach, but it works for me

@andysaab
Copy link
Author

For my opinion is an easiest way to restore addon`s functionality - restore ONLY Deconz addon from previous snapshot via Supervisor Snapshots page.
@frenck Is there any news on how to solve this problem?

@frenck
Copy link
Member

frenck commented Jul 24, 2020

As for all the reports mentioned, are you all running supervised on synology?

@ghost
Copy link

ghost commented Jul 24, 2020

hi Frenck, no I have an CentOs with docker on ESX

@omersh82
Copy link

i am running on Synology with hassio on docker

@mpolivanov
Copy link

Synology 716 with hassio package

@andysaab
Copy link
Author

i am running on Synology with hassio on docker too.

@frenck
Copy link
Member

frenck commented Jul 24, 2020 •
edited
Loading

image

The issue occurs on systems that are not supported by the Home Assistant project. We'll look into bypassing this, but even with that in place, please be aware, that your system is actually not suited for running Home Assistant and not suited to run deCONZ as well.

Your Conbee stick will not be able to upgrade firmware for example.

@pvizeli
Copy link
Member

pvizeli commented Jul 24, 2020 •
edited
Loading

The issue is the kernel is to old for the binary ELF.
microsoft/WSL#3023 (comment)

Also reported on other linux distro. There is a workaround to stripe ABI part out of ELF which require this kernel version. We look into to fix that for older kernel to give compatibtle with unsupported systems. However, we strict recommend to read this ADR carfully: https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md

@jlvandusen
Copy link

jlvandusen commented Jul 24, 2020 •
edited
Loading

@jlvandusen I Tihink there is a simpler way: I use hassio on Synology Docker, too. I went to the ha supervisor tab and selected one of my last snapshots. There you can choose only to restore deCONZ. After a few minutes my deCONZ was up and running again (5.3.6)

I would agree - however, I don't snap within HA I snap my volumes at the block level.

@frenck and @pvizeli - the strange part is, I have been updating that firmware several times in this docker environment, I dont think that is 100% the case. There was a event logged when looking on a clean start of deconz that shows the following:
06:45:29:664 GW firmware update not supported on x86 linux headless
Is that related maybe, this latest 6.1.1 does not support linux headless configs?!?! that would be first time I have been unable to update firmware from within HA in docker environment on synology.

@pvizeli pvizeli mentioned this issue Jul 24, 2020
Closed
@pvizeli
Copy link
Member

pvizeli commented Jul 24, 2020

@jlvandusen your system is not supported and looks like the Linux kernel has issues with a new binary ABI level. Means, you will have this issue next time more often. You should run a supported system or freeze what you run and never update again.

@pvizeli
Copy link
Member

pvizeli commented Jul 24, 2020

I close this PR now follow up of:
https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md

All systems with this issue are not supported by us. Feel free to create a fork of this add-on and merge my closed PR to fix it partially. However, all QT builts higher as 5.10 need at least a Linux kernel >= 3.17.

@pvizeli pvizeli closed this as completed Jul 24, 2020
@althaus
Copy link

althaus commented Jul 24, 2020

I understand the decision, but it's a pity as there a many folks out there successfully running HA on a Synology this way. :(

@omersh82
Copy link

Is there a way to revert back even if i don't have a snapshot?

@jlvandusen
Copy link

@pvizeli agreed- I could run THE SUPPORTED HA on Synology without supervision... however having the supervisor is key here though. So I used fredrikes workaround...
You do show support for docker and synology in the installation guides...
https://www.home-assistant.io/docs/installation/docker/

@frenck
Copy link
Member

frenck commented Jul 24, 2020

Our container-based installation (docker guides you linked) does not include the supervisor or add-ons @jlvandusen. The ADR linked above by Pascal shows exactly what is supported, the method by fredrikes to run a Supervised system on a Synology is not supported and will cause issues.

@ghost
Copy link

ghost commented Jul 24, 2020

I have replace my installation from Centos with docker to HassOS and now its working perfect with version 6.1.1

@labaland
Copy link

labaland commented Jul 24, 2020 •
edited
Loading

Synology user here too :( just bought the conbee stick...

@omersh82
Copy link

i just installed the conbee as a standalone docker, had to re-add the sensor but now there is no dependency on the hassio

@labaland
Copy link

i just installed the conbee as a standalone docker, had to re-add the sensor but now there is no dependency on the hassio

Do you mean this one ? : https://registry.hub.docker.com/r/marthoc/deconz

@omersh82
Copy link

i just installed the conbee as a standalone docker, had to re-add the sensor but now there is no dependency on the hassio

Do you mean this one ? : https://registry.hub.docker.com/r/marthoc/deconz

yes

@jlvandusen
Copy link

jlvandusen commented Jul 24, 2020 via email

@omersh82
Copy link

Did it actually install 6.1.1 as a docker container on Synology right? James From: omersh82mailto:[email protected] Sent: Friday, July 24, 2020 2:49 PM To: home-assistant/hassio-addonsmailto:[email protected] Cc: James VanDusenmailto:[email protected]; Mentionmailto:[email protected] Subject: Re: [home-assistant/hassio-addons] HASS.IO addon upgrade to 6.1.1 error (#1487) i just installed the conbee as a standalone docker, had to re-add the sensor but now there is no dependency on the hassio Do you mean this one ? : https://registry.hub.docker.com/r/marthoc/deconzhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fregistry.hub.docker.com%2Fr%2Fmarthoc%2Fdeconz&data=02%7C01%7C%7C0781bb3a2d154be667e108d83002526c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637312133807609230&sdata=JB7ltNH%2FpvgfoxRTUycZyaCo8%2FcwALy1bSbJR3dh9iY%3D&reserved=0 yes — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fhassio-addons%2Fissues%2F1487%23issuecomment-663681981&data=02%7C01%7C%7C0781bb3a2d154be667e108d83002526c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637312133807609230&sdata=g%2F3tWXXOlXRUa4TGxjbiIZxsTSKrg7FE41TIizS5CVo%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADTO3YGOWCVJ3MA6AXUODC3R5HJUHANCNFSM4PDJ63HA&data=02%7C01%7C%7C0781bb3a2d154be667e108d83002526c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637312133807609230&sdata=eUPc%2F1s1WpqTUpmKW61XDd1ikLnMK%2FrRwipwnTJB1KI%3D&reserved=0.

yes, and add it as an integration to ha with the internal ip it got from the docker

@labaland
Copy link

Works for me now. But how do i check if i have the newest version of deconz? omhersh82 ?

@jlvandusen
Copy link

It should be shown on the container... when in docker?

@labaland
Copy link

It should be shown on the container... when in docker?

[marthoc/deconz] Current deCONZ version: 2.05.79

@pvizeli
Copy link
Member

pvizeli commented Jul 24, 2020

Just for lowering the happiness, we updated the library inside container because deconz updated the glibc which here binary blobs are built again. If marthoc fix the issues because some components stop to work, you end up in same issue, or short never update also that container because the next version can include the new glibc fix and it leads on the same issue now. Try to become a kernel update for your system is the only longterm fix

@labaland
Copy link

labaland commented Jul 24, 2020 •
edited
Loading

Just for lowering the happiness, we updated the library inside container because deconz updated the glibc which here binary blobs are built again. If marthoc fix the issues because some components stop to work, you end up in same issue, or short never update also that container because the next version can include the new glibc fix and it leads on the same issue now. Try to become a kernel update for your system is the only longterm fix

Ok :( sry for my noob question.. Is Raspberry Pi 4 B (2gb) the best device to host HA on? everything will always work there? will restarts and other things be much slower?

@pvizeli pvizeli mentioned this issue Jul 25, 2020
Closed
@bgmn
Copy link

bgmn commented Jul 25, 2020

For those with an old snapshot like me:

docker container rm <id of deconz 6.1.1 container>
docker image rm homeassistant/amd64-addon-deconz:6.1.1 (use --force if necessary)
docker pull homeassistant/amd64-addon-deconz:5.3.6
docker tag homeassistant/amd64-addon-deconz:5.3.6 homeassistant/amd64-addon-deconz:6.1.1

Start addon from HA web interface. It is by far not the cleanest approach, but it works for me

Did you manually create a container from the image after tag command? And if you did, what parameters did you use?
All I'm seeing is the old 6.1.2 version on supervisor panel.

@mpolivanov
Copy link

Did you manually create a container from the image after tag command? And if you did, what parameters did you use?
All I'm seeing is the old 6.1.2 version on supervisor panel.

no, it is created automatically by surevisor

@mpepping
Copy link

Newer Synology models ship with the 4.4 kernel instead of the 3.10 or even 3.2 kernel.
Doesn't change the fact that it's an unsupported configuration to run HA supervised though.

https://www.reddit.com/r/synology/comments/cz8xse/kernel_4459_on_dsm_62/

@bgmn
Copy link

bgmn commented Jul 26, 2020

I'm installing Ubuntu server on Synology virtual machine manager and configuring Docker on it. That way I would have new kernel on Docker host and run Home assistant without legacy problems. I'm afraid how much will the overhead of virtual machine slow things down.

@jlvandusen
Copy link

I ended up enabling VMM on my 1517+ and then downloaded THE SUPPORTED VMDK version and proceeded to migrate over my configuration to that... with 100% success.... now running Deconz 6.12 now with full support.

@bgmn
Copy link

bgmn commented Jul 27, 2020

I ended up enabling VMM on my 1517+ and then downloaded THE SUPPORTED VMDK version and proceeded to migrate over my configuration to that... with 100% success.... now running Deconz 6.12 now with full support.

Right after installing Ubuntu, Docker and Home Assistant, I noticed the supported VMDK version. 😀

@Nick1100
Copy link

How to run it corecley on donker om Synology itself via supervisor itself?

deCONZ: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

There must be a way to solve this error

@jlvandusen
Copy link

How to run it corecley on donker om Synology itself via supervisor itself?

deCONZ: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

There must be a way to solve this error

Depending upon the synology you have, please try to run the VMDK version in using VMM from synology. Once you have it up and running, you can simply copy the backup or if you can see the files, copy the files from the docker and overwrite the deployed version running under VMM.... it will essentially migrate your config to the VMM version and you can use the latest Deconz etc...

@pvizeli pvizeli mentioned this issue Jul 28, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
add-on: deconz wontfix
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix ABI compatibility with old unsupported linux kernel on amd64 home-assistant/addons