8 Lis
2024
8 Lis
'24
10:14
Hi Erik,
You shouldn't change the service type (Type=notify). That's why you don't
see knot.sock IMO.
You can enable https://www.knot-dns.cz/docs/3.4/singlehtml/index.html#async-start,
which helps with the long startup. However, Knot will still not be able to respond
from the zones until they are fully loaded!
What is your CPU? Maybe you should optimize the configuration (e.g.
https://www.knot-dns.cz/docs/3.4/singlehtml/index.html#signing-threads,
and/or https://www.knot-dns.cz/docs/3.4/singlehtml/index.html#server-background-wo…).
800 zones isn't much. Are the zones huge? Or do you use an HSM?
Daniel
On 11/8/24 09:50, Erik P. Ostlyngen via knot-dns-users wrote:
Hi,
I'm running an instance of knotd for testing. It is installed with the
official ubuntu debian package from kont-dns.cz. When I start the knot
service, using systemctl, it takes a very long time to start up
(sometimes 30 min). This seems to be related to the systemd unit which
is set to type 'notify', and the fact that knot after starting up
wants to re-sign all the zones which needs that before notifying. If I
change the type to 'simple' or 'forked' (together with the knotd -d
option), the start command returns more immediately. My test system
has about 800 zonefiles in it. A large number of them want to be
re-signed after each startup.
My question is, what is the recommended way to start, stop and restart
the server? Also, after starting I cannot find the /run/knot/knot.sock
file, which is needed when stopping the service with 'knotc stop'.
Knot version: 3.4.1-cznic.1~focal (debian package from knot-dns.cz)
OS: Linux 5.4.0/Ubuntu 20.04 Focal amd64.
Kind regards,
Erik Østlyngen
Norid
--