deCONZ upgrade from 2.11.5 to 2.12.6 crashes

deCONZ General Support
1

deconz init failed after update to version 2.12.6, here are the logs

Aug 20 07:51:13 fhem systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.
Aug 20 07:51:44 fhem systemd[1]: deconz.service: Service RestartSec=30s expired, scheduling restart.
Aug 20 07:51:44 fhem systemd[1]: deconz.service: Scheduled restart job, restart counter is at 6.
Aug 20 07:51:44 fhem systemd[1]: Stopped deCONZ: ZigBee gateway – REST API.
Aug 20 07:51:44 fhem systemd[1]: Started deCONZ: ZigBee gateway – REST API.
Aug 20 07:51:44 fhem systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 20 07:51:44 fhem systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 20 07:51:44 fhem systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.
Aug 20 07:51:44 fhem deCONZ[12051]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-pi’
Aug 20 07:51:44 fhem deCONZ[12051]: libpng warning: iCCP: known incorrect sRGB profile
Aug 20 07:51:45 fhem deCONZ[12051]: This plugin does not support propagateSizeHints()
Aug 20 07:51:45 fhem deCONZ[12051]: This plugin does not support propagateSizeHints()
Aug 20 07:51:48 fhem deCONZ[12051]: This plugin does not support propagateSizeHints()
Aug 20 07:51:49 fhem systemd[1]: deconz.service: Main process exited, code=killed, status=7/BUS
Aug 20 07:51:49 fhem systemd[1]: deconz.service: Failed with result ‘signal’.
Aug 20 07:51:49 fhem systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 20 07:51:49 fhem systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 20 07:51:49 fhem systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.

Any idea or recommendation on this issue?

Thx

*) restored backup to 2.,11.5 works

2

Same here, I posted a question on discord. detail as below: -

I have an issue after updating to 2.12.6 this morning. I have a ConBee II on a Raspberry Pi 4 running Buster, Kernel 5.10.52-v8+ . Before updating deConz/Phoscon, I updated the ConBee II F/W to the latest 0x26720700 successfully. It is headless by the way, so don’t really use deConz-GUI. I have tried reinstalling the deb package manually after the initial issues to no avail. When I start deConz initially, I get: -

systemctl status deconz
● deconz.service - deCONZ: ZigBee gateway – REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2021-08-20 12:35:57 BST; 2s ago
Main PID: 5008 (deCONZ)
Tasks: 3 (limit: 3949)
CGroup: /system.slice/deconz.service
└─5008 /usr/bin/deCONZ -platform minimal --http-port=80 Aug 20 12:35:57
raspberrypi4 systemd[1]: Started deCONZ: ZigBee gateway – REST API. Aug 20 12:35:58
raspberrypi4 deCONZ[5008]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-pi’ Aug 20 12:35:58
raspberrypi4 deCONZ[5008]: libpng warning: iCCP: known incorrect sRGB profile Aug 20 12:35:58
raspberrypi4 deCONZ[5008]: This plugin does not support propagateSizeHints() Aug 20 12:35:58
raspberrypi4 deCONZ[5008]: This plugin does not support propagateSizeHints()(edited)

Then after a few seconds I get: -
systemctl status deconz
● deconz.service - deCONZ: ZigBee gateway – REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: signal) since Fri 2021-08-20 12:36:35 BST; 14s ago
Process: 5030 ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80 (code=killed, signal=BUS) Main PID: 5030 (code=killed, signal=BUS)

Same issues as @rsedlmeier in journalctl logs: -

systemd[1]: Started deCONZ: ZigBee gateway – REST API.
Aug 20 12:56:29 raspberrypi4 deCONZ[6458]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-pi’
Aug 20 12:56:29 raspberrypi4 deCONZ[6458]: libpng warning: iCCP: known incorrect sRGB profile
Aug 20 12:56:30 raspberrypi4 deCONZ[6458]: This plugin does not support propagateSizeHints()
Aug 20 12:56:30 raspberrypi4 deCONZ[6458]: This plugin does not support propagateSizeHints()
Aug 20 12:56:33 raspberrypi4 deCONZ[6458]: This plugin does not support propagateSizeHints()
Aug 20 12:56:33 raspberrypi4 systemd[1]: deconz.service: Main process exited, code=killed, status=7/BUS
Aug 20 12:56:33 raspberrypi4 systemd[1]: deconz.service: Failed with result ‘signal’.
Aug 20 12:56:33 raspberrypi4 systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 20 12:56:33 raspberrypi4 systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 20 12:56:33 raspberrypi4 systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.

Any help appreciated
It worked fine under version 2.11.5, the last stable

3

Is this the vanilla deCONZ version, or was the deCONZ REST API plugin self compiled in earlier versions?

The code=killed, signal=BUS indicates a SEGV but I wonder why this didn’t happen in the beta versions :thinking:

4

Vanilla for me.
P.S. I’ve reverted to 2.11.05, and this works fine. I’ve left the ConBee II F/W as the latest, no problems with this combo. so far.

5

Just by hazard, are you able to test intermediate versions ?
Because there is so much change beetween the 2.11.5 and the 2.12.6.

6

I can give it a go tomorrow morning, any particular version?

Just so you know, before I reverted to 2.11.05 I tried a command from a discord guru/pro/mod as follows: -

/usr/bin/deCONZ -platform minimal --http-port=80

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-root’
libpng warning: iCCP: known incorrect sRGB profile
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
Bus error

7

IDK if @manup already have an idea, but there is so much code to check.

There is nothing new in the v2.12.5-beta
There is nothing new in the v2.12.4-beta
Big change in the v2.12.3-beta, so this one can help (even there is 60 files changed in this version)

8

OK, will try 3-beta then.
Do you just want the same log detail as previously?

dpkg -l | grep -i deconz
ii deconz 2.12.03-raspbian-stretch-beta armhf A generic ZigBee monitoring and control tool

After start attempt: -
systemctl status deconz
● deconz.service - deCONZ: ZigBee gateway – REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: signal) since Sat 2021-08-21 09:45:13 BST; 1s ago
Process: 17039 ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80 (code=killed, signal=BUS)
Main PID: 17039 (code=killed, signal=BUS)

logs from journalctl: -

systemd[1]: deconz.service: Service RestartSec=30s expired, scheduling restart.
Aug 21 09:46:16 raspberrypi4 systemd[1]: deconz.service: Scheduled restart job, restart counter is at 5.
Aug 21 09:46:16 raspberrypi4 systemd[1]: Stopped deCONZ: ZigBee gateway – REST API.
Aug 21 09:46:16 raspberrypi4 systemd[1]: Started deCONZ: ZigBee gateway – REST API.
Aug 21 09:46:16 raspberrypi4 systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 21 09:46:16 raspberrypi4 systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 21 09:46:16 raspberrypi4 systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.
Aug 21 09:46:16 raspberrypi4 deCONZ[17083]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-pi’
Aug 21 09:46:16 raspberrypi4 deCONZ[17083]: libpng warning: iCCP: known incorrect sRGB profile
Aug 21 09:46:17 raspberrypi4 deCONZ[17083]: This plugin does not support propagateSizeHints()
Aug 21 09:46:17 raspberrypi4 deCONZ[17083]: This plugin does not support propagateSizeHints()
Aug 21 09:46:20 raspberrypi4 deCONZ[17083]: This plugin does not support propagateSizeHints()
Aug 21 09:46:20 raspberrypi4 systemd[1]: deconz.service: Main process exited, code=killed, status=7/BUS
Aug 21 09:46:20 raspberrypi4 systemd[1]: deconz.service: Failed with result ‘signal’.
Aug 21 09:46:20 raspberrypi4 systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 21 09:46:20 raspberrypi4 systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 21 09:46:20 raspberrypi4 systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.

Manual start as previous: -

/usr/bin/deCONZ -platform minimal --http-port=80
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-root’
libpng warning: iCCP: known incorrect sRGB profile
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
Bus error

Just tried the above as a separate reply, and it stopped me, apparently I can only reply 3 times to one topic as I’m new.
Anything additional you need?

@rsedlmeier - Sorry, I don’t know what propagateSizeHints() means? I can’t reply any more - I’m blocked to x3 replies per topic.

Oddly 3-beta has started to work? I’ve changed nothing…

Aug 21 09:51:20 raspberrypi4 systemd[1]: Service RestartSec=30s expired, scheduling restart.
Aug 21 09:51:20 raspberrypi4 systemd[1]: deconz.service: Scheduled restart job, restart counter is at 14.
Aug 21 09:51:20 raspberrypi4 systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 21 09:51:20 raspberrypi4 systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 21 09:51:20 raspberrypi4 systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.
Aug 21 09:51:20 raspberrypi4 systemd[1]: Stopped deCONZ: ZigBee gateway – REST API.
Aug 21 09:51:20 raspberrypi4 systemd[1]: Started deCONZ: ZigBee gateway – REST API.
Aug 21 09:51:20 raspberrypi4 deCONZ[17658]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-pi’
Aug 21 09:51:20 raspberrypi4 deCONZ[17658]: libpng warning: iCCP: known incorrect sRGB profile
Aug 21 09:51:21 raspberrypi4 deCONZ[17658]: This plugin does not support propagateSizeHints()
Aug 21 09:51:21 raspberrypi4 deCONZ[17658]: This plugin does not support propagateSizeHints()

Phoscon-GW Web Page hasn’t yet detected the ConBee II though!
Left it running a while and it still has not connected to the ConBee II. ~40mins

9

Thanks for contributing on this issue.
However, before you invest installing other versions, any idea what’ up with the msg on: propagateSizeHints()

/RS

10

The messages is from Qt internally, it’s annoying but we haven’t found a way to get rid of it yet.

11

What would be helpful to find the root of the crash is a backup.
Could you please create one (or simply the zll.db) and send it to support@dresden-elektronik.de.

I can load it in my development environment and see if some specific device in the database causes the crash.

12

For zll.db do you want me to try 2.12.6 again? I reverted back to 2.11.5.
Also, where would that file be located?

13

Thanks, the one from v2.11.5 is fine.

On Linux the file is located under $HOME/.local/share/dresden-elektronik/deCONZ/zll.db

It can also be found by find ~ -name zll.db

14

Sent.

15

Had a look in the zll.db file. The file loads fine here, but the database doesn’t seem to contain any lights or sensors. There are entries for routers (plugs and one light) which show up in deCONZ GUI.

I think based on that there should have been lights in the database :thinking:

Do you see any lights in the Phoscon App when running under v2.11.5?

16

Yes, I only have one light, with 4 power sockets/plugs (which come under the light subheading) and then 6 physical sensors (a mixture of door contact sensors, motion sensors and a vibration sensor). Oh and another light - a lightstrip that I don’t use much, which is normally greyed out because it’s off.

17

As I am the initiator of this thread, I can provide logs and the zll db filled with more than 30 devices by monday.
Please tell, if you want it and I install an run 2.16.5 again.

18

@manup Wouldn’t a backtrace help here to pin down the issue? I’ve lately seen some crashes where QNetworkAccessManager was involved, presumably some call before defined thingy…

19

Thanks the zll.db file would be helpful, at least to rule out if this is a bug related to specific device entries.

@manup Wouldn’t a backtrace help here to pin down the issue? I’ve lately seen some crashes where QNetworkAccessManager was involved, presumably some call before defined thingy…

Indeed a backtrace is always good, Erik wrote a guide on how to get a core dump for Raspbian:

20

Okay, after apt-get upgrade & reboot I get the crash again, here are the logs

fhem@fhem(2.10):~ $ systemctl status deconz
● deconz.service - deCONZ: ZigBee gateway – REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: signal) since Mon 2021-08-23 13:52:05 CEST; 35s ago
Process: 403 ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80 (code=killed, signal=BUS)
Main PID: 403 (code=killed, signal=BUS)

fhem@fhem(2.10):/var/log $ s tail syslog
Aug 23 13:53:25 fhem systemd[1]: Started deCONZ: ZigBee gateway – Initialisation.
Aug 23 13:53:25 fhem deCONZ[1731]: libpng warning: iCCP: known incorrect sRGB profile
Aug 23 13:53:26 fhem deCONZ[1731]: This plugin does not support propagateSizeHints()
Aug 23 13:53:26 fhem deCONZ[1731]: This plugin does not support propagateSizeHints()
Aug 23 13:53:29 fhem deCONZ[1731]: This plugin does not support propagateSizeHints()
Aug 23 13:53:30 fhem systemd[1]: deconz.service: Main process exited, code=killed, status=7/BUS
Aug 23 13:53:30 fhem systemd[1]: deconz.service: Failed with result ‘signal’.
Aug 23 13:53:30 fhem systemd[1]: deconz-init.service: Start request repeated too quickly.
Aug 23 13:53:30 fhem systemd[1]: deconz-init.service: Failed with result ‘start-limit-hit’.
Aug 23 13:53:30 fhem systemd[1]: Failed to start deCONZ: ZigBee gateway – Initialisation.

where can I mail to my zll.db ?