Re: knot-resolver 6.5.0

[Matthias Fischer <matthias.fischer@ipfire.org>]

On 03.10.2026 11:57, Michael Tremer wrote:
> Hello Matthias,

Hi Michael,
> Thanks for the update.

No problem - it just came my way. ;-)
> It seems like the supervisor process wants to create a “logs” directory inside another directory.

Yep. Thats the way it looks like. But where?

 What that is, is hard to tell from the trace, but there cannot be many
possible options. What permissions does /var/log/knot-resolver have? I
suppose it cannot write to it.

Sorry, but there is no such directory. The only *logging* option I can
find is in 'config.yaml':

***SNIP***
# Enable logging
logging:
  level: info
  target: syslog
***SNAP***

And as I see it, everything is logged to '/var/log/messages'.

Some thoughts:
The line containing to the 'generic exception' refers to something like
'config_store'(rather often), 'config' or 'write_config_file' ending
with 'self._accessor.mkdir' resulting in 'PermissionError' but you never
get a clue where this 'directory'(!?) is missing or where it should
be... Frustrating.

And the current documentation ends with version 6.4.2
(https://www.knot-resolver.cz/documentation/latest/NEWS.html). Hm!

Best
Matthias

> -Michael
> 
>> On 3 Oct 2026, at 09:59, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>> 
>> Hi all,
>> 
>> as always, I'd like to have a problem during updates - perhaps 'someone'
>> has a clue?
>> 
>> This time its 'knot-resolver 6.5.0' who refuses to start. Compiling and
>> building was ok - no seen problems.
>> 
>> But after updating, 'knot_resolver.manager.server' runs into an
>> "uncaught generic exception during manager inicialization[sic]",
>> throwing a looong line, ending in "PermissionError: [Errno 13]
>> Permission denied:  'logs'". What does this "'logs'" mean? A directory?
>> Where should it be?
>> 
>> If 'someone' has the time to take a closer look, I attached a short
>> excerpt of the logfile plus my current lfs and rootfile.
>> 
>> Some thoughts: For building and compiling of the previous versions the
>> 'setcap'-command for 'kresd' in lfs is needed. With 'v6.5.0' there is a
>> additional binary - 'usr/bin/kres-manager'. Whatever this one is good
>> for, could it be that something similar 'setcap'-command or some
>> config-option for the 'meson setup' is needed here? I searched in
>> 'meson_options.txt' (Configuration options) but didn't find something
>> suitable.
>> 
>> I would be very thankful for any hints...
>> 
>> Best
>> Matthias
>> <log.dat - knot-resolver 6.5.0.txt><lfs - knot-resolver.txt><rootfile - knot-resolver.txt>