So problem is solved for me, I've tried to start with just one zone which 
didn’t helped, but removing journal did. Many thanks to Daniel Salzman for kind 
help, maybe he will post some other details after analyzing our journal records.

--
Lukas Kocourek

> On 2019-10-15, at 12:27, [email protected] wrote:
> 
> Message: 5
> Date: Tue, 15 Oct 2019 11:56:26 +0200
> From: Lukáš Kocourek <[email protected]>
> To: [email protected]
> Subject: [knot-dns-users] 2.9.0 fails to start after upgrade
> Message-ID: <[email protected]>
> Content-Type: text/plain;     charset=utf-8
> 
> Hi,
> 
> I’ve upgraded from 2.8.4 to 2.9.0 (Ubuntu 18.04, using 
> ppa:cz.nic-labs/knot-dns-latest) and now knotd fail to start.
> After dispatching "service knot start" command knotd process immediately goes 
> to 100% CPU and after 3 minutes it’s killed by systemd because "Start 
> operation timed out”.
> 
> Here log from service start...
> 
> Oct 15 11:37:04 ns1-u18 knotc[4972]: Configuration is valid
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: Knot DNS 2.9.0 starting
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: loaded configuration file 
> '/etc/knot/knot.conf'
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: using reuseport for UDP
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: binding to interface X.X.X.X@53
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: binding to interface ::@53
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: loading 199 zones
> 
> [cut] - info that all zones will be loaded
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: [xxx.yyy.] zone will be loaded
> [/cut]
> 
> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: starting server
> Oct 15 11:38:34 ns1-u18 systemd[1]: knot.service: Start operation timed out. 
> Terminating.
> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: State 'stop-sigterm' timed 
> out. Killing.
> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: Killing process 4984 
> (knotd) with signal SIGKILL.
> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: Main process exited, 
> code=killed, status=9/KILL
> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: Failed with result 
> 'timeout'.
> 
> Any advice what to do?
> 
> Thank very much
> 
> --
> Lukas Kocourek
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Tue, 15 Oct 2019 12:27:34 +0200
> From: Daniel Salzman <[email protected]>
> To: [email protected]
> Subject: Re: [knot-dns-users] 2.9.0 fails to start after upgrade
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=utf-8
> 
> Hi Lukáš,
> 
> Could you try to temporarily disable some zones? We have no idea at the 
> moment :-(
> 
> Would it be possible to show me a snippet of your configuration?
> 
> Daniel
> 
> On 10/15/19 11:56 AM, Lukáš Kocourek wrote:
>> Hi,
>> 
>> I’ve upgraded from 2.8.4 to 2.9.0 (Ubuntu 18.04, using 
>> ppa:cz.nic-labs/knot-dns-latest) and now knotd fail to start.
>> After dispatching "service knot start" command knotd process immediately 
>> goes to 100% CPU and after 3 minutes it’s killed by systemd because "Start 
>> operation timed out”.
>> 
>> Here log from service start...
>> 
>> Oct 15 11:37:04 ns1-u18 knotc[4972]: Configuration is valid
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: Knot DNS 2.9.0 starting
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: loaded configuration file 
>> '/etc/knot/knot.conf'
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: using reuseport for UDP
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: binding to interface X.X.X.X@53
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: binding to interface ::@53
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: loading 199 zones
>> 
>> [cut] - info that all zones will be loaded
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: [xxx.yyy.] zone will be loaded
>> [/cut]
>> 
>> Oct 15 11:37:04 ns1-u18 knotd[4984]: info: starting server
>> Oct 15 11:38:34 ns1-u18 systemd[1]: knot.service: Start operation timed out. 
>> Terminating.
>> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: State 'stop-sigterm' timed 
>> out. Killing.
>> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: Killing process 4984 
>> (knotd) with signal SIGKILL.
>> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: Main process exited, 
>> code=killed, status=9/KILL
>> Oct 15 11:40:04 ns1-u18 systemd[1]: knot.service: Failed with result 
>> 'timeout'.
>> 
>> Any advice what to do?
>> 
>> Thank very much
>> 
>> --
>> Lukas Kocourek
>> 

-- 
https://lists.nic.cz/mailman/listinfo/knot-dns-users

Reply via email to