Unhealthy state

Configuration
28

You can indeed, good add :+1:

29

I had networkmanager.service disabled on Nuc with Ubuntu 18… because of zwave problem on reboots. Fix for my unhealty install was to enable networkmanager.service and update it with link from @nickrout, everything was ok after that. Then upgraded Ubuntu to 20.04.1 LTS and also everything ok.

30

I agree. It should have been mentioned in breaking changes. Having had some bad experiences from not doing so earlier, I always read them thoroughly. But I would have gone on to Debian 10 sooner or later anyway, so I’ll go for it today. Fingers crossed…

1 Like
31

let me know how it goes and what you needed to do to get it done, please.

I’m still running Debian 9 myself and dreading doing the upgrade since everything is “just working” (except for a stupid memory leak I can’t find).

32

I’m a bit worried.
I followed the instructions on several sites for upgrading to Debian 10, but it seems to require skills far above my linux level. Lots of packages that fail to upgrade, missing this and that, and so on. It’s been running without problems for 3 1/2 years, so I guess it’s had time to get a bit messy.

So, now I’m facing some alternatives:

  1. Install Debian 10 and Home Assistant Core from scratch. (Hoping that I have a good enough backup before i destroy my NUC installation)
  2. Install Home Assistant OS
  3. Windows 10 with HA installed on docker?
  4. Other options?

The NUC won’t be used for anything other than Home Assistant.
What should I do?

33

You can update your system with unsupported packages from this untrusted PPA by …

Thanks for the tip. Seems like the most painless way to get a more recent version of Network Manager on 18.04 but the ‘unsupported/untrusted’ aspect makes me leery. For a short-term fix, I think I’ll upgrade from 18.04 to 20.04 on the existing old hard-drive; long-term fix will be Debian 10 on a new SSD. Should’ve paid closer attention to the Black Friday sales for computer components … :man_shrugging:

UPDATE

Upgraded the production server from 18.04.5 to 20.04.1. Took a long time (over 90 minutes vs 20 minutes for a similar machine equipped with an SSD) but now Network Manager is at version 1.22.10 and there’s no longer any error/warnings about it. The ‘unhealthy’ indicator is gone but ‘unsupported’ remains for the obvious reason that this is still Ubuntu (not Debian).

Hopefully this will tide me over until I can get around to buying an SSD, installing Debian, and creating a completely new installation of Home Assistant Supervised.

34

Install Debian 10 and supervised.

35

FWIW, I hit this very issue yesterday (Supervised “running rogue” on Ubuntu 18.04), and installing host OS updates (including a new Docker version) and a reboot seemed to get me going. Certainly not claiming that this is a fix, but it might be something low-impact to try. Based on this thread, it sounds like I might look into a newer Ubuntu version as well.

36

I don’t remember any issues when I did it… I think it was as easy as editing sources…

37

What version of network-manager are you running?

38

Can I just ask… did the maintainers know in advance that the updated Supervisor would break the Ubuntu 18.04 LTS installs ? Please don’t just retort ‘it’s unsupported’

39

I imagine only the developers managing Supervisor can answer that. Otherwise, it’s just speculation.

FWIW, whether they knew or not, they aren’t obligated to consider the impact of their changes on anything that they don’t support.

Yet that’s the primary reason they aren’t obligated to consider the impact of their changes.

40

I agree but it would be professional to do so and a bit non caring on an LTS release not to. I’m trying to assess if not adding a breaking change notification was just a ‘told you so’ attitude. I do feel a little disappointed.

41

It’s “LTS” for Ubuntu; the designation is not meaningful for Home Assistant Supervised which is officially supported only on Debian.

If anyone wondered what’s the difference between an unsupported installation method and a supported one, this is what it looks like.

Let’s not overlook the fact that the original intent was to deprecate Home Assistant Supervised. The compromise was to continue supporting it but exclusively on Debian. For people like me who still run it on Ubuntu, it’s done with the understanding that it’s subject to modifications that don’t consider Ubuntu’s needs.

FWIW, I’ve been planning to switch to Debian and this recent incident has given me more incentive to do it sooner than later.

2 Likes
42

I’m not here to criticise except to say that a breaking change notification would have been helpful and professional if it was a known issue.

43

I don’t think there is even a change log presented and supervisor automatically updates so not sure how you think a notification will help.

44

Fair point but a forced update that causes issues (albeit I have an unsupported OS) is concerning.

45

I agree that it would have been nice to know in advance. It seems like the recent release of Supervisor became more stringent about operating conditions. Knowing about this new behavior would have been useful (even if one runs on Debian). The problem is that there’s almost never any information provided about Supervisor updates (short of checking its release notes after it has already been deployed).

1 Like
46

I too will transition to Debian. However I am not Linux proficient and have around a dozen other apps running on the Ubuntu machine and it all works really well. I just know it’s going to take a lot of time and effort and so notice would have been good. Updating Ubuntu seems only a temporary solution.

47

Interestingly, it’s 1.10.6-2ubuntu1.4. In fact, it appears that I have the same setup as @123 described above: Ubuntu 18.04.5, Supervisor 2020.12.6, and Docker version 19.03.14.

In my case, I started from HA 0.118.1 and updated the Supervisor first. After that, when I tried to upgrade to HA 0.118.5, and that failed completely. It was then that I checked the System page and saw the “unhealthy installation” warning.

At that point, I noticed that my system had updates available, one of which was Docker, and I wondered if that might make a difference, so I updated and restarted, which seems to have worked.

I hadn’t read this thread or any info about network-manager at that point, or I wouldn’t have thought there would be any benefit. After reading this thread, though, I feel like I’m waiting for the other shoe to fall… :grimacing: