HA Suddenly dead

sender · May 12, 2025, 9:13pm

Suddenly all was dead… I got:

Home Assistant observer
Supervisor:	Disconnected
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 fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
[20:27:14] INFO: Using udev information from host
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
[20:27:14] INFO: Starting local supervisor watchdog...
s6-rc: info: service legacy-services successfully started
2025-05-12 20:27:14.984 INFO (MainThread) [__main__] Initializing Supervisor setup
2025-05-12 20:27:15.035 INFO (MainThread) [supervisor.coresys] Setting up coresys for machine: qemux86-64
2025-05-12 22:27:15.037 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/amd64-hassio-supervisor with version 2025.05.0
2025-05-12 22:27:15.037 INFO (MainThread) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network
2025-05-12 22:27:15.071 INFO (SyncWorker_2) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/amd64-hassio-supervisor:2025.04.1']
2025-05-12 22:27:15.418 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state initialize
2025-05-12 22:27:15.419 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-05-12 22:27:15.420 INFO (MainThread) [__main__] Setting up Supervisor
Traceback (most recent call last):
  File "", line 198, in _run_module_as_main
  File "", line 88, in _run_code
  File "/usr/src/supervisor/supervisor/__main__.py", line 67, in 
    loop.run_until_complete(coresys.core.setup())
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 719, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/usr/src/supervisor/supervisor/core.py", line 138, in setup
    await self.coresys.init_websession()
  File "/usr/src/supervisor/supervisor/coresys.py", line 124, in init_websession
    resolver = aiohttp.AsyncResolver()
  File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 96, in __init__
    self._resolver = aiodns.DNSResolver(*args, **kwargs)
                     ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiodns/__init__.py", line 67, in __init__
    self._channel = pycares.Channel(event_thread=True,
                    ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
                                    timeout=timeout,
                                    ^^^^^^^^^^^^^^^^
                                    **kwargs)
                                    ^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pycares/__init__.py", line 422, in __init__
    raise AresError('Failed to initialize c-ares channel')
pycares.AresError: Failed to initialize c-ares channel
[20:27:15] WARNING: Halt Supervisor
[20:27:15] INFO: Supervisor restart after closing
s6-rc: info: service legacy-services: stopping
[20:27:15] INFO: Watchdog restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
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
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 fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
[20:27:24] INFO: Using udev information from host
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
[20:27:24] INFO: Starting local supervisor watchdog...
s6-rc: info: service legacy-services successfully started
2025-05-12 20:27:24.528 INFO (MainThread) [__main__] Initializing Supervisor setup
2025-05-12 20:27:24.559 INFO (MainThread) [supervisor.coresys] Setting up coresys for machine: qemux86-64
2025-05-12 22:27:24.561 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/amd64-hassio-supervisor with version 2025.05.0
2025-05-12 22:27:24.570 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state initialize
2025-05-12 22:27:24.571 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-05-12 22:27:24.571 INFO (MainThread) [__main__] Setting up Supervisor
Traceback (most recent call last):
  File "", line 198, in _run_module_as_main
  File "", line 88, in _run_code
  File "/usr/src/supervisor/supervisor/__main__.py", line 67, in 
    loop.run_until_complete(coresys.core.setup())
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 719, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/usr/src/supervisor/supervisor/core.py", line 138, in setup
    await self.coresys.init_websession()
  File "/usr/src/supervisor/supervisor/coresys.py", line 124, in init_websession
    resolver = aiohttp.AsyncResolver()
  File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 96, in __init__
    self._resolver = aiodns.DNSResolver(*args, **kwargs)
                     ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiodns/__init__.py", line 67, in __init__
    self._channel = pycares.Channel(event_thread=True,
                    ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
                                    timeout=timeout,
                                    ^^^^^^^^^^^^^^^^
                                    **kwargs)
                                    ^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pycares/__init__.py", line 422, in __init__
    raise AresError('Failed to initialize c-ares channel')
pycares.AresError: Failed to initialize c-ares channel
[20:27:24] WARNING: Halt Supervisor
[20:27:24] INFO: Supervisor restart after closing
s6-rc: info: service legacy-services: stopping
[20:27:24] INFO: Watchdog restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
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
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 fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
[20:27:33] INFO: Using udev information from host
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
[20:27:33] INFO: Starting local supervisor watchd

I have HAOS

Core2025.5.1
Supervisor2025.05.0
Operating System15.2
Frontend20250509.0

