From 3e05425e56bd186505d4bbd3898cb5741bf30e7e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20S=C3=B8rensen?= Date: Mon, 23 Nov 2020 17:37:26 +0100 Subject: [PATCH] Add more-info about unhealthy setups (#15729) Co-authored-by: Franck Nijhof --- source/more-info/unhealthy/docker.markdown | 13 +++++++++ source/more-info/unhealthy/setup.markdown | 29 +++++++++++++++++++ .../more-info/unhealthy/supervisor.markdown | 17 +++++++++++ 3 files changed, 59 insertions(+) create mode 100644 source/more-info/unhealthy/docker.markdown create mode 100644 source/more-info/unhealthy/setup.markdown create mode 100644 source/more-info/unhealthy/supervisor.markdown diff --git a/source/more-info/unhealthy/docker.markdown b/source/more-info/unhealthy/docker.markdown new file mode 100644 index 00000000000..8050c6255ca --- /dev/null +++ b/source/more-info/unhealthy/docker.markdown @@ -0,0 +1,13 @@ +--- +title: "The Docker environment is not working properly" +description: "More information on why a misconfigured Docker environment marks the system as unhealthy." +--- + +Docker is at the core of most operations that the Supervisor does, it is important that it is configured properly and is working the way the Supervisor expects. + +The Supervisor will be marked as unhealthy if any of these requirements are not met: + +- [Running containers known to cause issues](/more-info/unsupported/container) +- [Running an unsupported Docker version](/more-info/unsupported/docker_version) +- [Running the Supervisor under LXC](/more-info/unsupported/lxc) +- [Not running the Supervisor as privileged](/more-info/unsupported/privileged) diff --git a/source/more-info/unhealthy/setup.markdown b/source/more-info/unhealthy/setup.markdown new file mode 100644 index 00000000000..e56f19c5c97 --- /dev/null +++ b/source/more-info/unhealthy/setup.markdown @@ -0,0 +1,29 @@ +--- +title: "Setup of the Supervisor failed" +description: "More information on why failing the setup stage makes an installation as unhealthy." +--- + +## The issue + +This happens when any of the setup tasks fails to complete, this can be due to the host not being completely ready when the Supervisor starts or that [DBUS] is not properly working. + +## The solution + +If the issue is related to DBUS, you will see an unsupported message about that as well; You can have a look [here][DBUS] on how to resolve that. + +The first thing you should try is to restart the Supervisor. +This can be done from the "System" tab in the Supervisor panel. On the card for "Supervisor", there is a button to restart the Supervisor. + +This can also be done with the CLI, by running the following command: + +```bash +ha supervisor restart +``` + + +If this does not help, you can try to reboot the host. +If you are running Home Assistant Operating System, this can be done from the "System" tab in the Supervisor panel. On the card for "Host System", there is a button to reboot the host. + +To help us make the setup more robust, please enable the sharing of diagnostics and crash logs on the "System" tab in the Supervisor panel. + +[DBUS]: /more-info/unsupported/dbus diff --git a/source/more-info/unhealthy/supervisor.markdown b/source/more-info/unhealthy/supervisor.markdown new file mode 100644 index 00000000000..167b8946839 --- /dev/null +++ b/source/more-info/unhealthy/supervisor.markdown @@ -0,0 +1,17 @@ +--- +title: "Supervisor was not able to update" +description: "More information on why a failed Supervisor update marks a system as unhealthy." +--- + +## The issue + +This can happen when there was a network issue during the startup of the Supervisor. + +## The solution + +Manually update the Supervisor. This can be done from the "System" tab in the Supervisor panel. On the card for "Supervisor", there is a button to update the Supervisor. + +This can also be done with the CLI, by running the following command: +```bash +ha supervisor update +```