-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on Supervisor API / Supervisor issues #134976
Labels
Comments
Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) hassio documentation |
Home Assistant observerSupervisor: | 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 [19:01:56] 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) [19:01:56] INFO: Starting local supervisor watchdog... s6-rc: info: service legacy-services successfully started 2025-01-03 19:01:57.716 INFO (MainThread) [__main__] Initializing Supervisor setup 2025-01-03 19:01:57.770 INFO (MainThread) [supervisor.utils.sentry] Initializing Supervisor Sentry 2025-01-03 20:01:57.773 INFO (MainThread) [supervisor.bootstrap] Setting up coresys for machine: generic-x86-64 2025-01-03 20:01:57.777 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/amd64-hassio-supervisor with version 2024.12.3 2025-01-03 20:01:57.777 INFO (MainThread) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network 2025-01-03 20:01:57.899 INFO (SyncWorker_0) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/amd64-hassio-supervisor:2024.12.0'] 2025-01-03 20:01:58.368 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state initialize 2025-01-03 20:01:58.369 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete 2025-01-03 20:01:58.370 INFO (MainThread) [__main__] Setting up Supervisor 2025-01-03 20:01:58.583 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2 2025-01-03 20:01:58.651 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor 2025-01-03 20:01:58.652 INFO (MainThread) [supervisor.dbus.manager] Connected to system D-Bus. 2025-01-03 20:01:58.652 INFO (MainThread) [supervisor.dbus.agent] Load dbus interface io.hass.os 2025-01-03 20:01:58.653 INFO (MainThread) [supervisor.dbus.hostname] Load dbus interface org.freedesktop.hostname1 2025-01-03 20:01:58.654 INFO (MainThread) [supervisor.dbus.logind] Load dbus interface org.freedesktop.login1 2025-01-03 20:01:58.655 INFO (MainThread) [supervisor |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Everyone,
Happy New Year! And thank you all for HA, great Project.
I am observing a strange problem, Supervisor is not responding anymore.
The problem
No Backupinformations, canˋt reboot HA PC, get an error messages, no connection to Add-on such as AppDeamon, Backup, Grafana, InfluxDB. Hard reset helps but some time later problems start to come back.
HA dashboard is working so far.
What version of Home Assistant Core has the issue?
core-2025.1.0
What was the last working version of Home Assistant Core?
core-2024.11.0
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Supervisor
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hassio
Diagnostics information
config_entry-hassio-fdb17ed127e72381c2f42ac4d6e4a993.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
Error on Supervisor API: Error occurred connecting to supervisor
No response
The text was updated successfully, but these errors were encountered: