Container start stuck in loop

[potatostuff13]

What happened?

Upgraded to 2.1.1 and now docker container is stuck in a loop on start and never fully starts. Container does not work.

What did you expect to happen?

I expected that the container would complete startup.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.1.1

Adapter firmware version

20240710

Adapter

zstack: Sonoff Zigbee Dongle P

Setup

Docker container on Unraid

Debug log

Log behavior:

Starting Zigbee2MQTT without watchdog.
[2025-02-21 08:34:53] info: z2m: Logging to console, file (filename: log.log)
[2025-02-21 08:34:53] info: z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)
[2025-02-21 08:34:53] info: z2m: Starting zigbee-herdsman (3.2.5)
[2025-02-21 08:34:53] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
Starting Zigbee2MQTT without watchdog.
[2025-02-21 08:34:54] info: z2m: Logging to console, file (filename: log.log)
[2025-02-21 08:34:54] info: z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)
[2025-02-21 08:34:54] info: z2m: Starting zigbee-herdsman (3.2.5)
[2025-02-21 08:34:54] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
Starting Zigbee2MQTT without watchdog.
[2025-02-21 08:34:56] info: z2m: Logging to console, file (filename: log.log)
[2025-02-21 08:34:56] info: z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)
[2025-02-21 08:34:56] info: z2m: Starting zigbee-herdsman (3.2.5)
[2025-02-21 08:34:56] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}

[Koenkk]

Could you provide the debug log of this?

See this on how to enable debug logging.

[potatostuff13]

Starting Zigbee2MQTT without watchdog.

[2025-02-22 09:31:13] debug:    z2m: Removing old log directory '/config/log/2025-02-22.09-30-56'

[2025-02-22 09:31:13] info:     z2m: Logging to console, file (filename: log.log)

[2025-02-22 09:31:13] debug:    z2m: Loaded state from file /config/state.json

[2025-02-22 09:31:13] info:     z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)

[2025-02-22 09:31:13] debug:    z2m: sd-notify loaded

[2025-02-22 09:31:13] info:     z2m: Starting zigbee-herdsman (3.2.5)

[2025-02-22 09:31:13] debug:    z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":6754,\"extendedPanID\":[221,221,221,221,221,221,221,221],\"channelList\":[11],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/database.db\",\"databaseBackupPath\":\"/config/database.db.backup\",\"backupPath\":\"/config/coordinator_backup.json\",\"serialPort\":{\"path\":\"/dev/ttyUSB0\",\"adapter\":\"zstack\"},\"adapter\":{\"disableLED\":false}}"'

[2025-02-22 09:31:13] debug:    zh:adapter:discovery: Error while trying to match USB adapter (spawn udevadm ENOENT).

[2025-02-22 09:31:13] debug:    zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyUSB0","adapter":"zstack"},"adapter":{"disableLED":false},"databasePath":"/config/database.db","databaseBackupPath":"/config/database.db.backup","backupPath":"/config/coordinator_backup.json"}'

[2025-02-22 09:31:13] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}

[Koenkk]

Do you see more in the STDOUT? (docker logs -f CONTAINER_ID). Also on what hardware are you running z2m? (I'm especially interested in the CPU architecture)

[potatostuff13]

A few cycles of the STDOUT attached.

Hardware:
CPU: Intel Core i5-13500 (Raptor Lake)
Motherboard: Asrock Z690 Extreme

OS: Unraid

STDOUT.txt

[potatostuff13]

Not sure if this is helpful, but if I designate the port by-id vs ttyUSB0, I get a different set of errors:

by_id_logs.txt