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.
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
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.
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.
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.
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.
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.
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.
