20 Pro
2019
20 Pro
'19
16:24
There is no hardcoded ID in the server data :-)
Could you try to manually execute the server under root (knotd -c /etc/knot/knot.conf)?
Could you try to change the control socket location to a non-var directory
(https://www.knot-dns.cz/docs/2.9/singlehtml/index.html#control-listen)?
Daniel
On 12/20/19 3:02 PM, Alarig Le Lay wrote:
I just found this:
backup02 ~ # borg mount /home/alarig/backups/kaiminus-old/ /tmp/alarig/
backup02 ~ # grep knot /tmp/alarig/2019-12-19/etc/passwd
knot:*:553:553:Knot DNS Server:/nonexistent:/usr/sbin/nologin
kaiminus ~ # grep knot /etc/passwd
knot:x:53:53:User for knot DNS server:/var/lib/knot:/sbin/nologin
Perhaps the user ID is hardcoded somewhere in the storage and as long as
I had the whole old /var/db/knot inside my new /var/lib/knot, the UID
553 (which doesn’t exist on the new system) was used instead of 53?
On 20/12/2019 14:55, Alarig Le Lay wrote:
The socket wasn’t created at all, so I tried to
touch the file and chown
to knot, but same result. As knot dies if the socket doesn’t exist, it
wasn’t running until I removed /var/lib/knot.
On 20/12/2019 14:44, David Vašek wrote:
I meant, if it helps to *remove* the socket.
Sorry.
David
On 2019-12-20 14:43, David Vašek wrote:
> Hi,
>
> are you sure, that knot isn't running already (pgrep knotd)? If not,
> does it help to remote /var/run/knot/knot.sock manually before you
> start knot?
>
> David
>
>
> On 2019-12-20 13:56, Alarig Le Lay wrote:
>> Here is my config file: https://paste.swordarmor.fr/raw/kXaN
>>
>> The init script:
>> https://gitweb.gentoo.org/repo/sync/gentoo.git/tree/net-dns/knot/files/knot…
>>
>>
>> The content of the dirs (and what I kept in .old):
>> https://paste.swordarmor.fr/raw/IG3K
>>
>> The error wasn’t in the logs but in the shell (and I closed it since
>> then) when I tried to launch it directly from CLI. It was a permission
>> denied on /var/run/knot/knot.sock
>>
>> I don’t recall when I first installed knot on the FreeBSD machine, but
>> it was on the 10th release, so 2014~2015 if I refer to Wikipedia.
>>
>> Regards,
>> Alarig
>>
>> On 20/12/2019 13:30, David Vašek wrote:
>>> 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,
>>>>>>