#Docker matter-server dead after system update

1 messages · Page 1 of 1 (latest)

molten frost
#

I've not had any issues with matter-server before but now after a system update it just seems to go into a crash loop.

[Wed Nov 27 10:16:43 2024] Code: 81 c7 38 02 00 00 e8 9f 01 00 00 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 41 56 be 68 01 00 00 41 55 41 54 55 53 48 89 fb <4c> 8b 6f 28 bf 01 00 00 00 e8 52 ad fa ff 48 85 c0 0f 84 be 0d eb
[Wed Nov 27 10:17:44 2024] matter-server[65661]: segfault at 28 ip 0000726718324130 sp 00007ffe3cf56bd0 error 4 in libpython3.11.so.1.0[243130,7267181d0000+1bc000] likely on CPU 11 (core 5, socket 0)
[Wed Nov 27 10:17:44 2024] Code: 81 c7 38 02 00 00 e8 9f 01 00 00 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 41 56 be 68 01 00 00 41 55 41 54 55 53 48 89 fb <4c> 8b 6f 28 bf 01 00 00 00 e8 52 ad fa ff 48 85 c0 0f 84 be 0d eb```

I'm running it Docker via...
```CONTAINER ID   IMAGE                                                     COMMAND                  CREATED        STATUS                            PORTS                      NAMES
e114a441a147   ghcr.io/home-assistant-libs/python-matter-server:stable   "matter-server --sto…"   6 hours ago    Restarting (139) 32 seconds ago                              matter-server```
image.png
junior raptor
#

… oh, you're not running HAOS? that makes things trickier :/

#

i can't see how a change to the host operating system would affect python-matter-server in the docker container, as long as you haven't updated the docker container itself.

#

I'd recommend checking for signs of hardware failure, tbh; run a memory test on your machine, for example.

molten frost
#

I've been using the machine heavily for other things on and off and nothing else is having issues or acting odd in any way, so I don't think it's hardware. There WAS a library that Docker uses that kept echoing noisily to the kernel log which was apparently updated and no-longer does that. I wonder if that's somehow related...

#

It was a library that updated from 1.21 to 1.22 and it was 4 letters long but I'm damned if I can remember what the name of it was...

#

"runc"

junior raptor
#

one other thing you can try is backing up and clearing the configuration for the python-matter-server container, to see if it starts up.

molten frost
#

(could be unrelated, but it is Docker related and that was actually one of the few things updated when this happened)

molten frost
junior raptor
#

it's possible that something got corrupted in the configuration which is triggering a reliable crash at startup, that can be ruled out by clearing the config

#

the container stores everything - keys for talking to matter devices, info about which devices are connected, etc.

molten frost
#

So nuking that would require readding all the devices?

junior raptor
#

back up the config. you just want to clear it to see if clearing it is sufficient for the container to start up.

#

if it doesn't start up, then that's not the issue. If it does start up then there might be some investigation into what broke in the config that triggers the crash - it might be possible to repair, or it might be easiest to re-add the devices :/

molten frost
#

Do you happen to know which folders/files belong to the matter process? Having trouble tracking them down...

junior raptor
#

i'm not that familiar with the docker container :/ I think all of the state should be within a single directory - which might be a docker volume?

#

if you were using haos, my recommendation would have been to make a new backup of the add-on, then restore a previous backup.

molten frost
#

Yeah, this is being used on a NAS that does much else so I'm not using HAOS.

#

I may set up a VM with it at some point though as it's been a bit of a nightmare using HA like this which is a shame.

junior raptor
#

i personally run haos as a VM on my nas, and have had great results using matter devices with that config.

molten frost
#

For reference it seems to create these on start:

-rw------- 1 root root 66 Nov 28 11:20 chip_counters.ini
-rw------- 1 root root 71 Nov 28 11:19 chip_factory.ini```
#

But yeah, same issue fresh.

sleek narwhal
#

If you're using docker compose (which I highly recommend), you can see mapping of the config folder there

molten frost
#

It's borked even as a new blank one

sleek narwhal
#

Are you running a 64 bit OS?

junior raptor
#

wouldn't be running at all otherwise, so that's not the problem. what version of the matter server container are you running? have you tried a newer or older version?

sleek narwhal
#

It definitely did run on some interesting versions of Raspbian that were half 32 bit and half 64 bit. I remember the issues. Though that was a few years ago.

junior raptor
#

this is inside docker tho, so i'd expect it to be fine as long as the kernel was 64bit, since the docker container will have all the required supporting libraries.

molten frost