Not starting after Restore

Installation Home Assistant OS
1

Hi there,
I just restored an old complete SD card backup which was running great that time creating it. Now when I boot it Home Assistant is not starting, because the supervisor seems to crash. I can only find this log message:

KeyError: 'CgroupVersion'
22-07-06 11:49:35 ERROR (MainThread) [asyncio] Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0xb3c05c10>

Can anyone explain why this happens? This image runs great a few weeks ago.

1 Like
2

Your are probably running a Supervised installation and the Supervisor updated to the latest version automatically.

1 Like
3

Do bit of search how to update supervisor manually to 2022.07.0, as it fixes the problem. But generally you should update Docker to 20.10.0.

4

I have this same issue -
Iā€™m running hassio in a VM -

given the supervisor wont start, how can I manually update it?
ā€˜ha supervisor updateā€™ does not work, as it needs the supervisor to run

Also, how can the docker version itself be updated from hassio?

5

So the core is still running and you can access it though SSH?

Otherwise what OS are you running? If it is Supervisedā€¦

6

I can login and access the emergency terminal (as the hassio_cli does not start), but it allows me to access the system. From there I can start the homeassistant docker container so can get the core working - but every time I try start the supervisor I get the Unclosed client session error.

So Iā€™m caught in a loop - cannot start supervisor ā†’ try to update supervisor ā†’ supervisor needs to be runining to run the ā€˜ha supervisor updateā€™ command.

So is there something I can do to get out of this ?

7

Have a look on the observer what it says, why the supervisor fails:

If it is the same issue with 2022.06.3 as described in the linked Github issues above, then from the terminal run this to list the running containers:

docker ps

Then you can do a:

docker pull homeassistant/XXXXX-hassio-supervisor:2022.07.0 or docker pull homeassistant/XXXXX-hassio-supervisor:latest where XXXXX is the architecture what you are using. (Probably the second one is the right choice.)

And then a

docker tag homeassistant/XXXXX-hassio-supervisor:latest homeassistant/XXXXX-hassio-supervisor:latest

Edit: I updated to the correct ones, I typed from memory beforeā€¦

2 Likes
8

The observer simply says the supervisor is not connected - but that is no surprise, the supervisor does not start - with the exact same error as the OP.

I tried the command you gave as:
docker pull homeassistant/amd64-hassio-supervisor:2022.07.0

it now gives me a file now found error:
screenshot

When I run this container, do I need to give it commands to specify -v paths and network addresses, etc?

Note: I tried the docker images command and it listed a version of the supervisor loaded from 9 days ago - I was out of the country then, so I assume this was the version that broke everything:
docker images

9

If you really have the same issue, then look here:

When starting up the host, it should start the latest version of the supervisor along the core and everything.

1 Like
10

Whoop! that did it, thanks a million!

1 Like
11

Thanks to OP for starting the thread and thanks to @GSzabados for the commands needed.

2 Likes