Journal issues with supervised install after updating to 2022.11

1

The latest update 11.01 is slowing things down.

2022-11-03 20:50:52.940 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds.

2022-11-03 20:50:54.217 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.

2022-11-03 20:50:54.220 WARNING (MainThread) [homeassistant.setup] Setup of input_number is taking over 10 seconds.

2022-11-03 20:50:54.221 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.

2022-11-03 20:50:54.223 WARNING (MainThread) [homeassistant.setup] Setup of input_button is taking over 10 seconds.

2022-11-03 20:50:54.227 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.

2022-11-03 20:50:54.229 WARNING (MainThread) [homeassistant.setup] Setup of schedule is taking over 10 seconds.

2022-11-03 20:50:54.231 WARNING (MainThread) [homeassistant.setup] Setup of input_datetime is taking over 10 seconds.

2022-11-03 20:50:54.233 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform energy is taking over 10 seconds.

Im not even using for example the energy platform at all.

And its asking me to install NetworkManager, Systemd-resolved, systemd-journal-gatewayd and its saying docker cgroup version 2 is not supported.

1 Like
2

Supervised installer has installing the gateway as a pre-req step

Since when? Why is there no changelog about this requirement? Maybe update the installation documents/guides.

3

Ok, just a little summary on my unsupported problem with systemd journal.

Those are all the steps I already tried:

  1. update OS-agent to 1.4.1
  2. update HA to 2022.11.1
  3. reinstall the systemd journal service
  4. update / upgrade Debian Bullseye
  5. rerun the supervised installer
  6. reinstall Docker
  7. multiple host restarts

Still unsupported… :frowning:

4

It’s in here. Was added 2 months ago. It’s in the release notes of v1.3.0 of the supervised installer. Now the latest version of supervisor uses this new service so if you don’t have it it tells you about it along with a link to instructions.

Appears the instructions had a bug so I put in a PR to fix it based on this discussion. Seems pretty complete to me, idk.

2 Likes
5

Not good.
Since the update I have 5 issues:
My installation is supervised on docker running on Openmediavault NAS.
Running rock solid until this update :frowning:

immagine

6

Sounds like you’ve gone through steps 1-4 of the supervised installer and still can’t shake that message. At that point it seems like there might be a bug with the supervised installer as I’m not really sure what else can be done.

Check if the gateway service is running I suppose but if there’s anything else that needs to be done then the installer needs to be updated to mention it.

1 Like
7

In host log in my ha I have this

Nov 03 20:10:41 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported
Nov 03 20:10:41 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not supported
Nov 03 20:10:41 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Failed to push the data from buffers to the network. Client may experience some delay (usually in range 200ms - 5 sec).
8

I had to re-run the whole install (just without docker), so basically:

apt-get install \
apparmor \
jq \
wget \
curl \
udisks2 \
libglib2.0-bin \
network-manager \
dbus \
systemd-journal-remote -y
wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb
dpkg -i homeassistant-supervised.deb

