Homeaissitant stürzt immer wieder ab

Dano3112 · 9. Mai 2025 um 07:00

Hallo zusammen,

leider hab ich seit mehreren Wochen das Phänomen, dass mein Host System nicht mehr erreichbar ist.
Ich muss von Hand die Hardware neustarten.
Ich betreibt Homeassistant auf einem Lenovo Thinkcentre M715q mit 8 GM Ram und einer 200GB NVME SSD.
Da auf dem System noch Frigate läuft nutze ich einen Coral TPU.
Hab unterandern Raspberry Matic, ZHA und Mosquitto Broker als Addon laufen.

Kann mir jenamd ggf helfen das Problem in Griff zu bekommen.
Aus den Systemlog werd ich leider nicht schlau.

Grüße

der_Micro · 9. Mai 2025 um 17:09

Nunja, wenn du das Log hier reinhängen würdest, dann andere schon . Geht der Lenovo aus oder freezt er? (Monitor ranhängen)
Ansonsten könnte auch der RAM ein Problem haben oder die SSD, wie ist denn HA installiert?

totow · 9. Mai 2025 um 17:15

Moin,
willkommen in der Community.

Was ist dein Host System? Proxmox?

finde ich ein bisschen wenig für Host System, HA und Addons.
wie viel hast du HA zugeordnet?

Dano3112 · 13. Mai 2025 um 07:02

Am Ram kann es nicht liegen. habe das Hostsystem ausgetauscht.
gleiches Problem.

hier das Log.
da das system immer noch abstürzt,
Protokolle

2025-05-13 06:56:56.513 homeassistant systemd-resolved[462]: Detected conflict on homeassistant36\032\0911679bfa84d1046739db0feb51b133ed1\093._workstation._tcp.local IN SRV 0 0 0 homeassistant36.local

2025-05-13 06:56:56.513 homeassistant systemd-resolved[462]: Detected conflict on homeassistant36\032\0911679bfa84d1046739db0feb51b133ed1\093._workstation._tcp.local IN TXT ""

2025-05-13 06:56:56.513 homeassistant systemd-resolved[462]: Detected conflict on homeassistant36.local IN A 192.168.32.172

2025-05-13 06:56:56.514 homeassistant systemd-resolved[462]: Hostname conflict, changing published hostname from 'homeassistant36' to 'homeassistant37'.

2025-05-13 06:56:56.701 homeassistant NetworkManager[476]: <info> [1747119416.7016] audit: op="connection-update" uuid="1d8ee89a-a678-31d3-b99d-99e4631ae811" name="Supervisor enp1s0f0" args="connection.mdns,connection.timestamp" pid=6711 uid=0 result="success"

