bind910-9.10.4 installed from package crash with these lines: 05-May-2016 14:34:35.528 general: critical: rbt.c:2726: INSIST(sibling != ((void *)0)) failed, back trace 05-May-2016 14:34:35.528 general: critical: #0 0x4189d8 in ?? 05-May-2016 14:34:35.528 general: critical: #1 0x5b812a in ?? 05-May-2016 14:34:35.528 general: critical: #2 0x4bc5c8 in ?? 05-May-2016 14:34:35.528 general: critical: #3 0x4c94be in ?? 05-May-2016 14:34:35.528 general: critical: #4 0x4c8b4b in ?? 05-May-2016 14:34:35.528 general: critical: #5 0x4c8448 in ?? 05-May-2016 14:34:35.528 general: critical: #6 0x4c39cc in ?? 05-May-2016 14:34:35.528 general: critical: #7 0x52d561 in ?? 05-May-2016 14:34:35.528 general: critical: #8 0x5d9305 in ?? 05-May-2016 14:34:35.528 general: critical: #9 0x801a37814 in ?? 05-May-2016 14:34:35.528 general: critical: #10 0x0 in ?? 05-May-2016 14:34:35.528 general: critical: exiting (due to assertion failure)
This is a bug in BIND9, please, report it to the ISC directly: https://www.isc.org/community/report-bug/
My two bind servers crashed recently as well. I suppose this is related to upgrade to 9.10.4, as they were working ok for months. Master: May 9 10:21:54 ns1 pkg: bind910 upgraded: 9.10.3P4 -> 9.10.4 ... 10-May-2016 16:19:58.630 general: critical: rbt.c:2726: INSIST(sibling != ((void *)0)) failed, back trace 10-May-2016 16:19:58.630 general: critical: #0 0x41888d in ?? 10-May-2016 16:19:58.630 general: critical: #1 0x5bdd6a in ?? 10-May-2016 16:19:58.630 general: critical: #2 0x4bce44 in ?? 10-May-2016 16:19:58.630 general: critical: #3 0x4c8841 in ?? 10-May-2016 16:19:58.630 general: critical: #4 0x4c7e9b in ?? 10-May-2016 16:19:58.630 general: critical: #5 0x4c77a3 in ?? 10-May-2016 16:19:58.630 general: critical: #6 0x4c4a36 in ?? 10-May-2016 16:19:58.630 general: critical: #7 0x4af8d0 in ?? 10-May-2016 16:19:58.630 general: critical: #8 0x4af405 in ?? 10-May-2016 16:19:58.630 general: critical: #9 0x533597 in ?? 10-May-2016 16:19:58.630 general: critical: #10 0x5dd808 in ?? 10-May-2016 16:19:58.630 general: critical: #11 0x80186f855 in ?? 10-May-2016 16:19:58.630 general: critical: #12 0x0 in ?? 10-May-2016 16:19:58.630 general: critical: exiting (due to assertion failure) Slave: May 9 10:25:43 ns2 pkg: bind910 upgraded: 9.10.3P4 -> 9.10.4 ... 11-May-2016 13:06:51.708 general: critical: rbt.c:2726: INSIST(sibling != ((void *)0)) failed, back trace 11-May-2016 13:06:51.708 general: critical: #0 0x41888d in ?? 11-May-2016 13:06:51.708 general: critical: #1 0x5bdd6a in ?? 11-May-2016 13:06:51.708 general: critical: #2 0x4bce44 in ?? 11-May-2016 13:06:51.708 general: critical: #3 0x4c8841 in ?? 11-May-2016 13:06:51.708 general: critical: #4 0x4c7e9b in ?? 11-May-2016 13:06:51.708 general: critical: #5 0x4c77a3 in ?? 11-May-2016 13:06:51.708 general: critical: #6 0x4c4a36 in ?? 11-May-2016 13:06:51.708 general: critical: #7 0x532d59 in ?? 11-May-2016 13:06:51.708 general: critical: #8 0x5dd808 in ?? 11-May-2016 13:06:51.708 general: critical: #9 0x801870855 in ?? 11-May-2016 13:06:51.708 general: critical: #10 0x0 in ?? 11-May-2016 13:06:51.708 general: critical: exiting (due to assertion failure) @Dmitry, did you report bug to ISC?
There was an email this morning on bind-users: https://lists.isc.org/pipermail/bind-users/2016-May/096851.html I'm kinda pondering what to do with it, and I'd like to wait a couple of days before committing any course of action, like rolling back to 9.10.3-P4.
Thank you for the information. I've easily reverted to bind910-9.10.3P3 thanks to older package in /var/cache/pkg. Let's wait and see...
I've seen this crash as well a couple of times on my amd64/10.3-STABLE box
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209553 and https://lists.freebsd.org/pipermail/freebsd-ports/2016-May/103104.html for additional details.
As in bug 209553, if anyone on this bug has either a core dump, or a good reproducer, I'd like to know. :)
ISC believe have identified the cause of this and are working on patch. Once they are confident the issue is fixed they will issue an updated 9.10.4. In the mean time 9.10.3 is the best course of action.
*** Bug 209553 has been marked as a duplicate of this bug. ***
Created attachment 170431 [details] patch-assertion The ISC has a tentative fix: https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=patch;h=04a6d1de64b2b600f1c3a67b82abc32392048692 Could you try and put the attached file in dns/bind910/files/patch-assertion and rebuild/reinstall ?
I've applied the patch and restarted named. Not sure how long to let it run before we declare it "fixed"
based on my monitor script mail, I was seeing a crash every 4-5 days. Since I applied this patch, no crashes. Can this get pushed to the tree?
And the ISC released -P1 releases for both 9.9 and 9.10, the ports have been updated.