Z2M Keeps crashing #12031
Comments
|
Ok, I noticed that watchtower had updated zigbee2mqtt to 1.25.0 |
|
I am seeing a similar issue. Watchtower updated overnight, now z2m doesn't start. Rolled back to 1.24.0 for now, but there part of my network seems to be offline. Error with |
|
seeing same issues. Zigbee2mqtt running as docker container. Log states: |
|
Happens on |
|
I'm running in a Docker container on Ubuntu |
As @markprins mentioned this is due to libsecomp2, read the first note from https://github.com/Koenkk/zigbee2mqtt/releases @ChrisHae could you look at the |
Thanks, this solved it for me. Even read it on the april's fool post yesterday, but completely forgot about it... |
The message is printed because it received a faulty frame. I will look at it and change the message. |
|
So after update to 1.25.0 i start observing random crashes of z2m. It already happened twice in a week. If this is caused by faulty frame, any reason for that? I didnt do anything (no new device) to zigbee network. |
|
We would need to see a zigbee sniffer log to see the real origin and kind of the (faulty) frame that causes those messages. Could anybody provide that? |
|
I never did any zb sniffing, but i have spare cc2652p. So if there is any howto+firmware i can try. One thing is that i need to avoid breaking my current network. So couple of questions:
|
|
here is a howto: https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#with-cc2531 You keep your network as it is and use only the other stick for sniffing. It is a distinct process. |
|
For what it's worth, I am experiencing crashes with v1.25.0-dev as well. I'm running in a docker container on top of Ubuntu 20.04 Server. Did not experience these issues with v1.24.0 release either. I can't seem to pinpoint the error, but if someone could point me in the right direction as to what log to look at to get more information, that would be great. |
|
Since my last comment, i didnt notice any restarts. So nothing to share yet. |
Weirdly, mine has been up for two days now (since I last posted) and hasn't crashed. I'll keep an eye on it, but so far, so good. |
NM... crashed again about 15 hours ago, maybe right after posting my last response. Unfortunately, still no sign of what might be the issue. At least it's a silent crash, and docker spins right back up. |
|
FWIW - Observed another crash after about 4-days of up-time on the latest stable release v1.25.1. |
|
@nebhead How serious are those crashes? Aren't they just some error messages in the logs or does the whole program crash? And could you provide a sniffer log maybe? |
|
In my case, a crash means the Docker container crashes and stops. It's set to restart automatically, which it does. And as such, it would be ok if it just happened like once per day or so. |
I'm running in a docker, and the docker container crashes and restarts automatically. In my case, it's usually after 1-2 days. Did not occur on v1.24.x
OK, so this is where I'm having some challenges and need some help. I've looked at the log in Portainer, and inside the UI of the Z2M application and it doesn't show enough history for me to track down the error. Does anyone have any advice on how I can get logs that are more persistent? |
|
I just tried the latest version, and every 10 seconds might have been an overstatement I see. Here's a snippet from my log. The actual number is 33 crashes in 8,5 hours. And none of my 100 zigbee devices are functional atm. I reverted to 1.24.0 and it's working again. |
I just tried 1.25.1 and the message is the same. I don't have a sniffer at hand, but 1.24.0 is still working for me. So something changed from 1.24.0 to 1.25.0 which affects this. |
|
Well these information pinpoint the problem pretty precisely. I will try to find a fix and upload soon. Just to be curious: do you have any Green Power Devices? |
|
Yes I do. And I also have a small suspicion of the device that's causing it. Are you on Discord? If so, hit me up there. Else, I'll try to give a long explanation here |
|
@ChrisHae just FYI i dont own any Green Power devices and i observed those issues also. |
|
@bkupidura does your error messages look the same? With |
|
Nope, my last stack trace: But as you said, 1.24.0 was rock solid. So i would expect that something has changed in z2m between 1.24 and 1.25. |
|
@Inrego perhaps you could test your network without that device. When you enable zigbee-herdsman debug logging we should be able to see the network address of that device. |
|
Alright, so that indicates it's not related to GreenPower. Although I do believe I have a GreenPower device gone rogue that's causing the crashes, the crashes seem to happen when receiving a bad frame (GreenPower or not). More info on my rogue GreenPower device: On 1.25.0+, the device doesn't join, Z2M just crashes. The Model (and I think network address) of the joined device keeps changing, so even if I block it from joining again, it joins again shortly after. I am pretty certain that this rogue GreenPower device is a Schneider Electric PowerTag. Strange thing is, it's already connected to a separate Zigbee network (the Schneider Electric hub). Also, Z2M version 1.25.1 adds support for these PowerTags, so I'm not sure why they keep crashing on that version. Maybe because they behave differently when connected to their own hub. |
|
@ChrisHae i enabled debug, lets see. But for me those crashes are not that often (like once or twice per week). So probably i need couple of days to share anything. |
|
I can now confirm the rogue device. I switched it off, and the errors stopped. Another strange thing, I have 2 of them. Only one does this. But that's more of a device related problem, not a Z2M problem I figure. EDIT: I'll now try to update, and pair the rogue PowerTag to Z2M |
|
Ok, I've updated to 1.25.1 and paired the device successfully. However, I'm still getting a lot of crashes. |
|
So I have added some quick fixes. Those errors should now be catched and hopefully does not cause crashes anymore. When posting some logs it would be helpfull when zigbee-herdsman debug logging is enabled. @inegro Do you have checked if the two GP devices have a different firmware version? Perhaps a newer firmware could be the solution there. |
|
On the new latest-dev, and now I'm getting this error: |
|
Trying a few different things on my end. Will give more info tomorrow |
|
I've left it overnight, and the container has been running for 8 hours without crash. With the small caveat that none of my ZigBee devices are working, lol Edit: restarted Z2M and now they're working again. Will get back to you again later |
|
Ok so far it seems to be running alright until I "Permit Join" on my network. Here's something from my log. It seems to be running ok, although being spammed a lot with some greenpower messages (which it says is from the coordinator?). |
|
I'm gonna try now with both of those GreenPower devices switched off. It's just not that feasible for longer periods of time due to the nature of their installation. It requires me to switch off the mains that they're monitoring. |
|
Ok, I've now paired those green power devices back to their own hub. And Z2M seems to run stable again. So this issue can be closed I guess. I'm still having lots of problems when trying to pair them to Z2M, but I guess that's another issue. |
|
Scratch that, my ZigBee network is down again. |
|
There was a pull request that is related to those GP devices I think: And because of that |
|
Ooh that's great news. I've also ordered another zigbee coordinator. But if a fix is coming to Conbee, I'll keep that, and maybe flash the incoming one with sniffer firmware for other purposes. Thanks for linking to how to enable herdsman log output. I was looking for it in settings, without luck. Lets put a pin in this issue and wait and see if I'm still having issues with above changes. |
|
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 |
|
FYI... with version 1.25.2-dev commit: e525919 I am no longer seeing crashes every 2-7 days. |
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Very recently, my Z2M keeps crashing, with this error in the log:
It reboots roughly every 10 seconds.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
I'm not sure, I don't know what caused the issue.
Zigbee2MQTT version
1.25.0
Adapter firmware version
0x26680700
Adapter
Conbee II
Debug log
No response
The text was updated successfully, but these errors were encountered: