Project

General

Profile

Bug #10760

pfSense BIND 9.14.12 server terminates due to assertion failure

Added by Jeffrey Altman about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
High
Assignee:
-
Category:
BIND
Target version:
-
Start date:
07/11/2020
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.5-p1
Affected Architecture:
amd64

Description

BIND is periodically terminating and not automatically restarted. The system log shows:

Jul 6 13:13:21 named 66921 client.c:1625: INSISTdns_rcode_noerror) && rcode != ((dns_rcode_t)dns_rcode_nxdomain)) failed, back trace
Jul 6 13:13:21 named 66921 #0 0x438e30 in ??
Jul 6 13:13:21 named 66921 #1 0x6133ea in ??
Jul 6 13:13:21 named 66921 #2 0x473f3a in ??
Jul 6 13:13:21 named 66921 #3 0x482926 in ??
Jul 6 13:13:21 named 66921 #4 0x47ff6a in ??
Jul 6 13:13:21 named 66921 #5 0x486b6b in ??
Jul 6 13:13:21 named 66921 #6 0x480ef0 in ??
Jul 6 13:13:21 named 66921 #7 0x47f5d0 in ??
Jul 6 13:13:21 named 66921 #8 0x4833b3 in ??
Jul 6 13:13:21 named 66921 #9 0x476078 in ??
Jul 6 13:13:21 named 66921 #10 0x630002 in ??
Jul 6 13:13:21 named 66921 #11 0x8020c40b6 in ??
Jul 6 13:13:21 named 66921 exiting (due to assertion failure)

The version information is:

Jul 11 16:51:24 named 69484 starting BIND 9.14.12 (Stable Release) <id:f3dc26e>
Jul 11 16:51:24 named 69484 running on FreeBSD amd64 11.3-STABLE FreeBSD 11.3-STABLE #239 885b1ed26b6(factory-RELENG_2_4_5): Tue Jun 2 17:53:42 EDT 2020 :/build/factory-crossbuild-245-amd64/obj/amd64/kkVaWThR/build/factory-crossbuild-245-amd64/sources/FreeBSD-src/sys/pfSense
Jul 11 16:51:24 named 69484 built with '--localstatedir=/var' '--disable-linux-caps' '--with-libxml2=/usr/local' '--with-readline=-L/usr/local/lib -ledit' '--with-dlopen=yes' '--with-openssl=/usr' '--sysconfdir=/usr/local/etc/namedb' '--with-dlz-filesystem=yes' '--disable-dnstap' '--disable-fixed-rrset' '--without-geoip2' '--without-gssapi' '--with-libidn2=/usr/local' '--with-libjson=/usr/local' '--disable-largefile' '--with-lmdb=/usr/local' '--disable-native-pkcs11' '--without-python' '--disable-querytrace' 'STD_CDEFINES=-DDIG_SIGCHASE=1' '--enable-tcp-fastopen' '--with-tuning=default' '--disable-symtable' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/share/info/' '--build=amd64-portbld-freebsd11.3' 'build_alias=amd64-portbld-freebsd11.3' 'CC=cc' 'CFLAGS=-O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing ' 'LDFLAGS= -fstack-protector-strong ' 'LIBS=-L/usr/local/lib' 'CPPFLAGS=-DLIBICONV_PLUG -isystem /usr/local/include' 'CPP=cpp' 'PKG_CONFIG=pkgconf'

What additional information would be useful to identify the source of the problem?

History

#1 Updated by Jeffrey Altman about 1 month ago

The assertion failure is in ns_client_error() which means that its impossible to file a reasonable report upstream without a translation of the stack trace. Can you assist with converting the logged stack trace from function pointer addresses to names?

#2 Updated by Jeffrey Altman about 1 month ago

Secondary question, is there is method to configure pfSense to auto-restart named on failure?

Also available in: Atom PDF