Hello,
I’m experiencing a reproducible issue with deCONZ since the end of April.
Environment
- Raspberry Pi 5
- Raspberry Pi OS / Debian 12 Bookworm (64-bit)
- Linux kernel 6.12.x
- ConBee III
- deCONZ 2.32.5
- Around 80 Zigbee devices
- ConBee III connected via USB extension cable
- Native installation (no Docker)
Symptoms
Every 2-3 days the complete Zigbee network stops responding.
After a short time, devices reconnect one after another.
At the same moment the ioBroker deCONZ adapter reports only an ECONNRESET, which appears to be a consequence of the actual deCONZ failure.
The deCONZ web interface is sometimes still reachable shortly before deCONZ crashes and is automatically restarted by systemd.
Journal output
Immediately before the crash I repeatedly get
Could not create AF_NETLINK socket (Too many open files)
followed by
GLib-ERROR **: Creating pipes for GWakeup: Too many open files
and finally
deconz.service: Main process exited, code=killed, status=5/TRAP
deconz.service: Failed with result 'signal'
Afterwards systemd automatically restarts deCONZ.
Already checked
LimitNOFILE=524288/proc/<pid>/limitsalso reports 524288 open files- Immediately after restart deCONZ only has about 20 open file descriptors
- USB extension cable is used
- ConBee III is detected correctly (
lsusb) - Debian and deCONZ are fully up to date
- The issue does not seem to originate from ioBroker; it only reports
ECONNRESETafter deCONZ crashes.
Question
Is this a known issue? The combination of
Could not create AF_NETLINK socket (Too many open files)
and
GLib-ERROR: Creating pipes for GWakeup: Too many open files
looks like an internal resource or socket leak inside deCONZ rather than a Linux file descriptor limit issue.
I’m happy to provide additional logs, debug output or perform further tests if required.
Thank you.