public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: 'kresd' throws errors and warnings...
Date: Thu, 23 Jul 2026 10:03:41 +0100	[thread overview]
Message-ID: <D974CE36-94D6-4856-A2B7-C1217F53126C@ipfire.org> (raw)
In-Reply-To: <4440f4fb-6c9a-4a75-a688-0c81b7533eeb@ipfire.org>

Hello Matthias,

You are trying to start a Knot Resolver worker when Knot Resolver is already running in the background.

That is all about this one.

Best,
-Michael

> On 22 Jul 2026, at 15:00, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> Hi,
> 
> while searching for the reason why the zone files can't be updated or
> changed, I've found these earnings / errors from 'kresd':
> 
> ***SNIP***
> root@ipfire: ~ # kresd
> [system] warning: hard limit for number of file-descriptors is only 4096
> but recommended value is 524288
> [net   ] bind to '127.0.0.1@53' (TCP): Address already in use
> [system] error while loading config:
> /usr/lib/knot-resolver/postconfig.lua:42: bind to 127.0.0.1@53 error
> occurred here (config filename:lineno is at the bottom, if config is
> involved):
> stack traceback:
>        [C]: at 0x004162f0
>        [C]: in function 'pcall'
>        /usr/lib/knot-resolver/postconfig.lua:40: in main chunk
> ERROR: net.listen() failed to bind (workdir '/root')
> ***SNAP***
> 
> Can anyone confirm? Is there a need for action?
> 
> Best
> Matthias
> 



      reply	other threads:[~2026-07-23  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 14:00 Matthias Fischer
2026-07-23  9:03 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D974CE36-94D6-4856-A2B7-C1217F53126C@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=matthias.fischer@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox