Matter-server keeps restarting for unknown reasons

Heya!

I am running Home Assistant on a Pi3B+ and have configured the matter-server which, for a while, intermittently would crash but since I turned on watchdog it’s just continuously restarting after being alive for a few minutes.

Here’s a log that always pops up from start to kill:

-----------------------------------------------------------
 Add-on: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 7.0.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.0  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2024.12.5
 Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[14:40:59] INFO: Starting Matter Server...
[14:41:05] INFO: Using 'enu1u1u1' as primary network interface.
[14:41:08] INFO: Successfully send discovery information to Home Assistant.
2025-01-26 14:41:24.918 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2025-01-26 14:41:24.931 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1737898886.860836][118:118] CHIP:CTL: Setting attestation nonce to random value
[1737898886.925117][118:118] CHIP:CTL: Setting CSR nonce to random value
[1737898887.130553][118:118] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1737898887.162363][118:118] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1737898887.169209][118:118] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1737898887.208317][118:118] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1737898887.215834][118:118] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1737898887.313111][118:118] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1737898887.313294][118:118] CHIP:DL: NVS set: chip-counters/reboot-count = 4706 (0x1262)
[1737898887.314664][118:118] CHIP:DL: Got Ethernet interface: enu1u1u1
[1737898887.315526][118:118] CHIP:DL: Found the primary Ethernet interface:enu1u1u1
[1737898887.316432][118:118] CHIP:DL: Got WiFi interface: wlan0
[1737898887.316531][118:118] CHIP:DL: Failed to reset WiFi statistic counts
2025-01-26 14:41:27.357 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2025-01-26 14:41:27.464 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2025-01-26 14:41:28.714 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2025-01-26 14:41:28.715 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2025-01-26 14:41:28.755 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2025-01-26 14:41:28.791 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2025-01-26 14:41:28.794 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2025-01-26 14:41:28.903 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2025-01-26 14:41:29.006 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2025-01-26 14:41:29.007 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
[13:41:33] WARNING: matter-server service exited with code 137 (by signal 9).

Code 137 would indicate a lack of memory but I can’t seem to figure out if that’s actually the case. While my continuous usage is around 85%, it seems that this has more to do with Linux keeping a memory cache available.

To make sure I wasn’t using more memory than needed, I’ve turned off all my addons. From what I can tell there’s no excessive memory usage. Core is using approx 300MB, supervisor about 100 and matter about 60 (which is not running stable, so I imagine this would be lower when properly running).

I’m not sure what to do anymore and what to debug but would love to figure out what the problem could be.

Hi,
I have quite the same problem : Matter Server keeps on booting/stopping with code 137. Hereafter the log with the end of the previous start and the new start :
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started

e[34m-----------------------------------------------------------e[0m
e[34m Add-on: Matter Servere[0m
e[34m Matter WebSocket Server for Home Assistant Matter support.e[0m
e[34m-----------------------------------------------------------e[0m
e[34m Add-on version: 7.0.0e[0m
e[32m You are running the latest version of this add-on.e[0m
e[34m System: Home Assistant OS 14.2 (aarch64 / qemuarm-64)e[0m
e[34m Home Assistant Core: 2025.1.4e[0m
e[34m Home Assistant Supervisor: 2024.12.3e[0m
e[34m-----------------------------------------------------------e[0m
e[34m Please, share the above information when looking for helpe[0m
e[34m or support in, e.g., GitHub, forums or the Discord chat.e[0m
e[34m-----------------------------------------------------------e[0m
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[13:48:18] INFO: e[32mStarting Matter Server…e[0m
s6-rc: info: service legacy-services successfully started
[13:48:19] INFO: e[32mUsing ‘enp0s3’ as primary network interface.e[0m
[13:48:20] INFO: e[32mSuccessfully send discovery information to Home Assistant.e[0m
[12:48:22] WARNING: e[33mmatter-server service exited with code 137 (by signal 9).e[0m
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service matter-server: stopping
s6-rc: info: service matter-server successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Any idea ? Thanks.

Hi,
Problem seems to be fixed by increasing RAM.
HA runs on a VM ; original RAM dedicated to this machine was 1GB. Since upgrade to 4GB, Matter Server is stable.
Flat6