gdbus introspect --system --dest io.hass.os --object-path /io/hass/os
node /io/hass/os {
interface org.freedesktop.DBus.Introspectable {
methods:
Introspect(out s out);
signals:
properties:
};
interface org.freedesktop.DBus.Properties {
methods:
Get(in s interface,
in s property,
out v value);
GetAll(in s interface,
out a{sv} props);
Set(in s interface,
in s property,
in v value);
signals:
PropertiesChanged(s interface,
a{sv} changed_properties,
as invalidates_properties);
properties:
};
interface io.hass.os {
methods:
signals:
properties:
@org.freedesktop.DBus.Property.EmitsChangedSignal("invalidates")
readonly s Version = '1.4.1';
@org.freedesktop.DBus.Property.EmitsChangedSignal("true")
readwrite b Diagnostics = false;
};
};
That command shows that the os-agent is installed.
I understand that its installed but ie. homeassistant-supervised v1 requires os-agent v1. If you install homeassistant-supervised v2 it will throw you a dependency problem because this v2 requires os-agent v2.
With respect to systemd-journal-gatewayd and unsupported installs, first step is install the package.
# apt-get install systemd-journal-remote -y
OK, so here’s what the HA installer actually does and how it differs from the default Debian/Raspbian installation.
The HA installer creates the file /usr/lib/systemd/system/systemd-journal-gatewayd.socket. This has a different socket specified from the default, IE this is the key line:
ListenStream=/run/systemd-journal-gatewayd.sock
In my case on Debian/Raspbian, I don’t want the HA startup file in that location because it’s going to be overwritten by any OS upgrades to that package. The better way is to use the /etc directory for systemd.
# cp /usr/lib/systemd/system/systemd-journal-gatewayd.socket /etc/systemd/system
# vi /etc/systemd/system/systemd-journal-gatewayd.socket
Change the ListenStream line as follows and save/exit:
ListenStream=/run/systemd-journal-gatewayd.sock
Yes, for me too. The issue on Github leaded me to the problem. using wget I got a new package with .1 at the end homeassistant-supervised.deb.1, but the install command called homeassistant-supervised.deb, so an old image was installed.
Sad, I did overlooked this…
But, hey, full reinstall of the package as a solution to keep a system running is still weird…
I had to do the same, but the warning is still present - although I’m not sure that the service has been configured properly, not sure what the configuration is supposed to be though
UNIT LOAD ACTIVE SUB DESCRIPTION
containerd.service loaded active running containerd container runtime
cron.service loaded active running Regular background program processing daemon
dbus.service loaded active running D-Bus System Message Bus
docker.service loaded active running Docker Application Container Engine
[email protected] loaded active running Getty on tty1
haos-agent.service loaded active running Home Assistant OS Agent
hassio-supervisor.service loaded active running Hass.io supervisor
NetworkManager.service loaded active running Network Manager
polkit.service loaded active running Authorization Manager
rsyslog.service loaded active running System Logging Service
ssh.service loaded active running OpenBSD Secure Shell server
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-resolved.service loaded active running Network Name Resolution
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
udisks2.service loaded active running Disk Manager
unattended-upgrades.service loaded active running Unattended Upgrades Shutdown
[email protected] loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicant
I was originally using the -d option (for an alternate directory) with the original supervisor install.sh script which was apparently deprecated for the deb file which forces everything into /usr/share/hassio, from what I can tell. This is causing my installation to be borked now. I’m attempting to remove all my customizations so I can perform a fresh install to the /usr/share/hassio location and then restore a backup…
The full restore from backup sorta worked, the system is “up” but several sub-systems are semi-broken. The Add-ons are all greyed out like Home Assistant doesn’t know that they’re running even though I can see them in the docker container ls results. Also they appear to be up when I query them directly (bw, unifi), however ESPHome/Studio Code Server thinks they’re down and the ingress is unreachable because of that “Add-on is not running. Please start it first”. The Z-wave JS integration is broken, all devices offline and won’t load properly even though I can see in ha su logs it is complaining that core_zwave_js is already running!
How can I get my system back up and running at full strength?
After clearing the “systemd-journal” unsupported error , i got the following errors when searching the host log
Nov 04 09:20:25 Debian11-KVM systemd-journal-gatewayd[4081]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported
Nov 04 09:20:25 Debian11-KVM systemd-journal-gatewayd[4081]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not supported
Nov 04 09:20:25 Debian11-KVM systemd-journal-gatewayd[4081]: microhttpd: Failed to push the data from buffers to the network. Client may experience some delay (usually in range 200ms - 5 sec).
Same with command " sudo systemctl status systemd-journal-gatewayd.service"
I only looked at „latest“ in the wget but ignored the download directory. So happy now after hours of searching high and low.
the supervisor ugpraded from 1.2.2 to 1.3.1, but the error’s still popping - going to ignore it for now, I have work to do