And when going via cli doing “ha host reboot” I got:
“dial tcp ip adress coonect: no route to host” (sort of).

Only thing I could do was a hard power donw and up…

never had this before… what is wrong possibly?

Sir_Goodenough · May 12, 2025, 11:37pm

Hello sender,

Well my first 2 questions are are you running a pi based server with an SD card? If so is the card bad.
Are you running PiHole, AdGuard, or another DNS blocker? If so look there…

sender · May 13, 2025, 3:12am

As a VM on esxi with an enterprise grade ssd…

ShadNex · May 13, 2025, 4:29am

I woke up this morning to the same scenario. Supervisor was down, only an external reboot of the VM helped.
I found this GitHub issue and according to them, it is caused by the Octoprint Integration when it is enabled, but the Octoprint host itself is offline. This is the case for me, maybe you have the same? I have now disabled the Integration and will keep an eye on it.

github.com/home-assistant/core

Failed to initialize c-ares channel

opened 08:22AM - 08 May 25 UTC

closed 08:43PM - 08 May 25 UTC

brhahlen

### The problem I'm seeing this issue on multiple integrations: Sonos, Forecast… Solar (#144453), Tronity, TeamTracker, SmartThings, and Unifi. They cannot be setup as a result of this. ### What version of Home Assistant Core has the issue? core-2025.5.0 ### What was the last working version of Home Assistant Core? core-2025.4.x ### What type of installation are you running? Home Assistant Container ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt TeamTracker: This error originated from a custom integration. Logger: custom_components.teamtracker Source: helpers/update_coordinator.py:412 integration: Team Tracker (documentation, issues) First occurred: 10:11:37 (21 occurrences) Last logged: 10:11:37 Error fetching team_tracker_golf data: Failed to initialize c-ares channel Error fetching team_tracker_golf_tiger data: Failed to initialize c-ares channel Error fetching team_tracker_golf_jt data: Failed to initialize c-ares channel Error fetching team_tracker_golf_rory data: Failed to initialize c-ares channel Error fetching team_tracker_golf_spieth data: Failed to initialize c-ares channel --------------------- Sonos Logger: homeassistant.config_entries Source: config_entries.py:749 First occurred: 10:11:42 (1 occurrence) Last logged: 10:11:42 Error setting up entry Sonos for sonos Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 171, in async_setup_entry await manager.setup_platforms_and_discovery() File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 603, in setup_platforms_and_discovery await self.async_poll_manual_hosts() File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 461, in async_poll_manual_hosts await self._async_handle_discovery_message( ...<3 lines>... ) File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 502, in _async_handle_discovery_message await self.async_subscribe_to_zone_updates(discovered_ip) File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 227, in async_subscribe_to_zone_updates sub = await soco.zoneGroupTopology.subscribe() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/soco/events_asyncio.py", line 373, in _async_wrap_subscribe await self.event_listener.async_start(self.service.soco) File "/usr/local/lib/python3.13/site-packages/soco/events_asyncio.py", line 219, in async_start self.session = ClientSession(raise_for_status=True, timeout=client_timeout) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 359, in __init__ connector = TCPConnector(loop=loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 869, in __init__ resolver = DefaultResolver(loop=self._loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 96, in __init__ self._resolver = aiodns.DNSResolver(*args, **kwargs) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiodns/__init__.py", line 67, in __init__ self._channel = pycares.Channel(event_thread=True, ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ timeout=timeout, ^^^^^^^^^^^^^^^^ **kwargs) ^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/pycares/__init__.py", line 422, in __init__ raise AresError('Failed to initialize c-ares channel') pycares.AresError: Failed to initialize c-ares channel ------------ SmartThings: Logger: homeassistant Source: /usr/src/homeassistant/homeassistant/runner.py:112 First occurred: 10:11:46 (1 occurrence) Last logged: 10:11:46 Error doing job: Task exception was never retrieved (None) Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/pysmartthings/smartthings.py", line 508, in subscribe async with ClientSession(timeout=timeout) as session: ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 359, in __init__ connector = TCPConnector(loop=loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 869, in __init__ resolver = DefaultResolver(loop=self._loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 96, in __init__ self._resolver = aiodns.DNSResolver(*args, **kwargs) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiodns/__init__.py", line 67, in __init__ self._channel = pycares.Channel(event_thread=True, ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ timeout=timeout, ^^^^^^^^^^^^^^^^ **kwargs) ^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/pycares/__init__.py", line 422, in __init__ raise AresError('Failed to initialize c-ares channel') pycares.AresError: Failed to initialize c-ares channel -------------- Unifi: Logger: homeassistant Source: components/unifiprotect/discovery.py:54 First occurred: 10:12:24 (1 occurrence) Last logged: 10:12:24 Error doing job: Task exception was never retrieved (None) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/unifiprotect/discovery.py", line 34, in _async_discovery async_trigger_discovery(hass, await async_discover_devices()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/unifiprotect/discovery.py", line 54, in async_discover_devices devices = await scanner.async_scan() ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/unifi_discovery/__init__.py", line 521, in async_scan await self._probe_services_and_system(response_list) File "/usr/local/lib/python3.13/site-packages/unifi_discovery/__init__.py", line 432, in _probe_services_and_system connector=TCPConnector(ssl=False), timeout=API_TIMEOUT ~~~~~~~~~~~~^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 869, in __init__ resolver = DefaultResolver(loop=self._loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 96, in __init__ self._resolver = aiodns.DNSResolver(*args, **kwargs) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiodns/__init__.py", line 67, in __init__ self._channel = pycares.Channel(event_thread=True, ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ timeout=timeout, ^^^^^^^^^^^^^^^^ **kwargs) ^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/pycares/__init__.py", line 422, in __init__ raise AresError('Failed to initialize c-ares channel') pycares.AresError: Failed to initialize c-ares channel --------------- Tronity: This error originated from a custom integration. Logger: custom_components.tronity Source: helpers/update_coordinator.py:380 integration: Tronity (documentation, issues) First occurred: 10:11:40 (7 occurrences) Last logged: 10:15:43 Unexpected error fetching tronity data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 281, in _async_update_data return await self.update_method() ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tronity/__init__.py", line 62, in async_update_data bearer_token = await get_bearer_token(client_id, client_secret) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tronity/__init__.py", line 47, in get_bearer_token async with aiohttp.ClientSession() as session: ~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 359, in __init__ connector = TCPConnector(loop=loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 869, in __init__ resolver = DefaultResolver(loop=self._loop) File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 96, in __init__ self._resolver = aiodns.DNSResolver(*args, **kwargs) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aiodns/__init__.py", line 67, in __init__ self._channel = pycares.Channel(event_thread=True, ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ timeout=timeout, ^^^^^^^^^^^^^^^^ **kwargs) ^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/pycares/__init__.py", line 422, in __init__ raise AresError('Failed to initialize c-ares channel') pycares.AresError: Failed to initialize c-ares channel --------------- ``` ### Additional information _No response_

