Re: [knot-dns-users] failed in mdb_freelist_save()

2017-07-21 Thread Yoshihito Horigome
Hi,  Vladimir  Thank you for the detailed information.I set the value of fork (-f) to 1 and tried restarting but it did not recover as a result.In conclusion, restart succeeded by deleting cache.storage.Best regards. On 7月 21 2017, at 7:00 午後, Vladimír Čunát wro

Re: [knot-dns-users] failed in mdb_freelist_save()

2017-07-21 Thread Vladimír Čunát
On 07/21/2017 11:51 AM, Yoshihito Horigome wrote: > Thank you for the information. > Is fork still to be an experimental parameter? > > As it is commonly used, it is not mandatory as myself, so for the > moment I think whether to deal with the parameter removed. If you run kresd without (direct) s

Re: [knot-dns-users] failed in mdb_freelist_save()

2017-07-21 Thread Yoshihito Horigome
Hi,  Vladimir Thank you for the information.Is fork still to be an experimental parameter?As it is commonly used, it is not mandatory as myself, so for the moment I think whether to deal with the parameter removed.Best regards. On 7月 21 2017, at 6:45 午後, Vladimí

Re: [knot-dns-users] failed in mdb_freelist_save()

2017-07-21 Thread Vladimír Čunát
Hello! On 07/21/2017 11:31 AM, Yoshihito Horigome wrote: > /usr/sbin/kresd -c /etc/knot-resolver/kresd.conf -v -f 4 -k > /etc/knot-resolver/root.key /var/knot-resolver I don't immediately see what happens in your case, but so far kresd does not support running under systemd supervision with multi

[knot-dns-users] failed in mdb_freelist_save()

2017-07-21 Thread Yoshihito Horigome
Hi, allWhen we started knot resolver, we confirmed that the following message will be output and the process will end.What kind of problem is this?Jul 21 18:24:02 dns02 systemd[1]: Started Knot DNS Resolver daemon.Jul 21 18:24:02 dns02 systemd[1]: kresd.service: Got notification message from PID 23

Re: [knot-dns-users] Impossible to purge zone data for unconfigured zone

2017-07-21 Thread Anand Buddhdev
Hi Daniel and Jan, Thank you for your suggestions and acknowledgements. Regards, Anand On 21/07/2017 10:35, Daniel Salzman wrote: > Hello Anand and Jan, > > You are right. This case cannot be handled easily. We will extend the > zone-purge command > to be able to purge a specific unknown zone

Re: [knot-dns-users] Impossible to purge zone data for unconfigured zone

2017-07-21 Thread Daniel Salzman
Hello Anand and Jan, You are right. This case cannot be handled easily. We will extend the zone-purge command to be able to purge a specific unknown zone or all unknown zones from the databases (journal, timer, and kasp). Since Knot 2.5.0 it is easy because the databases are common for all zone

Re: [knot-dns-users] Impossible to purge zone data for unconfigured zone

2017-07-21 Thread Jan Včelák
Hey, I think your arguments make sense, Anand. I would just suggest slightly different solution: Add control command that removes all orphaned zones from the journal (knotc journal-gc). It will be more practical as you wouldn't have to call it for each zone you have removed. It will be idempotent