HA crashed with no obvious reason

aaroneisele55 · January 9, 2024, 4:41pm

Hello,

I have Home Assistant OS installed on a Raspberry Pi 4 and it has been running flawlessly since several months.

Then, it suddenly crashed with no obvious reason and my only error in the logs is this one:

Logger: async_upnp_client.ssdp
Source: components/ssdp/__init__.py:350
First occurred: 17:14:41 (1 occurrences)
Last logged: 17:14:41

Received error: [Errno 99] Address not available, transport: <_SelectorDatagramTransport fd=25 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=25, family=10, type=2, proto=0, laddr=('::', 46583, 0, 0)>

What is the cause for that and how can I prevent it from happening again?

Best regards
Aaron Eisele

MaxK · January 9, 2024, 7:57pm

Is it this:

github.com/home-assistant/core

SSDP | Received error: [Errno 99] Address not available

opened 05:33PM - 25 Jan 23 UTC

closed 09:14PM - 30 Jan 23 UTC

finalsabbath

integration: ssdp

### The problem ssdp fails to start with this message ``` Logger: async_u…pnp_client.ssdp Source: components/ssdp/__init__.py:381 First occurred: January 24, 2023 at 8:35:38 PM (1 occurrences) Last logged: January 24, 2023 at 8:35:38 PM Received error: [Errno 99] Address not available, transport: <_SelectorDatagramTransport fd=16 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=16, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 57409, 0, 0)> ``` ``` Logger: homeassistant.setup Source: components/ssdp/__init__.py:711 First occurred: January 24, 2023 at 8:35:39 PM (1 occurrences) Last logged: January 24, 2023 at 8:35:39 PM Error during setup of component ssdp Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 256, in _async_setup_component result = await task File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 223, in async_setup await server.async_start() File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 731, in async_start await self._async_start_upnp_servers() File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 787, in _async_start_upnp_servers http_port = await _async_find_next_available_port(source) File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 711, in _async_find_next_available_port test_socket.bind(addr) OSError: [Errno 99] Address not available ``` Seems similar to https://github.com/home-assistant/core/issues/81459 but only a single message(not flood) Deployed to kubernetes(k3s) Was previously working with same configuration though not sure what version as I only noticed this around the end of the last year when I went to set up some new devices and re-vamp my setup ### What version of Home Assistant Core has the issue? core-2023.2.0.dev20230124 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Container ### Integration causing the issue ssdp ### Link to integration documentation on our website https://www.home-assistant.io/integrations/ssdp/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ssdp: ``` ### Anything in the logs that might be useful for us? ```txt debug logs 2023-01-24 20:35:37.832 DEBUG (MainThread) [homeassistant.components.network.network] Adapters: [{'name': 'lo', 'index': 1, 'enabled': False, 'auto': False, 'default': False, 'ipv4': [{'address': '127.0.0.1', 'network_prefix': 8}], 'ipv6': [{'address': '::1', 'flowinfo': 0, 'scope_id': 0, 'network_prefix': 128}]}, {'name': 'eth0', 'index': 3, 'enabled': True, 'auto': True, 'default': True, 'ipv4': [{'address': '10.42.0.216', 'network_prefix': 24}], 'ipv6': [{'address': 'fe80::90d7:58ff:fe77:46bf', 'flowinfo': 0, 'scope_id': 3, 'network_prefix': 64}]}] 2023-01-24 20:35:38.964 DEBUG (MainThread) [async_upnp_client.ssdp] Creating socket, source: (<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_DGRAM: 2>, 17, 'fe80::90d7:58ff:fe77:46bf%3', ('fe80::90d7:58ff:fe77:46bf', 0, 0, 3)), target: (<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_DGRAM: 2>, 17, 'ff02::c%3', ('ff02::c', 1900, 0, 3)) 2023-01-24 20:35:38.964 DEBUG (MainThread) [async_upnp_client.ssdp] Creating socket, source: (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_DGRAM: 2>, 17, '10.42.0.216', ('10.42.0.216', 0)), target: (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_DGRAM: 2>, 17, '239.255.255.250', ('239.255.255.250', 1900)) 2023-01-24 20:35:38.965 DEBUG (MainThread) [async_upnp_client.ssdp] Connection made, transport: <_SelectorDatagramTransport fd=14 read=idle write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=14, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 1900, 0, 0)> 2023-01-24 20:35:38.965 DEBUG (MainThread) [async_upnp_client.ssdp] Connection made, transport: <_SelectorDatagramTransport fd=15 read=idle write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=15, family=AddressFamily.AF_INET, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('0.0.0.0', 1900)> 2023-01-24 20:35:38.980 DEBUG (MainThread) [async_upnp_client.ssdp] Creating socket, source: (<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_DGRAM: 2>, 17, 'fe80::90d7:58ff:fe77:46bf%3', ('fe80::90d7:58ff:fe77:46bf', 0, 0, 3)), target: (<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_DGRAM: 2>, 17, 'ff02::c%3', ('ff02::c', 1900, 0, 3)) 2023-01-24 20:35:38.981 DEBUG (MainThread) [async_upnp_client.ssdp] Creating socket, source: (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_DGRAM: 2>, 17, '10.42.0.216', ('10.42.0.216', 0)), target: (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_DGRAM: 2>, 17, '239.255.255.250', ('239.255.255.250', 1900)) 2023-01-24 20:35:38.981 DEBUG (MainThread) [async_upnp_client.ssdp] Connection made, transport: <_SelectorDatagramTransport fd=16 read=idle write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=16, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 0, 0, 0)> 2023-01-24 20:35:38.981 DEBUG (MainThread) [async_upnp_client.ssdp] Connection made, transport: <_SelectorDatagramTransport fd=17 read=idle write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=17, family=AddressFamily.AF_INET, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('0.0.0.0', 0)> 2023-01-24 20:35:38.981 DEBUG (MainThread) [async_upnp_client.ssdp] Sending SSDP packet, transport: <_SelectorDatagramTransport fd=16 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=16, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 0, 0, 0)>, target: ('FF02::C', 1900, 0, 3) 2023-01-24 20:35:38.982 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 99] Address not available, transport: <_SelectorDatagramTransport fd=16 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=16, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 57409, 0, 0)> 2023-01-24 20:35:38.987 DEBUG (MainThread) [async_upnp_client.ssdp] Sending SSDP packet, transport: <_SelectorDatagramTransport fd=17 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=17, family=AddressFamily.AF_INET, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('0.0.0.0', 0)>, target: ('239.255.255.250', 1900) 2023-01-24 20:35:38.987 DEBUG (MainThread) [async_upnp_client.ssdp] Sending SSDP packet, transport: <_SelectorDatagramTransport fd=17 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=17, family=AddressFamily.AF_INET, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('0.0.0.0', 54056)>, target: ('255.255.255.255', 1900) 2023-01-24 20:35:39.057 ERROR (MainThread) [homeassistant.setup] Error during setup of component ssdp Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 256, in _async_setup_component result = await task File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 223, in async_setup await server.async_start() File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 731, in async_start await self._async_start_upnp_servers() File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 787, in _async_start_upnp_servers http_port = await _async_find_next_available_port(source) File "/usr/src/homeassistant/homeassistant/components/ssdp/__init__.py", line 711, in _async_find_next_available_port test_socket.bind(addr) OSError: [Errno 99] Address not available ``` ### Additional information Installation type flags as unknown for some reason ![image](https://user-images.githubusercontent.com/40742722/214638241-306711e3-5e69-46d0-ab4f-8894287aad4e.png) Did try same kubernetes deployment with no config/storage/etc and had same issue. Deployment ``` apiVersion: apps/v1 kind: Deployment metadata: name: home-assistant labels: app: home-assistant namespace: home-assistant spec: replicas: 1 selector: matchLabels: app: home-assistant template: metadata: labels: app: home-assistant spec: volumes: - name: home-assistant-nfs persistentVolumeClaim: claimName: home-assistant-data - name: media-nfs persistentVolumeClaim: claimName: media containers: - name: home-assistant image: homeassistant/home-assistant:dev imagePullPolicy: Always ports: - containerPort: 8123 env: - name: TZ value: "America/New_York" - name: PUID value: "1029" - name: PGID value: "100" volumeMounts: - mountPath: "/config" name: home-assistant-nfs - mountPath: "/media" name: media-nfs lifecycle: postStart: exec: command: ["/bin/sh", "-c", wget -O - https://get.hacs.xyz | bash -] ```

