-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
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
Container keeps restarting with version 1.23 #11545
Comments
Here is content of serial:
port: /dev/ttyUSB0
disable_led: true
mqtt:
server: mqtt://my-server:1883
base_topic: zigbee2mqtt-home
user: '!secret user'
password: '!secret password'
client_id: zigbee2mqtt-home
include_device_information: true
permit_join: false
frontend:
port: 8080
host: 0.0.0.0
devices: devices.yaml
groups: groups.yaml
ota:
ikea_ota_use_test_url: false
update_check_interval: 3600
disable_automatic_update_check: true
availability:
active:
timeout: 20
passive:
timeout: 720
homeassistant: false
advanced:
log_level: debug
log_output: ['console']
pan_id: 6755
channel: 25
last_seen: ISO_8601_local
legacy_api: false Here is content of '0x000d6ffffe4b4615':
friendly_name: hallway-wall-light
availability: true
'0x847127fffebea049':
friendly_name: mailbox-motion
'0x14b457fffe693ef6':
friendly_name: storeroom-motion
'0xa4c138a63ca36dd1':
friendly_name: '0xa4c138a63ca36dd1' Here is content of {} |
Please provide the debug log of the crash See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
Here we go:
|
I don't see any crash in this log. Can you provide the STDOUT when running with env variable |
Here we go:
This log doesn't seem to be very useful too. Just switching image between Just in case, here is my version: "3.7"
services:
zigbee2mqtt:
image: koenkk/zigbee2mqtt:latest-dev
# image: koenkk/zigbee2mqtt:1.23.0
container_name: zigbee2mqtt
restart: unless-stopped
ports:
- "8080:8080/tcp"
volumes:
- ./data:/app/data
- /run/udev:/run/udev:ro
devices:
- /dev/ttyUSB0:/dev/ttyUSB0
environment:
- TZ=Europe/Berlin
- DEBUG=*
privileged: true |
Still no crash, it just stop working right? Can you do a |
yes, I run it in the docker, but can run interactively from the shell. Which node to take 14 or 16? |
What system are you running on? |
Took 14. $:> cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Rev 1.2
$:> lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
$:> arch
armv7l
$:> uname -a
Linux raspberrypi 5.10.92-v7+ #1514 SMP Mon Jan 17 17:36:39 GMT 2022 armv7l GNU/Linux
$:> node -v
v14.19.0
$:> npm -v
6.14.16
$:> git clone https://github.com/Koenkk/zigbee2mqtt.git
remote: Total 21079 (delta 717), reused 735 (delta 526), pack-reused 20079
Receiving objects: 100% (21079/21079), 87.04 MiB | 2.32 MiB/s, done.
Resolving deltas: 100% (15776/15776), done.
$:> git checkout dev
Branch 'dev' set up to track remote branch 'dev' from 'origin'.
Switched to a new branch 'dev'
$:> git rev-parse HEAD
9e35f22ac4862103abe1c41678ab0de5c1f0051c
$:> npm ci
added 922 packages in 116.529s
$:> echo $?
0 |
I did |
I think it worth to take a look in direction of |
Don't know if this will help but with the addon on Home Assistant OS, I get the same problem. Starting of zigbee2mqtt is on infinite loop and it "breaks" on same line as @avakarev. Everything was working fine on 1.23.0-dev commit f6f507c
|
@Koenkk I can confirm now that downgrading |
I also noticed that z2m's dockerfile referencing quite old version of alpine: 3.12. I assume |
Ok, image based on |
@avakarev I think this issue is specific to rpi/arm, latest-dev works fine om my intel nuc. |
I run zigbee2mqtt as HA addon on Home Assistant OS 7.4. Hardware : Raspberry Pi 4 B 8 Go |
Same problem here with a Raspberry Pi 4 B 4 GB with the arm64 image. |
@Koenkk can you please bump zigbee-herdsman pkg in zigbee-herdsman-converters from
|
Same problem with a Raspberry Pi 4 2 GB with the arm64 image with the zigbee2mqtt-edge version. |
JFYI I reproduced the issue with just |
@avakarev thanks for the investigation! I've reverted to serialport 9 for the time being, lets keep this issue open until serialport/node-serialport#2438 is fixed. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened?
Docker container of image
koenkk/zigbee2mqtt:latest-dev
constantly restarts.Same configurations works just fine with latest release
koenkk/zigbee2mqtt:1.23.0
What did you expect to happen?
I expect container to keep running, connects to mqtt server and publishes / consumes messages.
How to reproduce it (minimal and precise)
Pull and run latest
koenkk/zigbee2mqtt:latest-dev
image (I found the following version in logs:1.23.0-dev (commit #a345181)
Zigbee2MQTT version
1.23.0-dev (commit #a345181)
Adapter firmware version
20211217
Adapter
Electrolama zzh! CC2652R
Debug log
zigbee2mqtt | Using '/app/data' as data directory
zigbee2mqtt | Zigbee2MQTT:debug 2022-02-21 17:22:14: Loaded state from file /app/data/state.json
zigbee2mqtt | Zigbee2MQTT:info 2022-02-21 17:22:14: Logging to console only'
zigbee2mqtt | Zigbee2MQTT:info 2022-02-21 17:22:14: Starting Zigbee2MQTT version 1.23.0-dev (commit #a345181)
zigbee2mqtt | Zigbee2MQTT:info 2022-02-21 17:22:14: Starting zigbee-herdsman (0.14.17)
zigbee2mqtt | Zigbee2MQTT:debug 2022-02-21 17:22:14: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":true},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[25],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6755},"serialPort":{"path":"/dev/ttyUSB0"}}'
The text was updated successfully, but these errors were encountered: