All looks ok but Home Assistant Supervised does not run - on Debian Buster

Installation
1

Hi,

I cannot access GUI on fresh Home Assistant Supervised installation

installation went absolutely OK:

sudo dpkg -i homeassistant-supervised.deb
(Reading database ... 145336 files and directories currently installed.)
Preparing to unpack homeassistant-supervised.deb ...
[warn] 
[warn] If you want more control over your own system, run
[warn] Home Assistant as a VM or run Home Assistant Core
[warn] via a Docker container.
[warn] 
Leaving 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised'
Leaving 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant-supervised'
Leaving 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised'
Leaving 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised'
Unpacking homeassistant-supervised (1.0.2) over (1.0.2) ...
Setting up homeassistant-supervised (1.0.2) ...
[info] Restarting NetworkManager
[info] Restarting docker service
PING version.home-assistant.io (104.26.4.238) 56(84) bytes of data.
64 bytes from version.home-assistant.io (104.26.4.238): icmp_seq=1 ttl=57 time=126 ms

--- version.home-assistant.io ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 125.695/125.695/125.695/0.000 ms
[info] Install supervisor Docker container
[info] Install supervisor startup scripts
[info] Install AppArmor scripts
[info] Start Home Assistant Supervised
[info] Installing the 'ha' cli

docker ps
CONTAINER ID   IMAGE                                                     COMMAND                  CREATED         STATUS         PORTS                  NAMES
b036eff3dde1   ghcr.io/home-assistant/armv7-hassio-multicast:2021.04.0   "/init"                  3 minutes ago   Up 3 minutes                          hassio_multicast
7b9a9010acd6   ghcr.io/home-assistant/armv7-hassio-audio:2021.07.0       "/init"                  3 minutes ago   Up 3 minutes                          hassio_audio
880eab9ea82e   ghcr.io/home-assistant/armv7-hassio-dns:2021.06.0         "/init"                  3 minutes ago   Up 3 minutes                          hassio_dns
d8763b233069   ghcr.io/home-assistant/armv7-hassio-cli:2021.09.0         "/init /bin/bash -c …"   3 minutes ago   Up 3 minutes                          hassio_cli
50d9be6fbb3b   ghcr.io/home-assistant/armv7-hassio-observer:2021.10.0    "/init"                  5 hours ago     Up 3 minutes   0.0.0.0:4357->80/tcp   hassio_observer
f63f9f444788   homeassistant/armv7-hassio-supervisor                     "/init"                  5 hours ago     Up 3 minutes                          hassio_supervisor

but problem is that port 8123 is not opened and it is not listening

sudo netstat -tnlp | grep 8123
...

looks the Home Assistant is running too:

ha info
arch: aarch64
channel: stable
docker: 20.10.10
features:
- reboot
- shutdown
- services
- network
- hostname
- timedate
- os_agent
hassos: null
homeassistant: 2021.11.2
hostname: zipi
logging: info
machine: raspberrypi4-64
operating_system: Raspbian GNU/Linux 10 (buster)
state: running
supervisor: 2021.10.8
supported: false
supported_arch:
- aarch64
- armv7
- armhf
timezone: Europe/Paris

anyone can help to get home assistant started?

2

What is it ?

And did you install os-agent ?

4

Sorry my bad - indeed Buster, ah OK, so I cannot make it working on Buster

5

There is a guide here: https://community.home-assistant.io/t/installing-home-assistant-supervised-on-debian-11/200253 .
Should be valid for debian 10. Check all the steps just in case…

6

Yes, os-agent installation went good as well

