Open jlkDE opened 1 year ago
It looks like a bug with radicale. Interesting though, it looks like it's confused between ipv6 and ip4 for localhost for whatever reason (if I had to guess).
Ok, sounds plausible. As I have a workaround this does not bug me that much, do you think I should file an issue against radicale?
I am using etesync-dav via a virtual environment with system-site packages enabled on openSUSE Tumbleweed and therefore keep all packages up-to-date.
After my last update and without changing the configuration etesync-dav failed to start with the following traceback:
I tried searching for
localhost
inside of my configuration files without matches, afterwards I changed some hardcoded occurences oflocalhost
inside some the etesync-dav virtual env files, but both led to nothing.Then I tried to find out which package could have caused the error
unknown address family
: I was able to grep the string within the packages boltons and dnspython, but they were updated 9 and 6 months ago for me, so not recently.Lastly I moved the etesync data dir including the configurations and tried to start a clean instance, but the error remained.
These are the packages available inside the venv: pip-list.txt
Workaround
As a workaround I started etesync-dav with the environment variable
ETESYNC_LISTEN_ADDRESS=127.0.0.1
(or more specifically I added the lineEnvironment=ETESYNC_LISTEN_ADDRESS=127.0.0.1
to my systemd service unit.