-
-
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
Migrated to 2.0.0, failed to start, exited with code 0 or 139 #25092
Comments
139 is a SIGSEGV, could you provide your |
|
Could you change the log level to debug? See this on how to enable debug logging. |
not much more info it seems with …
|
maybe my docker-compose.yaml is of any help — which works flawlessly with 1.42.0
|
Hi there, |
deleted lines with
|
i’m running zigbee2mqtt in a docker container on buster. although 1.42.0 is running smoothly, i’ll try upgrading the pi to bullseye or bookworm in the next couple of days. i guess there might be a possibility that Docker version 20.10.17 doesn’t play nice with the node version that 2.0.0 uses. or is that an unlikely theory? |
I pushed a possible fix in #25189, can you try with |
just pulled and tried it (just now), but unfortunately the same error pattern as before :( |
@diplix can you try replacing the appropriate "prebuild" file in your container using the ones I built here (make sure to extract and rename the same). Then see if Z2M starts? Side note: 139 could be a hardware issue too (memory). |
@Nerivec i would, but can you help/direct me where/how i can find the prebuild files to download? since zigbee2mqtt version 1.42.0 is running (very) smoothly on the same machine, isn’t it rather unlikly there’s a HW/memory issue? |
Scroll down on that page I linked before, it's at the bottom (by arch, like Memory is a tricky thing, if it hits an area that wasn't before, and that area is the one with issues... that will do it. |
@Nerivec could you try with the latest dev branch in 30 mins from now? |
Wrong tag 😜 |
i just updated my raspberry pi to bookworm, reinstalled docker, pulled and started my zigbee2mqtt v2.0.0 (latest-dev) container — and now it works. seems to me either v2.0.0 won’t run on older systems / docker installs or memory menagment in buster is not sufficient. this issue could be closed, but maybe there should be a warning, that v2.0.0 won’t run in older docker installs in the Readme? |
latest-dev would have included #25202 |
🤷♂️ |
What happened?
after i migrated to 2.0.0 (accoring to migration log everything went fine), zigbee2bqtt faily to start:
What did you expect to happen?
error code 139 seems to indicate a serial problem, at least accoring to issue 11545.
How to reproduce it (minimal and precise)
i run zigbee2mqtt on docker on raspberry pi 3.
1.42.0 runs fine.
Zigbee2MQTT version
1.42.0, 2.0.0
Adapter firmware version
20240710
Adapter
zStack3x0, LAUNCHXL-CC1352P-2
Setup
i run zigbee2mqtt on docker on raspberry pi 3
Debug log
No response
The text was updated successfully, but these errors were encountered: