Deconz 6.1.1 broken - after upgrade error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

Configuration Zigbee
1

It asked to update the deconz on HA to 6.1.1
I clicked update
It spun and eventually I see this in the logs:

[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
[20:36:26] 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.
[00:36:28] INFO: Starting udevd...
[00:36:28] INFO: Running the IKEA OTA updater...
[00:36:28] INFO: Running the OSRAM LEdvance OTA updater...
[00:36:28] INFO: Running the deCONZ OTA updater...
[20:36:28] INFO: Waiting for device...
[20:36:28] 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.
2

Need forum monitors to review this… here is thread for bug

3

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

  1. Stopped Docker
  2. I then found the last good snapshot of my docker folder for hass.io
  3. 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)
  4. I then started docker
  5. I went and stopped all hassio containers
  6. I deleted all containers related to hassio
  7. I then removed all images related to hassio
  8. I started fredrike’s synology package - it did its part downloading and re-creating all the primary containers to run homeassistant
  9. Once Home assistant was back up and running
  10. I went into supervisor
  11. I selected deconz
  12. it showed I was originally running 5.3.6
  13. I then went back to docker
  14. downloaded homeassistant/addon_deconz 5.3.6
  15. once downloaded, I mounted it
  16. I named the container addon_core_deconz
  17. I clicked on advance
  18. I set its volume to the below path
    /data = /docker/hass.io/addons/data/core_deconz
  19. I did not start it
  20. I went back to homeassistant UI and into supervisor
  21. I then started deconz
  22. It started…
  23. after a few moments my sensors were back online!

Close call…

4

I’m having the same issue :frowning: Docker on Synology. Looks like I’m stuck on the old version of Deconz.

5

install VMM and run it as a VMDK - I ended up then copying my config over to the SAMBA share on the new install via vmm and viola! I have a future proof version running under VMM and supporting deconz 6.20 even :slight_smile:

6

I’m thinking about moving my install off Synology completely.

I’m confused over the kernel version issue though. I thought Docker was virtualisation, so the underlying OS shouldn’t affect it.

7

No Docker is Containerisation which is very different. it relies on parts of the base OS which is how the images are kept so small.

Where as virtualisation is total abstraction, each VM has a full OS Install of its own.