Failed to get add-on logs, No systemd-journal-gatewayd Unix socket available

Help, after a restore on Proxmox via Proxmox Backup Server, everything went perfectly except now I am receiving the following error when attempting to views the logs for any of the add-ons.

Failed to get add-on logs, No systemd-journal-gatewayd Unix socket available

Any idea how I can resolve this?

Thanks

Hi @deanfourie.
I have the same issue on my Zigbee2MQTT addon:

Failed to get add-on logs, No systemd-journal-gatewayd Unix socket available

Now I have all my devices down.

My HA instalation is:

  • Core 2024.5.0
  • Supervisor 2024.04.4
  • Frontend 20240501.0

on an android box with Debian GNU/Linux 10 (buster) / Linux 5.9.0-arm-64

Can anyone, please, help?

Supervised is already a long time not supported on Buster. Try to upgrade to Bookworm.

sudo apt install systemd-journal-remote

But it’s been running fine for ages.

It’s only happened since the restore which is strange.

Hi @francisp. Thanks for your help.
I updated to Debian 11 but still get some errors in HA after reboot:

Unsupported system - CGroup version

Unsupported system - Systemd Journal issues

Unsupported system - Connectivity check disabled


I tried to run your command but get an error:

dpkg: cannot write to log file ‘/var/log/dpkg.log’: No space left on device
dpkg: cannot write to log file ‘/var/log/dpkg.log’: No space left on device
dpkg: cannot write to log file ‘/var/log/dpkg.log’: No space left on device
E: Write error - ~LZMAFILE (28: No space left on device)


mikegodin23@armhassio:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.4G 0 1.4G 0% /dev
tmpfs 360M 39M 322M 11% /run
/dev/mmcblk2p2 56G 34G 23G 61% /
tmpfs 1.8G 0 1.8G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.8G 0 1.8G 0% /tmp
/dev/mmcblk2p1 488M 58M 430M 12% /boot
/dev/zram0 49M 48M 0 100% /var/log
tmpfs 360M 0 360M 0% /run/user/1000

I fixed this by

  1. Updating from buster to bookworm
  2. Following these instructions
    SystemD Journal warning is still there after 6 months - #8 by francisp

I have the same issue with Zigbee2MQTT, I’m running HA (hass.io) baremetal.

It’s down since I updated the core today - system didn’t reboot and required a hard restart.

Edit: I rolled back to 4.4 and Z2MQTT is working again - perhaps try that?