Hi Jeroen,
just a quick reply - the debugging packages are now in separate
archive:
https://wiki.debian.org/AutomaticDebugPackages
Could you try installing debugging symbols and run this under
gdb and/or valgrind?
Also would you be able to provide the /var/lib/knot and /etc/knot
for inspection?
After backing-up /var/lib/knot you could try bisecting /var/lib/knot
by deleting journal .db files one by one and/or timers database.
We would be interested in seeing a corrupted .db file if you can
detect which one is causing the troubles.
Cheers,
--
Ondřej Surý -- Technical Fellow
--------------------------------------------
CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC
Milesovska 5, 130 00 Praha 3, Czech Republic
mailto:ondrej.sury@nic.cz
https://nic.cz/
--------------------------------------------
----- Original Message -----
From: "Jeroen Massar"
<jeroen(a)massar.ch>
To: "knot-dns-users" <knot-dns-users(a)lists.nic.cz>
Sent: Wednesday, 9 November, 2016 16:23:24
Subject: [knot-dns-users] Segfault in knot 2.3.1-1~bpo8+ and 2.3.2-1
Hola,
As recently a variety of people claimed to me that 'running DNSSEC is
not scary'.... I was like, lets try again after having tried it ~10
years ago and it failing miserably.
DNSSEC auto-maintain style looks to be better; still not as nice as
running dual-nsd's in master mode; but we'll live with those moving parts.
It ran fine for a bit, till I noticed the signatures of the zone had
expired and noticed the master simply did not bother to update the sigs
anymore. So much for 'automatic' mode.
Restarting it caused a nice crash:
Debian provided jessie-backports 2.3.1-1~bpo8:
```
knotd[6679]: *** Error in `/usr/sbin/knotd': double free or corruption
(out): 0x00007f4244042e80 ***
```
Then was like... lets try the latest edition:
Debian provided unstable 2.3.2-1:
```
knotd[11892] general protection ip:7fb8f7f0f218 sp:7fb8ce1cc3b0 error:0
in libc-2.24.so[7fb8f7e98000+195000]
````
yes, that is on a newer libc, hence different style error message it seems.
The 2.3.1 edition was able to report:
```
error: [
example.com] changes from journal applied 1 -> 1 (invalid parameter)
````
before crashing out, the 2.3.2 just borks out.
Unfortunately there are no dbgsym packages for those editions, thus
can't easily dig what goes wrong where without having to resort to
manually building it all.
I could also not find a way to signup to:
https://gitlab.labs.nic.cz/users/sign_in
to be able to file a ticket about this.
Any extra details that one should be providing outside of the above
(link to that list is welcome ;) )
Should I attempt knot-nightly?
Greets,
Jeroen
PS: News on
https://labs.nic.cz/en/ ends in April 2016...
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users