Re: [knot-dns-users] Issue encountered during a migration from FreeBSD to Gentoo

Hello Alarig, could you please send us some more data? The config file and some output would be helpful, i.e. knot.conf, /etc/init.d/knot, ls -l /var/lib/knot /var/run/knot, and the knot logfile from the failed attempt. So far, it seems to us it should work. Thanks. Regards, David On 2019-12-20 09:55, Alarig Le Lay wrote: > Hi Daniel, > > Yes I’m sure the permissions were good, they are set by the package. I > pulled it from the official repo, and server.user were already set for > my old configuration. I also changed the storage (s/db/lib) before > running the daemon. > Plus, when I started the daemon with an empty /var/lib/knot (and just > rsynced my zones & keys) I didn’t changed any permission. > > I don’t use systemd by openrc. > > On 20/12/2019 09:30, Daniel Salzman wrote: >> Hi, >> >> Are you sure the permissions are right? >> Do you have 'server.user' configured? >> Where did you get the Knot DNS package for Gentoo? >> >> There are some differences between FreeBSD and Linux packages with >> systemd enabled. >> >> Daniel >> >> On 12/19/19 11:33 PM, Alarig Le Lay wrote: >>> Hi, >>> >>> Today I migrated my knot from FreeBSD to Gentoo (because it take too >>> much time to stay on a supported release of FreeBSD) >>> >>> I rsynced my knot.conf (and changed the paths) and /var/db/knot to >>> /var/lib/knot >>> >>> However, daemon failed to start because it wasn’t able to bind to >>> /var/run/knot/knot.sock, and the permissions where good. I had to >>> remove >>> /var/db/knot and rsync only zones and keys. >>> >>> I don’t get the link from files in /var/lib and a denied permission on >>> /var/run/knot/knot.sock, so I think that there is a bug here. >>> >>> Regards, >>>