aaroneisele55 · January 11, 2024, 4:31pm

It could be this, but what can I do now?
Should I wait for 2023.2 to be released?
This is my production HA install which is too important for me to use a beta version as I want to avoid any unnecessary downtime.
Also, I recently improved the power supply of my RPI4 as I constantly received Undervoltage errors in my logs.

MaxK · January 11, 2024, 5:08pm

What versions of Home Assistant are you running (Settings → About)?

aaroneisele55 · January 11, 2024, 6:27pm

I’m running version 2024.1.2

MaxK · January 11, 2024, 6:52pm

You are at the current release of Core but OS is currently at 11.4 so, you should already have the fix that was referenced in GitHub.

How many times has the async_upnp_client.ssdp appeared in your logs?
Did the actual time of the crash match the actual time in the log (17:14:41)?
Were there any changes to your network (the async_upnp_client.ssdp error looks like a network issue)?

I’m more inclined to believe that the crash may have been caused by your under voltage errors - not the async_upnp_client.ssdp error.

aaroneisele55 · January 11, 2024, 7:10pm

As far as I know, it appeared only once but I don’t have the full logs as the Pi and HA were restarted since then (I upgraded the power supply, so no Undervoltage anymore)
I took notes on the crash and from those I saw that it matches the time that I noticed the crash
it may have been caused by my network switch (the one that connects the Pi to the rest of the network) that I think locks itself up sometimes and then needs to be powercycled.