sender · May 13, 2025, 5:27am

Oh yes I have that… but for around 2 years now…

Good tip, will also monitor now

agners · May 13, 2025, 11:09am

Hey, yeah this is a Supervisor 2025.05.0 bug which got released to the stable channel yesterday. The problem might come back if your system is out of inotify resources (see also Supervisor fails to start with pycares.AresError: Failed to initialize c-ares channel · Issue #5883 · home-assistant/supervisor · GitHub).

A proper fix will be shipped soon with Supervisor 2025.05.1. A reboot should be sufficient to temporarily get around the problem, since on startup Supervisor is started early when inotify resources are still available. Supervisor will continue working from that point onwards.

sender · May 13, 2025, 11:21am

Good to know it is “something”. A pity it is “something”

Morphy · May 13, 2025, 6:41pm

I’ve had an issue with a couple of instances going offline, supervisor just stopping with no error. I’ve not seen anything in the logs like above so I’m wondering if it’s related.

vbh · May 13, 2025, 7:00pm

I had the same issue and reboot of HA VM fixed it. After that i was presented with the 2025.05.1 update which should fix this issue permanently. Thanks for this very quick fix!

SpeedlimitsB · May 16, 2025, 4:27pm

I installed 2025.05.1 but still facing this issue . A hardware reboot is the only way to get it back. A restart will lead to this ;

ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!

ERROR (MainThread) [supervisor.core] Can’t start Home Assistant Core - rebuilding

ha core check
Processing… Done.
Command completed successfully.

ha core info
arch: amd64
audio_input: null
audio_output: null
backups_exclude_database: false
boot: true
image: Package generic-x86-64-homeassistant · GitHub
ip_address: -----
machine: generic-x86-64
port: -----
ssl: false
update_available: false
version: 2025.5.1
version_latest: 2025.5.1
watchdog: true