Supervisor Won't Start

I hate those automatic supervisor updates. This is the second time it just killed my environment while not home!

7 Likes

I had the same problem this morning. Fixed it with running (as root) the install script as suggested here.

Same issue for me. Had some issues with the suggested fix. Ran both suggestions from @night. To run the curl command I originally ran it with ‘sudo’ but that didn’t work. Got an error ’ bash: line 133: /etc/hassio.json: Permission denied’ had to login as root and then run it. That worked and I’m back up and running. But, not sure whether it was just the curl command or the curl command and the docker commands were required to resolve the issue.

I typed sudo -i
then pasted the curl command and started again

Same thing here, had to reboot after the “docker” command.

Thank you all !

Yes, that’s what I had to do as well, I should have mentioned it. Here’s the the order I ran the commands in if anyone else still struggles with this.

sudo -i
apt-get update
apt-get install -y software-properties-common apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
systemctl disable ModemManager
curl -fsSL get.docker.com | sh

docker pull homeassistant/amd64-hassio-supervisor:latest

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

curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
9 Likes

Yeah, that’s not ideal. If you haven’t done it already I suggest you make a feature request to disable automatic updates here: https://community.home-assistant.io/c/feature-requests

It’s the first time I’ve had any issues, but if it’s after every supervisor release you should open a ticket about it to find the root cause.

Same issue here on ubuntu 18.04 since this morning.

Yesterday, HA showed the supervisor update in the Supervisor section, but I did NOT install it.
Apparently, it did not stop it from being installed automatically a couple of hours later…

This is not the first time these automatic updates broke stuff. The last time was the introduction of the DNS thing that broke internet connectivity for a lot of people.

Ugh, glad I found this thread, been pulling my hair out as to why things were suddenly having problems! The latter recommendations worked to resolve my problem. Not a fan of automatic updates, I’ve stopped unattended-upgrades in Ubuntu 18.04 because of that.

I’ve opened a request here: [supervisor] option for disabling auto-updates

2 Likes

Same here.

The solution from night worked for me.

Thinking about getting rid of hassio and managing core and addons myself through Docker/Portainer…

I’ve opened a request here: [supervisor] option for disabling auto-updates

Thanks I added my vote to your thread.

1 Like

Same issue here and can confirm solution from night got things going again. I’m also on Ubuntu.

yes, is there a way to mark Night’s solution as THE solution? Worked for me too and saved me so much time.

Is there anyone who knows how to run the update if I can’t remember my Ubuntu username anymore?
Or knows how to find my username on a headless Ubuntu 18.04. Running Hassio on headless Ubuntu server and nothing starts anymore but since I don’t know my username I am just stuck…
And somehow posting here gave me a brainwave. Remembered my login and with the help of this great community was able to fix the problem.
Updated and running again!

1 Like

+1
@mostlychris, would you consider editing your original post to point to the thorough solution in the comment from @night? Thanks!

@night fixed it

I run @night command as root but get no response back other than the cursor…

You need to describe the situation in more detail if we’re going to be able to help you.

What platform are you running on? Raspberry pi, Linux server (Ubuntu for instance).
What exactly did you try? Did you run the command on the host or inside a docker container? Try to recreate your steps and describe it here.

I’ve just installed Home Assistant on a Raspberry Pi in a venv. I noticed that Supervisor isn’t showing up in the interface. How can I fix that?

1 Like