search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.02k stars 29.09k forks source link

Matter Server always shutdown #121527

Closed QuentinCaldeira-eaton closed 1 week ago

QuentinCaldeira-eaton commented 1 week ago

The problem

Hi, I don't know why, but suddenly I can't have my Matter Server working anymore. I used it during 4 months without issues. I joined logs.

What version of Home Assistant Core has the issue?

core-2024-7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter Server

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

-----------------------------------------------------------
 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
[04:10:39] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[04:10:41] INFO: Using 'end0' as primary network interface.
[04:10:41] INFO: Successfully send discovery information to Home Assistant.
2024-04-30 04:10:45.215 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2024-04-30 04:10:45.217 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1714443045.289450][126:126] CHIP:CTL: Setting attestation nonce to random value
[1714443045.290188][126:126] CHIP:CTL: Setting CSR nonce to random value
[1714443045.292163][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1714443045.292850][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-j11MKJ)
[1714443045.293018][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1714443045.293744][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1714443045.294263][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1714443045.294390][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1714443045.295110][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-m3PtXK)
[1714443045.296003][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1714443045.296052][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 59 (0x3B)
[1714443045.296966][126:126] CHIP:DL: Got Ethernet interface: end0
[1714443045.297522][126:126] CHIP:DL: Found the primary Ethernet interface:end0
[1714443045.298086][126:126] CHIP:DL: Got WiFi interface: wlan0
[1714443045.298139][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-04-30 04:10:45.299 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-04-30 04:10:45.300 (MainThread) WARNING [PersistentStorage] Loading configuration from /data/chip.json...
2024-04-30 04:10:45.488 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
2024-04-30 04:10:45.488 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
2024-04-30 04:10:45.491 (MainThread) WARNING [CertificateAuthority] Loading fabric admins from storage...
2024-04-30 04:10:45.491 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-04-30 04:10:45.493 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-04-30 04:10:45.501 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-04-30 04:10:45.509 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2024-04-30 04:10:45.509 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-04-30 04:10:45.999 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 487 ms, for event type 2
2024-04-30 04:10:46.011 (MainThread) INFO [matter_server.server.device_controller] Loaded 3 nodes from stored configuration
2024-04-30 04:10:46.026 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-04-30 04:10:46.036 (MainThread) INFO [matter_server.server.vendor_info] Loaded 185 vendors from storage.
2024-04-30 04:10:46.037 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-04-30 04:10:52.062 (MainThread) ERROR [matter_server.server.vendor_info] Unable to fetch vendor info from DCL: Cannot connect to host on.dcl.csa-iot.org:443 ssl:default [Temporary failure in name resolution]
2024-04-30 04:10:52.064 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
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
2024-04-30 04:13:59.931 (MainThread) WARNING [aiorun] Stopping the loop
2024-04-30 04:13:59.932 (MainThread) INFO [aiorun] Entering shutdown phase.
2024-04-30 04:13:59.932 (MainThread) INFO [aiorun] Executing provided shutdown_callback.
2024-04-30 04:13:59.933 (MainThread) INFO [matter_server.server.server] Stopping the Matter Server...
2024-04-30 04:13:59.941 (MainThread) INFO [matter_server.server.stack] Shutting down the Matter stack...
2024-04-30 04:13:59.942 (MainThread) CHIP_ERROR [chip.native.CTL] Shutting down the stack...
2024-04-30 04:13:59.946 (MainThread) CHIP_ERROR [chip.native.DL] Inet Layer shutdown
2024-04-30 04:13:59.946 (MainThread) CHIP_ERROR [chip.native.DL] BLE shutdown
s6-rc: info: service legacy-cont-init successfully stopped
2024-04-30 04:13:59.946 (MainThread) CHIP_ERROR [chip.native.DL] System Layer shutdown
s6-rc: info: service fix-attrs: stopping
2024-04-30 04:13:59.949 (MainThread) INFO [aiorun] Waiting for executor shutdown.
2024-04-30 04:13:59.950 (MainThread) INFO [aiorun] Shutting down async generators
2024-04-30 04:13:59.950 (MainThread) INFO [aiorun] Closing the loop.
2024-04-30 04:13:59.951 (MainThread) INFO [aiorun] Leaving. Bye!
s6-rc: info: service fix-attrs successfully stopped
[02:14:00] INFO: matter-server service exited with code 0 (by signal 0).
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 s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle
s6-rc: fatal: unable to take locks: No such file or directory
s6-linux-init-shutdownd: warning: /run/s6/basedir/scripts/rc.shutdown exited 111
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/banner/type: must be oneshot, longrun, or bundle

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `matter` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign matter` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

matter documentation matter source (message by IssueLinks)

marcelveldt commented 1 week ago

What version of the add-on are you running ? Looks like something is corrupted, do you have enough storage space ?

QuentinCaldeira-eaton commented 1 week ago

Hi, it seems that a corrupted device (a development board) broke it. After that I removed and re install Matter Server. Matter Client complains that Server and Client aren't on the same version anymore. After joining the Beta Channel, seems to be good