On HAOS in a VMware VM I get this…
It seems to function though.
It also has docker cgroup v2, which doesn’t get flagged as unhealthy/unsupported
systemctl status systemd-journal-gatewayd.socket
● systemd-journal-gatewayd.socket - Journal Gateway Service Socket
Loaded: loaded (/lib/systemd/system/systemd-journal-gatewayd.socket; enabled; vendor preset: disabled)
Active: active (running) since Fri 2022-11-11 16:58:26 AEDT; 10h ago
Triggers: ● systemd-journal-gatewayd.service
Docs: man:systemd-journal-gatewayd(8)
Listen: /run/systemd-journal-gatewayd.sock (Stream)
Tasks: 0 (limit: 9255)
Memory: 0B
CGroup: /system.slice/systemd-journal-gatewayd.socket
Nov 11 16:58:26 dock64 systemd[1]: Listening on Journal Gateway Service Socket.
systemctl status systemd-journal-gatewayd.service
● systemd-journal-gatewayd.service - Journal Gateway Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journal-gatewayd.service; indirect; vendor preset: disabled)
Active: active (running) since Fri 2022-11-11 13:58:51 UTC; 1h 12min ago
TriggeredBy: ● systemd-journal-gatewayd.socket
Docs: man:systemd-journal-gatewayd(8)
Main PID: 4784 (systemd-journal)
Tasks: 2 (limit: 2350)
Memory: 233.4M
CPU: 1.761s
CGroup: /system.slice/systemd-journal-gatewayd.service
└─ 4784 /usr/lib/systemd/systemd-journal-gatewayd
Nov 11 13:58:51 haosVM systemd[1]: Started Journal Gateway Service.
Nov 11 13:58:51 haosVM systemd-journal-gatewayd[4784]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
#
systemctl status systemd-journal-gatewayd.service
○ systemd-journal-gatewayd.service - Journal Gateway Service
Loaded: loaded (/usr/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)
systemctl start systemd-journal-remote
systemctl status systemd-journal-remote
× systemd-journal-remote.service - Journal Remote Sink Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journal-remote.service; indirect; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2022-11-11 14:05:30 UTC; 3s ago
TriggeredBy: ● systemd-journal-remote.socket
Docs: man:systemd-journal-remote(8)
man:journal-remote.conf(5)
Process: 4951 ExecStart=/usr/lib/systemd/systemd-journal-remote --listen-https=-3 --output=/var/log/journal/remote/ (code=exited, status=1/FAILURE)
Main PID: 4951 (code=exited, status=1/FAILURE)
Error: 2 (No such file or directory)
CPU: 199ms
Nov 11 14:05:30 haosVM systemd[1]: Started Journal Remote Sink Service.
Nov 11 14:05:30 haosVM systemd-journal-remote[4951]: Failed to read key from file '/etc/ssl/private/journal-remote.pem': No such file or directory
Nov 11 14:05:30 haosVM systemd[1]: systemd-journal-remote.service: Main process exited, code=exited, status=1/FAILURE
Nov 11 14:05:30 haosVM systemd[1]: systemd-journal-remote.service: Failed with result 'exit-code'.
pi 3b barebones install haos
I don’t have physical access to it atm to check further
I don’t have a barebones pi4 setup atm either.
Nov 11 16:35:33 homeassistant systemd-journal-gatewayd[13067]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
pi4 deb/docker/supervisor
healthy and supported
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 Fri 2022-11-11 17:04:37 AEDT; 10h ago
TriggeredBy: ● systemd-journal-gatewayd.socket
Docs: man:systemd-journal-gatewayd(8)
Main PID: 9117 (systemd-journal)
Tasks: 2 (limit: 9255)
Memory: 582.9M
CGroup: /system.slice/systemd-journal-gatewayd.service
└─9117 /lib/systemd/systemd-journal-gatewayd
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Failed to push the data from buffers to the network. Client ma>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not s>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not sup>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Failed to push the data from buffers to the network. Client ma>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not s>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not sup>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Failed to push the data from buffers to the network. Client ma>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not s>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not sup>
Nov 12 02:19:04 dock64 systemd-journal-gatewayd[9117]: microhttpd: Failed to push the data from buffers to the network. Client ma>
...skipping...
sudo systemctl status systemd-journal-gatewayd.socket
● systemd-journal-gatewayd.socket - Journal Gateway Service Socket
Loaded: loaded (/lib/systemd/system/systemd-journal-gatewayd.socket; enabled; vendor preset: disabled)
Active: active (running) since Fri 2022-11-11 16:58:26 AEDT; 10h ago
Triggers: ● systemd-journal-gatewayd.service
Docs: man:systemd-journal-gatewayd(8)
Listen: /run/systemd-journal-gatewayd.sock (Stream)
Tasks: 0 (limit: 9255)
Memory: 0B
CGroup: /system.slice/systemd-journal-gatewayd.socket
Nov 11 16:58:26 dock64 systemd[1]: Listening on Journal Gateway Service Socket.
sudo systemctl status systemd-journal-remote
● systemd-journal-remote.service - Journal Remote Sink Service
Loaded: loaded (/lib/systemd/system/systemd-journal-remote.service; indirect; vendor preset: disabled)
Active: inactive (dead)
TriggeredBy: ● systemd-journal-remote.socket
Docs: man:systemd-journal-remote(8)
man:journal-remote.conf(5)
Also for what its worth I couldn’t remove the
ha jobs options --ignore-conditions healthy
from one of my VMs (the only I had actually used that on)
ha job reset
ha jobs reset
ha supervisor restart
Wouldn’t clear the flag.
ha supervisor repair
Also didn’t clear it.
Even after a host reboot it was still getting flagged as unsupported due to the ignored flag.