After that (and a solid period of time at first startup after the install :slight_smile: the error is finally gone. I didn’t need to restore the backup however, all files and settings remained in their original directories.

Oh, yeah, and in betweeen I updated to 2022.11.01 also, but I’m not sure, if that helped as there are no release notes yet.

1 Like
9

I did that too. It went just fine.
It turned off all the add-ons that were not watchdog’ed, however, so watch for that. Just had to flick them back on.

(General Comment)… If these changes are baffling you, perhaps HAOS is what you should be using. They take care of all that stuff for us…

10 
os-agent:armhf is already the newest version (1.2.2).

dpkg: dependency problems prevent configuration of homeassistant-supervised:
 homeassistant-supervised depends on os-agent.
11

None of those have anything to do with this release of HA core. The only thing new in this release of HA core is that it is making repairs to tell you about things that were already there. If you rollback to the prior version and go to Settings → System → Repairs → (top right menu) → System Information you will see your system is marked unsupported with those same 5 reasons.

If you believe everything is working fine for you then feel free to ignore them. What unsupported means is simply that, unsupported. An issue is only considered a bug if reproduced on a supported system. For any issues submitted with steps to reproduce on an unsupported system the author will be asked to reproduce them on a supported system otherwise the issue will be rejected. Instead they’ll be directed here to look for help from others in the community who may be in a similar situation.

2 Likes
13

That’s an older problem you missed the update for, months ago.

14

Just reverted to 2022.10.5 and no issue to be repaired.
I only have the notification of the new update.
What’s wrong then?
Thank you.

15

Like I said, your system is still unsupported. Check system information.

16

Hello,
here it is, it seems all correct…
It isn’t?

immagine
immagine608×566 28 KB

17

That’s not where I directed you. Click the link, it’s a my link, it’ll take you to the right place.

This is why we made the repairs, its very hidden right now.

Alternatively, enter this command in the CLI:

ha resolution info
18

The ‘Problems’ have a link that tells you exactly what to do to resolve them.

19

This is what I have on 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: active (running) since Thu 2022-11-03 19:46:00 CET; 41min ago
TriggeredBy: ● systemd-journal-gatewayd.socket
       Docs: man:systemd-journal-gatewayd(8)
   Main PID: 20473 (systemd-journal)
      Tasks: 2 (limit: 9334)
     Memory: 84.5M
     CGroup: /system.slice/systemd-journal-gatewayd.service
             └─20473 /lib/systemd/systemd-journal-gatewayd

Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not supported
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Failed to push the data from buffers to the network. Client may experience some de>
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not supported
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Failed to push the data from buffers to the network. Client may experience some de>
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not supported
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Failed to push the data from buffers to the network. Client may experience some de>
Nov 03 20:19:09 homeassistant systemd-journal-gatewayd[20473]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported

I run sudo journalctl --verify
As I see every journal file passed. I only got this few times

7fffed0: Unused data (entry_offset==0)
20

Uhm… here it is and is flagged as unsupported but not able to understand why.
I have to dig inside a bit…

## System Information

version | core-2022.10.5
-- | --
installation_type | Home Assistant Supervised
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.5
os_name | Linux
os_version | 5.19.0-0.deb11.2-amd64
arch | x86_64
timezone | Europe/Rome
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4930
Installed Version | 1.28.0
Stage | running
Available Repositories | 1130
Downloaded Repositories | 10

</details>

<details><summary>Home Assistant Cloud</summary>
`
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Debian GNU/Linux 11 (bullseye)
-- | --
update_channel | stable
supervisor_version | supervisor-2022.10.2
agent_version | 1.2.2
docker_version | 20.10.21
disk_total | 54.9 GB
disk_used | 20.5 GB
healthy | true
supported | failed to load: Unsupported
supervisor_api | ok
version_api | ok
installed_addons | File editor (5.4.1), Node-RED (13.5.1), Mosquitto broker (6.1.3), motionEye (0.18.0), Duck DNS (1.15.0), MariaDB (2.5.1), Home Assistant Google Drive Backup (0.108.4), ESPHome (2022.10.2), Zigbee2MQTT (1.28.1-1)

</details>

<details><summary>Dashboards</summary>

dashboards | 1
-- | --
resources | 5
views | 11
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | 25 ottobre 2022 17:08
-- | --
current_recorder_run | 3 novembre 2022 20:17
estimated_db_size | 518.23 MiB
database_engine | mysql
database_version | 10.6.8

</details>

<details><summary>Spotify</summary>

api_endpoint_reachable | ok
-- | --

</details>
21

These are the reasons why. You’re not understanding what I’m trying to tell you about how this works.

Supervisor decides when a system is unsupported and why, not core. For reference core is what you probably call HA and what the release notes at the top of this discussion are about. Supervisor is behind the scenes and updates out of band with core. So if your system was unsupported in version 2022.11 of HA/core it is also unsupported in version 2022.10.5 of HA/core for the same reasons.

The only thing that changed in this space between version 2022.11 of HA and 2022.10.5 is that starting in 2022.11 of HA/core repairs are added for each reason supervisor tells HA/core that the system is unsupported and/or unhealthy. Your screenshot shows those repairs so those are the reasons.

Updating to 2022.11 does not change whether a system is unsupported or unhealthy and neither does rolling back to 2022.10.5. It will be the same before and after with the same reasons. The only difference is 2022.11 you’ll see repairs and in 2022.10.5 you won’t because that feature didn’t exist yet.

7 Likes