sudo dpkg -i os-agent_1.2.2_linux_armv7.deb
(Reading database ... 145342 files and directories currently installed.)
Preparing to unpack os-agent_1.2.2_linux_armv7.deb ...
Removed /etc/systemd/system/multi-user.target.wants/haos-agent.service.
Unpacking os-agent (1.2.2) over (1.2.2) ...
Setting up os-agent (1.2.2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/haos-agent.service → /usr/lib/systemd/system/haos-agent.service.
Processing triggers for dbus (1.12.20-0+deb10u1) ..
7

Check this guide (specific for Raspberry)

8

I verified all steps in above guide triple times and did not find any discrepancy. Only problem is that port 8123 is not opened and listening.

9

2 problems :

  • using Raspbian instead of Debian
  • Bullseye was released beginning of August, there was 4 months deprecation time, so Buster should still work for 2,5 weeks. Is it worth it for these 2,5 weeks ?
10

OK, agree. I will migrate to Bullseye first then I will try again

11

Having the exact same problem, but with Bullseye on an x86-type machine. Pretty sure it has nothing to do with Debian version or machine type. Also with me everything checks out ok - except for access to the frontend :frowning:

12

I migrated to Bullseye and the problem persists.

I found crashes in logs:

ha supervisor logs

21-11-11 12:11:58 INFO (MainThread) [supervisor.core] Supervisor is up and running
21-11-11 12:11:58 INFO (MainThread) [supervisor.host.info] Updating local host information
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.CREATE_FULL_BACKUP - ContextType.SYSTEM / None
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-11-11 12:11:58 INFO (MainThread) [supervisor.host.services] Updating service information
21-11-11 12:11:58 INFO (MainThread) [supervisor.host.network] Updating local network information
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-11-11 12:11:58 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-11-11 12:11:58 INFO (MainThread) [supervisor.host.manager] Host information reload completed
21-11-11 12:12:02 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-11-11 12:12:02 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-11-11 12:12:13 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with Home Assistant Docker!
21-11-11 12:12:13 INFO (SyncWorker_2) [supervisor.docker.interface] Starting homeassistant
21-11-11 12:12:13 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-11-11 12:12:18 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
21-11-11 12:12:18 ERROR (MainThread) [supervisor.misc.tasks] Home Assistant watchdog reanimation failed!
21-11-11 12:12:18 INFO (MainThread) [supervisor.misc.tasks] Rebuilding the Home Assistant Container
21-11-11 12:12:18 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning homeassistant application
21-11-11 12:12:18 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
21-11-11 12:12:20 INFO (SyncWorker_0) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/raspberrypi4-64-homeassistant with version 2021.11.2
21-11-11 12:12:20 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-11-11 12:12:25 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
21-11-11 12:12:40 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-42' coro=<Scheduler._run_task.<locals>._wrap_task() done, defined at /usr/src/supervisor/supervisor/misc/scheduler.py:58> exception=HomeAssistantCrashError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/misc/scheduler.py", line 62, in _wrap_task
    await task.coro_callback()
  File "/usr/src/supervisor/supervisor/misc/tasks.py", line 198, in _watchdog_homeassistant_docker
    await self.sys_homeassistant.core.rebuild()
  File "/usr/src/supervisor/supervisor/utils/__init__.py", line 33, in wrap_api
    return await method(api, *args, **kwargs)
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 317, in rebuild
    await self._start()
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 270, in _start
    await self._block_till_run(self.sys_homeassistant.version)
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 453, in _block_till_run
    raise HomeAssistantCrashError()
supervisor.exceptions.HomeAssistantCrashError

any idea?

13

I have the same exact problem here on debian 11 (x86)
I still can’t access the gui and homeassistant image is not listed in docker?

image
image1511Ă—458 62.9 KB

15

I gave up and installed OS version at dedicated device RPI3.

16

Sorry this post is so long. Here’s the summary:

  • Port 8123 is not open.
  • What is an effective way to delete everything and start again?
  Operating System: Debian GNU/Linux 11 (bullseye)
  Kernel: Linux 5.10.63-v8+
  Architecture: arm64

Here are many more words:
I have the exact same problem on my pi 4. There is no “homeassistant” docker image installed, and so nothing listening on 8125.

I have attempted to delete everything and start again, but that didn’t help. Here’s what I did to try and start from scratch:

systemctl stop hassio-supervisor.service
systemctl stop hassio-apparmor.service
docker stop homeassistant...
docker rmi -f homeassistant...
rm -rf /usr/share/hassio
dpkg -r homeassistant-supervised
dpkg -i homeassistant-supervised.deb
systemctl start hassio-supervisor.service
systemctl start hassio-apparmor.service

When I restart supervisor log says:

 [supervisor.docker] Image ghcr.io/home-assistant/raspberrypi4-64-homeassistant not exists for homeassistant

I tried ha core rebuild, but that didn’t help.

docker pull ghcr.io/home-assistant/raspberrypi4-64-homeassistant seemed like a good idea, but didn’t help.

I’ve since run docker image ls and can see I have multiple images. One could be from an earlier installation of the non-supervised image, so I deleted both raspberrypi4-64-homeassistant images, and tried to force a repair with ha su repair

docker logs hassio_supervisor says:

21-12-01 00:53:33 INFO (MainThread) [supervisor.homeassistant.core] Repair Home Assistant 2021.11.5
21-12-01 00:53:33 INFO (SyncWorker_3) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-64-homeassistant with tag 2021.11.5.
21-12-01 00:56:13 INFO (MainThread) [supervisor.supervisor] Repairing Supervisor 2021.10.8

and I can see the image in docker image ls, but there is nothing in docker ps.

After rebooting I can see the process is running, but port 8123 isn’t mapped:

root@blackbox:/# docker ps
CONTAINER ID   IMAGE                                                            COMMAND                  CREATED         STATUS         PORTS                                   NAMES
acb7e6343e9e   ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2021.11.5   "/init"                  5 minutes ago   Up 5 minutes                                           homeassistant
9d17665c61a0   ghcr.io/home-assistant/aarch64-hassio-multicast:2021.04.0        "/init"                  6 minutes ago   Up 6 minutes                                           hassio_multicast
cb56c260ac98   ghcr.io/home-assistant/aarch64-hassio-audio:2021.07.0            "/init"                  6 minutes ago   Up 6 minutes                                           hassio_audio
abb426d2766e   ghcr.io/home-assistant/aarch64-hassio-dns:2021.06.0              "/init"                  6 minutes ago   Up 6 minutes                                           hassio_dns
1c912734ce76   ghcr.io/home-assistant/aarch64-hassio-cli:2021.09.0              "/init /bin/bash -c …"   6 minutes ago   Up 6 minutes                                           hassio_cli
d7131144e77c   ghcr.io/home-assistant/aarch64-hassio-observer:2021.10.0         "/init"                  3 hours ago     Up 6 minutes   0.0.0.0:4357->80/tcp, :::4357->80/tcp   hassio_observer
414a640f8663   homeassistant/aarch64-hassio-supervisor                          "/init"                  4 hours ago     Up 6 minutes                                           hassio_supervisor

Any ideas what I need to do?
What is an effective way to delete everything and start again?

Also, once installed, where are the config files located? The instructions I followed don’t mention it.

Thank you for your time!
Kerry

PS: Is there no “preview” in this forum software?

1 Like
17

It’s port 8123

Terry

18

Sorry. 8125 was a slip of the finger. 8123 isn’t open either :slight_smile:

20

That’s fine. Can you tell me a guaranteed way to remove whatever is installed now? Are the steps I took above sufficient?

Thanks.

21

I’ve taken another run at uninstalling (including the complete removal of docker and all images) and re-installing using the official documentation, but the docker image still isn’t available on 8123, even though it seems to be running without any problem.

Please note that docker shows that no ports are mapped for homeassistant!:
docker ps --format 'table {{.Image}}\t{{.Command}}\t{{.Ports}}

IMAGE                                                            COMMAND                  PORTS
ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2021.11.5   "/init"
ghcr.io/home-assistant/aarch64-hassio-multicast:2021.04.0        "/init"
ghcr.io/home-assistant/aarch64-hassio-observer:2021.10.0         "/init"                  0.0.0.0:4357->80/tcp, :::4357->80/tcp
ghcr.io/home-assistant/aarch64-hassio-audio:2021.07.0            "/init"
ghcr.io/home-assistant/aarch64-hassio-dns:2021.06.0              "/init"
ghcr.io/home-assistant/aarch64-hassio-cli:2021.09.0              "/init /bin/bash -c …"
homeassistant/aarch64-hassio-supervisor                          "/init"

This smells like a bug rather than user error, but I’m happy to be proven wrong.

22

The other possibility is that my pi’s IP address has changed, despite my router being configured to dish out the same address to it. Sigh. I am a numpty.

24

Which provides software that is not compliant with ADR-0014.