2025-05-13 06:56:56.733 homeassistant NetworkManager[476]: <info> [1747119416.7338] device (enp1s0f0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')

2025-05-13 06:56:56.734 homeassistant NetworkManager[476]: <info> [1747119416.7342] manager: NetworkManager state is now DISCONNECTING

2025-05-13 06:56:56.736 homeassistant NetworkManager[476]: <info> [1747119416.7360] audit: op="connection-deactivate" uuid="1d8ee89a-a678-31d3-b99d-99e4631ae811" name="Supervisor enp1s0f0" pid=6724 uid=0 result="success"

2025-05-13 06:56:56.750 homeassistant systemd-resolved[462]: Detected conflict on homeassistant37\032\0911679bfa84d1046739db0feb51b133ed1\093._workstation._tcp.local IN SRV 0 0 0 homeassistant37.local

2025-05-13 06:56:56.750 homeassistant systemd-resolved[462]: Detected conflict on homeassistant37\032\0911679bfa84d1046739db0feb51b133ed1\093._workstation._tcp.local IN TXT ""

2025-05-13 06:56:56.750 homeassistant systemd-resolved[462]: Detected conflict on homeassistant37.local IN A 192.168.32.172

2025-05-13 06:56:56.750 homeassistant systemd-resolved[462]: Hostname conflict, changing published hostname from 'homeassistant37' to 'homeassistant40'.

2025-05-13 06:56:56.756 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-05-13 06:56:56.767 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-05-13 06:56:56.767 homeassistant NetworkManager[476]: <info> [1747119416.7679] device (enp1s0f0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')

2025-05-13 06:56:56.769 homeassistant NetworkManager[476]: <info> [1747119416.7694] dhcp4 (enp1s0f0): canceled DHCP transaction

2025-05-13 06:56:56.769 homeassistant NetworkManager[476]: <info> [1747119416.7695] dhcp4 (enp1s0f0): activation: beginning transaction (timeout in 45 seconds)

2025-05-13 06:56:56.769 homeassistant NetworkManager[476]: <info> [1747119416.7695] dhcp4 (enp1s0f0): state changed no lease

2025-05-13 06:56:56.772 homeassistant systemd-resolved[462]: enp1s0f0: Bus client reset search domain list.

2025-05-13 06:56:56.773 homeassistant systemd-resolved[462]: enp1s0f0: Bus client set default route setting: no

2025-05-13 06:56:56.780 homeassistant systemd-resolved[462]: enp1s0f0: Bus client reset DNS server list.

2025-05-13 06:56:56.810 homeassistant NetworkManager[476]: <info> [1747119416.8091] manager: NetworkManager state is now DISCONNECTED

2025-05-13 06:56:56.842 homeassistant NetworkManager[476]: <info> [1747119416.8425] agent-manager: agent[43c1c99baf306605,:1.67/nmcli-connect/0]: agent registered

2025-05-13 06:56:56.843 homeassistant NetworkManager[476]: <info> [1747119416.8438] device (enp1s0f0): Activation: starting connection 'Supervisor enp1s0f0' (1d8ee89a-a678-31d3-b99d-99e4631ae811)

2025-05-13 06:56:56.844 homeassistant NetworkManager[476]: <info> [1747119416.8439] audit: op="connection-activate" uuid="1d8ee89a-a678-31d3-b99d-99e4631ae811" name="Supervisor enp1s0f0" pid=6736 uid=0 result="success"

2025-05-13 06:56:56.844 homeassistant NetworkManager[476]: <info> [1747119416.8440] device (enp1s0f0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

2025-05-13 06:56:56.844 homeassistant NetworkManager[476]: <info> [1747119416.8444] manager: NetworkManager state is now CONNECTING

2025-05-13 06:56:56.844 homeassistant NetworkManager[476]: <info> [1747119416.8446] device (enp1s0f0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

2025-05-13 06:56:56.845 homeassistant NetworkManager[476]: <info> [1747119416.8454] device (enp1s0f0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')

2025-05-13 06:56:56.846 homeassistant NetworkManager[476]: <info> [1747119416.8466] dhcp4 (enp1s0f0): activation: beginning transaction (timeout in 45 seconds)

2025-05-13 06:56:56.850 homeassistant NetworkManager[476]: <info> [1747119416.8495] dhcp4 (enp1s0f0): state changed new lease, address=192.168.32.172

2025-05-13 06:56:56.850 homeassistant NetworkManager[476]: <info> [1747119416.8507] policy: set 'Supervisor enp1s0f0' (enp1s0f0) as default for IPv4 routing and DNS

2025-05-13 06:56:56.853 homeassistant systemd-resolved[462]: enp1s0f0: Bus client set MulticastDNS setting: resolve

2025-05-13 06:56:56.856 homeassistant systemd-resolved[462]: enp1s0f0: Bus client set search domain list to: iot.simon.local

2025-05-13 06:56:56.857 homeassistant systemd-resolved[462]: enp1s0f0: Bus client set default route setting: yes

2025-05-13 06:56:56.859 homeassistant systemd-resolved[462]: enp1s0f0: Bus client set DNS server list to: 192.168.32.1

2025-05-13 06:56:56.859 homeassistant NetworkManager[476]: <info> [1747119416.8596] device (enp1s0f0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')

2025-05-13 06:56:56.864 homeassistant NetworkManager[476]: <info> [1747119416.8640] device (enp1s0f0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')

2025-05-13 06:56:56.864 homeassistant NetworkManager[476]: <info> [1747119416.8645] device (enp1s0f0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')

2025-05-13 06:56:56.865 homeassistant NetworkManager[476]: <info> [1747119416.8656] manager: NetworkManager state is now CONNECTED_SITE

2025-05-13 06:56:56.867 homeassistant NetworkManager[476]: <info> [1747119416.8675] device (enp1s0f0): Activation: successful, device activated.

2025-05-13 06:56:56.932 homeassistant NetworkManager[476]: <info> [1747119416.9322] manager: NetworkManager state is now CONNECTED_GLOBAL

2025-05-13 06:56:58.594 homeassistant dockerd[604]: time="2025-05-13T06:56:58.592376225Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:56460" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:56460->172.30.32.3:53: read: connection refused" question=";www.google-analytics.com.\tIN\t AAAA"

2025-05-13 06:56:58.594 homeassistant dockerd[604]: time="2025-05-13T06:56:58.594431831Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:60662" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:60662->172.30.32.3:53: read: connection refused" question=";www.google-analytics.com.\tIN\t A"

2025-05-13 06:56:58.595 homeassistant dockerd[604]: time="2025-05-13T06:56:58.595390507Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:32982" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:32982->172.30.32.3:53: read: connection refused" question=";www.google-analytics.com.\tIN\t AAAA"

2025-05-13 06:56:58.595 homeassistant dockerd[604]: time="2025-05-13T06:56:58.595547286Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:57927" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:57927->172.30.32.3:53: read: connection refused" question=";www.google-analytics.com.\tIN\t A"

2025-05-13 06:56:58.596 homeassistant dockerd[604]: time="2025-05-13T06:56:58.596072907Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:36852" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:36852->172.30.32.3:53: read: connection refused" question=";www.google-analytics.com.local.hass.io.\tIN\t A"

2025-05-13 06:56:58.596 homeassistant dockerd[604]: time="2025-05-13T06:56:58.596072977Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:50512" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:50512->172.30.32.3:53: read: connection refused" question=";www.google-analytics.com.local.hass.io.\tIN\t AAAA"

2025-05-13 06:56:59.959 homeassistant systemd[1]: docker-f8fcfaba7346177d6d4041ce2fd4d27d4dcb33cdc26098be94360231f2df74e0.scope: Deactivated successfully.

2025-05-13 06:56:59.973 homeassistant dockerd[604]: time="2025-05-13T06:56:59.972747460Z" level=info msg="ignoring event" container=f8fcfaba7346177d6d4041ce2fd4d27d4dcb33cdc26098be94360231f2df74e0 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

2025-05-13 06:57:00.012 homeassistant kernel: hassio: port 4(veth6acd6e0) entered disabled state

2025-05-13 06:57:00.012 homeassistant kernel: veth9b99e85: renamed from eth0

2025-05-13 06:57:00.036 homeassistant NetworkManager[476]: <info> [1747119420.0366] manager: (veth9b99e85): new Veth device (/org/freedesktop/NetworkManager/Devices/17)

2025-05-13 06:57:00.038 homeassistant kernel: hassio: port 4(veth6acd6e0) entered disabled state

2025-05-13 06:57:00.039 homeassistant kernel: veth6acd6e0 (unregistering): left allmulticast mode

2025-05-13 06:57:00.039 homeassistant kernel: veth6acd6e0 (unregistering): left promiscuous mode

2025-05-13 06:57:00.039 homeassistant kernel: hassio: port 4(veth6acd6e0) entered disabled state

2025-05-13 06:57:00.147 homeassistant systemd[1]: Started libcontainer container f8fcfaba7346177d6d4041ce2fd4d27d4dcb33cdc26098be94360231f2df74e0.

2025-05-13 06:57:00.161 homeassistant systemd-resolved[462]: System hostname changed to 'homeassistant'.

2025-05-13 06:57:00.169 homeassistant kernel: hassio: port 4(vethb0176e8) entered blocking state

2025-05-13 06:57:00.169 homeassistant kernel: hassio: port 4(vethb0176e8) entered disabled state

2025-05-13 06:57:00.169 homeassistant kernel: vethb0176e8: entered allmulticast mode

2025-05-13 06:57:00.169 homeassistant kernel: vethb0176e8: entered promiscuous mode

2025-05-13 06:57:00.169 homeassistant NetworkManager[476]: <info> [1747119420.1698] manager: (vethb0176e8): new Veth device (/org/freedesktop/NetworkManager/Devices/18)

2025-05-13 06:57:00.198 homeassistant kernel: eth0: renamed from veth1839fc9

2025-05-13 06:57:00.198 homeassistant kernel: hassio: port 4(vethb0176e8) entered blocking state

2025-05-13 06:57:00.198 homeassistant kernel: hassio: port 4(vethb0176e8) entered forwarding state

2025-05-13 06:57:00.198 homeassistant NetworkManager[476]: <info> [1747119420.1986] device (vethb0176e8): carrier: link connected

2025-05-13 06:57:02.597 homeassistant dockerd[604]: time="2025-05-13T06:57:02.597225631Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:46054" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:46054->172.30.32.3:53: i/o timeout" question=";www.google-analytics.com.local.hass.io.\tIN\t AAAA"

2025-05-13 06:57:02.597 homeassistant dockerd[604]: time="2025-05-13T06:57:02.597242693Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.30.33.3:34210" dns-server="udp:172.30.32.3:53" error="read udp 172.30.33.3:34210->172.30.32.3:53: i/o timeout" question=";www.google-analytics.com.local.hass.io.\tIN\t A"

2025-05-13 06:57:04.259 homeassistant kernel: usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd

2025-05-13 06:57:05.943 homeassistant kernel: usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd

2025-05-13 06:57:05.961 homeassistant kernel: usb 3-3: LPM exit latency is zeroed, disabling LPM.

2025-05-13 06:57:05.962 homeassistant kernel: usb 3-3: device firmware changed

2025-05-13 06:57:05.962 homeassistant kernel: usb 3-3: USB disconnect, device number 2

2025-05-13 06:57:06.343 homeassistant kernel: usb 3-3: new SuperSpeed USB device number 3 using xhci_hcd

2025-05-13 06:57:06.354 homeassistant kernel: usb 3-3: LPM exit latency is zeroed, disabling LPM.

2025-05-13 06:57:06.356 homeassistant kernel: usb 3-3: New USB device found, idVendor=18d1, idProduct=9302, bcdDevice= 1.00

2025-05-13 06:57:06.357 homeassistant kernel: usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0

2025-05-13 06:57:06.942 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-05-13 06:57:15.982 homeassistant systemd[1]: Starting Bluetooth service...

2025-05-13 06:57:16.136 homeassistant bluetoothd[7742]: Bluetooth daemon 5.79

2025-05-13 06:57:16.136 homeassistant systemd[1]: Started Bluetooth service.

2025-05-13 06:57:16.136 homeassistant bluetoothd[7742]: Starting SDP server

2025-05-13 06:57:16.139 homeassistant kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3

2025-05-13 06:57:16.139 homeassistant kernel: Bluetooth: BNEP filters: protocol multicast

2025-05-13 06:57:16.139 homeassistant kernel: Bluetooth: BNEP socket layer initialized

2025-05-13 06:57:16.139 homeassistant bluetoothd[7742]: src/plugin.c:init_plugin() System does not support ccp plugin

2025-05-13 06:57:16.139 homeassistant bluetoothd[7742]: Bluetooth management interface 1.23 initialized

2025-05-13 06:57:16.168 homeassistant systemd[1]: Starting Hostname Service...

2025-05-13 06:57:16.386 homeassistant systemd[1]: Started Hostname Service.

2025-05-13 06:57:24.205 homeassistant systemd[1]: Starting Time & Date Service...

2025-05-13 06:57:24.437 homeassistant systemd[1]: Started Time & Date Service.

2025-05-13 06:57:28.521 homeassistant kernel: amdgpu: pp_dpm_get_mclk_od was not implemented.

2025-05-13 06:57:28.521 homeassistant kernel: amdgpu: pp_dpm_get_sclk_od was not implemented.

2025-05-13 06:57:50.443 homeassistant systemd-timesyncd[588]: Network configuration changed, trying to establish connection.

2025-05-13 06:57:50.447 homeassistant systemd-timesyncd[588]: Contacted time server 162.159.200.1:123 (time.cloudflare.com).

2025-05-13 06:57:50.452 homeassistant systemd[1]: Started Journal Gateway Service.

2025-05-13 06:57:54.200 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.

2025-05-13 06:57:54.474 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.

by tarag: Protokoll als vorformatierter Text formatiert

Dano3112 · 13. Mai 2025 um 07:03

moin,
hab kein Proxmox am laufen.
das hier hab ich am laufen.

73ymw · 13. Mai 2025 um 07:40

In den Logs ist ziemliches durcheinander mit deinem LAN-Anschluss. Betreibst du weitere HA-Intsanzen in deinem Netzwerk? Irgendetwas scheint zu Konflikten zu führen. Was passiert denn, wenn HA “abgestürzt” ist und du dann nur das LAN-Kabel aus- und wieder einsteckst? Geht es dann wieder?
Hast du in deinem Router mehrere HA-Verbindungen aufgelistet?

Zum testen kannst du HA eine feste IP zuweisen.

Was mich auch wundert: Das Netzwerkinterface wird periodisch getrennt und neu verbunden.

Dano3112 · 13. Mai 2025 um 07:48

Hi,
nein ich hab nur ein Home-Assistant.

die Idee mit dem LAN kabel kann ich mal testen wenn er abstürzt.

ich hatte mal ein Bildschirm dran gehaben nachdem er abgeschmiert war. hatte nur ein Schwarzen Bildschirm.

73ymw · 13. Mai 2025 um 07:48

Unter welcher IP ist dein HA erreichbar?

Dano3112 · 13. Mai 2025 um 07:49

das ist die IP Adresse. 192.168.32.172

73ymw · 13. Mai 2025 um 07:50

Wenn die IP fest vergeben ist, könntest du einmal eine andere IP vergeben und schauen, ob diese dann keine Konflikte mehr verursacht.

Dano3112 · 13. Mai 2025 um 14:54

okay werde ich direkt mal testen.

Hi,
Hab es ausprobiert. Kein Erfolg (lan Kabel ziehen.)
Bildschirm ist schwarz

by HarryP: Zusammenführung Doppelpost (bei Änderungen oder hinzufügen von Inhalten bitte die „Bearbeitungsfunktion“ anstatt „Antworten“ zu nutzen)