Journal issues with supervised install after updating to 2022.11

183

This works for me. EXCEPT, since I run Adguard the computer couldn’t reach the home-assistent server.

Changed the DHCP to not use the HA Adguard ip and I could run the last command.

Now the message is gone.

Thank you for helping! (Can these commands be pinned somewhere so people can find it much easier?)

184

Thank you this helped me as well!

185

I’m still having issues with this, using the latest installer.

Ignoring Apparmor (which breaks other items on my system and needs more thought) I have systemd-journal-gatewayd running. I have /run/systemd-journal-gatewayd.sock (empty file, owned by root) in place, and /lib/systemd/ contains systemd-journal-gatewayd (executable) but I’m now totally lost as to why HA can’t find it. Systemctl status systemd-journal-gatewayd returns that it is running, from /lib/systemd/system/systemd-journal-gatewayd.service and the CGroup contains /lib/systemd/systemd-journal-gatewayd

I’m lost as to what should be where and what should be referencing where, and why the installer doesn’t do this automatically.

186

Regarding

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

Should anybody be still looking for a solution, then the following can resolve it.
This problem is caused by Debian 11 having a too old version of libmicrohttpd12.

As per Since supervisor 2022.10.x host log not working correct on supervised installation · Issue #255 · home-assistant/supervised-installer · GitHub

The solution on Debian bullseye is to backport the package from Bookworm or Testing

Debian Resources:

Simple Backport Creation
Supported Architectures

Append the following to /etc/apt/sources.list

 #Debian testing packages sources
 deb-src http://deb.debian.org/debian/ testing main

Build it:

 sudo apt update
 sudo apt install packaging-dev debian-keyring devscripts equivs
 apt source libmicrohttpd12/testing
 cd libmicrohttpd-<version>
 sudo mk-build-deps --install --remove
 dch --bpo
 fakeroot debian/rules binary
 dpkg-buildpackage --build=binary --unsigned-changes

Install it:

cd .. 
sudo apt install ./libmicrohttpd12_<version>_<arch>.deb
187

I tried this but I get the following error message:

vmuser@debianVM:/usr/share/hassio/media$ sudo apt install ./libmicrohttpd12-dbgsym_0.9.77-3_amd64
Reading package lists... Done
E: Unsupported file ./libmicrohttpd12-dbgsym_0.9.77-3_amd64 given on commandline

Any idea? Running Debian on a core-i5

188

Had this problem when updating from 2024.03 to 2024.04. Using Raspberry Pi OS based on Debian 11. Even after 2 years, editing this file resolved the issue. Thank you.

189

which one? @reyalpreyalp , I started having this error

190

Sorry for late replay. I edited
/usr/lib/systemd/system/systemd-journal-gatewayd.socket
Here is how it looks like:

[Unit]
Description=Journal Gateway Service Socket
Documentation=man:systemd-journal-gatewayd(8)

[Socket]
#ListenStream=19531
ListenStream=/run/systemd-journal-gatewayd.sock

[Install]
WantedBy=sockets.target
191

I had this problem: “No systemd-journal-gatewayd Unix socket available”… always, but blocking for some functions since the 2024.5 update
It worked for me too, I run my Home Assistant on OS Ubuntu 22.04 on a cloud VM connected via VPN to the house.
Thank to all! @ reyalpreyalp

1 Like