Open ghost opened 1 year ago
i have hit this too when using an lxc holding debian 12. my main workstation with debian 12 has a bunch of custom setup so i forget if that is also happening there.
(this was on the recent 0.4 debs)
Hello @thomas-ives and @majestrate,
I am the maintainer of Yggdrasil packages in the Debian distribution (though not of the Yggdrasil packages that the Yggdrasil project produces). We are a bit confused about this bug report. Can you help by:
grep yggdrasil /var/log/dpkg.log
?Thanks,
John
Possibly related to #1048
Shame to admit, but after troubleshooting by modifying the systemd service file, I've managed to solve a similar issue (Admin socket failed to listen: listen unix /var/run/yggdrasil.sock: bind: read-only file system
) by reviewing my configuration file, which I copy-pasted from a significantly older, previous installation.
Simply commenting out AdminListen: unix:///var/run/yggdrasil.sock
solved it for me.
Hi,
Sorry in advance for the amount of text
I installed yggdrasil from system's repo onto a freshly installed Debian 12 (bookworm):
1.1. It didn't automatically create /var/run/yggdrasil/ and subsequently complained about it's socket being unachievable
The rights are set as follows
The systemd unit config is vanilla one from deb package
1.2. Sometimes instead of the error above It gives me a permission error during interface creation (even when ran as 'yggdrasil'). It seems to be a race condition somewhere. I found it by restarting yggdrasil in a while true loop for debugging. Most errors are the same as the 1st one, and occasionally are as below.
Main user has the following groups:
I tried updating to latest release, but nothing seems to have changed
Where should I look next? I would appreciate any pointers)
Thanks