Skip to content

traceback in logs since version 3.2.2

Description:

With the latest update to 3.2.2 and default service file provided with the package, a traceback is printed on every start of radicale:

radicale[17897]: [2024-07-03 19:34:50 +0200] [17897] [ERROR] Failed to connect to systemd journal: [Errno 97] Address family not supported by protocol
radicale[17897]: Traceback (most recent call last):
radicale[17897]:   File "/usr/lib/python3.12/site-packages/radicale/log.py", line 148, in _try_emit_journal
radicale[17897]:     journal_socket = socket.socket(
radicale[17897]:                      ^^^^^^^^^^^^^^
radicale[17897]:   File "/usr/lib/python3.12/socket.py", line 233, in __init__
radicale[17897]:     _socket.socket.__init__(self, family, type, proto, fileno)
radicale[17897]: OSError: [Errno 97] Address family not supported by protocol

AFAIK radicale will still be able be able to log via stdout instead of the journald socket. But the traceback is annoying when reviewing server logs. So I guess it may better to remove AF_UNIX from RestrictAddressFamilies.

Additional info:

  • radicale 3.2.2
  • shipped Arch Linux default systemd service file

Not an upstream bug but discussed on the project site already: https://github.com/Kozea/Radicale/issues/1532

Steps to reproduce:

  1. journalctl -b -u radicale
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information