Journal issues with supervised install after updating to 2022.11

22

So I vent thru all supervised requirements again… WTH I do need to do that on a system, which always has been supported?

  • Docker CE >= 20.10.17
    my version is 20.10.21

  • Systemd >= 239
    my version is 247

  • NetworkManager >= 1.14.6
    my version is 1.30.6

  • udisks2 >= 2.8
    my version is 2.9.2

  • AppArmor == 2.13.x (built into the kernel)
    my version is 2.13.6-10

  • Debian Linux Debian 11 aka Bullseye (no derivatives)
    I do have that, fully up to date

  • Home Assistant OS-Agent (Only the latest release is supported)
    my version is 1.4.1

So according to the docs my system does meet all requirements.

My HA system is:
Home Assistant 2022.11.1 Supervisor 2022.10.2 Frontend-versie: 20221102.1 - latest

Still, with all those steps I can’t get rid of the message:

update OS-agent to 1.4.1
update HA to 2022.11.1
reinstall the systemd journal service
update / upgrade Debian Bullseye
rerun the supervised installer
reinstall Docker
multiple host restarts

Also, I’m very sure, that about a week a go I have been checking the system info and logs, and there was not any sign of being unsupported. I will directly see that, if it was there.

Something must have changed. Something, that is beyond all the installation docs.

4 Likes
23

Ah. Yea I think something does need an update. The supervised adr mentions this:

Systemd journal gateway is enabled and mapped into supervisor as /run/systemd-journal-gatewayd.sock

I was under the impression that the installer had been updated to handle that but perhaps not. I’ll do some digging. Also looks like the ADR didn’t list systemd-journal-gatewayd in the software list when it was updated to include that additional step 2 months ago.

1 Like
24

I’m dealing with the same problem as you

Ive reinstalled from GitHub - home-assistant/supervised-installer: Installer for a generic Linux system…
But makes no difference :frowning:

1 Like
25

Marking messages as ignored for now and waiting for an update. :grinning:

26

The installer also lacks the installation of connectivity check, which is mandatory for ages. If I run the installer now, it just rewrites the config and connectivity check is gone and must be re added manually again. :wink:

2 Likes
27

I got the systemd journal issue after the update of supervisor-2022.10.2 before that i did not have the error with 2022.11

I installed systemd-journal-remote and started the service (also at boot)
After restart of the system still the error.
Than I installed the lasted homeassistant-supervised.deb, rebooted and error was away.

28

After you get the journal thing installed, reboot the host so it can be part of the OS. Worked for me.

29

Now I got it thanks :slight_smile:

30

All I did was what I wrote above while following errors that were reported when doing so. I.e. I had messages that I need to update some packages in order for it to fully complete. It was easy to do if you read the results of the commands. I’m not at home, so I can’t post everything I had to do.

1 Like
31

Hi, i followed all steps mentioned here in this topic (including multiple host reboots).

Weirdly, i am unable to start the service:

pi@raspberrypi:~ $ sudo systemctl start systemd-journal-gatewayd.socket
pi@raspberrypi:~ $ sudo systemctl status systemd-journal-gatewayd.service
● systemd-journal-gatewayd.service - Journal Gateway Service
     Loaded: loaded (/lib/systemd/system/systemd-journal-gatewayd.service; indirect; vendor preset: disabled)
     Active: inactive (dead)
TriggeredBy: ● systemd-journal-gatewayd.socket
       Docs: man:systemd-journal-gatewayd(8)

Any thoughts what is preventing it from start running? I’m on Raspbian Bullseye

32

No, that was also happened to me. I enabled service before reboot and after reboot I had to manually start it.

33

Yeah, i can’t start it. Neither before reboot nor after reboot.

34

I made an issue. Let’s take this discussion there as the installer needs to either be updated or the guide does as it appears there’s something missing.

Please make another issue in that same repo. Seems that needs to be updated too.

6 Likes
35

Love the look, but unfortunately Picture Elements have stopped working with IMAGES EXAMPLE below an extract from Picture Elements Card - Home Assistant

type: picture-elements
image: /local/floorplan.png
elements:
  # state_image & state_filter - toggle on click
  - type: image
    entity: light.living_room
    tap_action:
      action: toggle
    image: /local/living_room.png
    state_image:
      "off": /local/living_room_off.png
    filter: saturate(.8)
    state_filter:
      "on": brightness(120%) saturate(1.2)
    style:
      top: 25%
      left: 75%
      width: 15%

My simple one was

type: picture-elements
image: /local/irrigation/mon-sun1.png
elements:
  - type: image
    entity: input_boolean.water_monday
    tap_action:
      action: toggle
    state_image:
      'off': /local/off.png
      'on': /local/on/png

Worked like a charm before update, 2022.11, even updated to 2022.11.1 still not working

But then again the Picture Elements stopped pushing aspect ratio a long time ago too, so now it CROPS instead of CONSTRAINT the image to FIT the aspect Ratio.

Would love both to be fixed, but at least the First one is a little more important

36

I cant even reinstall homeassistant-supervised.deb because it fails with os-agent dependency, but os-agent is installed already. I tried 1.2.0 1.3.1 and 1.4.1 versions and .deb installation fails with all of them.

37

And I made mistake by rebooting and now the containers wont even start. So no automation for tonight. Nice.

38

Make sure you’re cleaning out the folder that you’re downloading the deb installer to - I found it was making .1 - .3 entries and I was blindly reinstalling the same old supervisor (1.1.0) instead of the most recent (1.3.1)

root@homeassistant:~# dpkg -i homeassistant-supervised.deb
(Reading database ... 294458 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]
[warn] ModemManager service is enabled. This might cause issue when using serial devices.
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.3.1) over (1.1.0) ...
Setting up homeassistant-supervised (1.3.1) ...
[info] Restarting NetworkManager
[info] Restarting docker service
PING checkonline.home-assistant.io (172.67.68.90) 56(84) bytes of data.
64 bytes from 172.67.68.90 (172.67.68.90): icmp_seq=1 ttl=54 time=26.2 ms

--- checkonline.home-assistant.io ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 26.219/26.219/26.219/0.000 ms
[info] Install supervisor startup scripts
[info] Install AppArmor scripts
[info] Start Home Assistant Supervised
[info] Installing the 'ha' cli
[info] Switching to cgroup v1
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-5.10.0-13-amd64
Found initrd image: /boot/initrd.img-5.10.0-13-amd64
Found linux image: /boot/vmlinuz-5.10.0-12-amd64
Found initrd image: /boot/initrd.img-5.10.0-12-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Adding boot menu entry for UEFI Firmware Settings ...
done
[info] Within a few minutes you will be able to reach Home Assistant at:
[info] http://homeassistant.local:8123 or using the IP address of your
[info] machine: http://172.24.0.250:8123
[warn] A reboot is required to apply changes to grub.

All of my repairs issues have gone away.

5 Likes
39 
sudo dpkg -i homeassistant-supervised.deb
(Reading database ... 40505 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]
[warn] ModemManager service is enabled. This might cause issue when using serial devices.
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.3.1) over (1.3.1) ...
dpkg: dependency problems prevent configuration of homeassistant-supervised:
 homeassistant-supervised depends on os-agent.

dpkg: error processing package homeassistant-supervised (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 homeassistant-supervised
40

Have you removed and re-installed os-agent?

41

Yes, it does not help.