bind 9.12.3-P1 fatal error
Summary
I upgraded from 9.12.3 to 9.12.3-P1 2 days ago and today 2 of our 5 servers get fatal error and crashes with about 2 hours between each other. I started them again and everything seems normal again. We have no dynamic zones on these 2 servers.
Now i has happen again with another server, same version and the same behavior.
BIND version used
BIND 9.12.3-P1 id:cfdd35f running on Linux x86_64 3.10.0-862.14.4.el7.x86_64 #1 SMP Fri Sep 21 09:07:21 UTC 2018 built by make with '--prefix=/service/dns/bind-9.12.3-P1' '--sysconfdir=/data/dns/named' '--localstatedir=/var' '--with-openssl=/service/dns/openssl' '--enable-threads' '--with-libxml2' '--with-randomdev=/dev/urandom' compiled by GCC 4.8.5 20150623 (Red Hat 4.8.5-28) compiled with OpenSSL version: OpenSSL 1.0.2q 20 Nov 2018 linked to OpenSSL version: OpenSSL 1.0.2q 20 Nov 2018 compiled with libxml2 version: 2.9.1 linked to libxml2 version: 20901 compiled with zlib version: 1.2.7 linked to zlib version: 1.2.7 threads support is enabled
Steps to reproduce
Don't know.
What is the current bug behavior?
Fatal error and bind craches.
What is the expected correct behavior?
Not relevant
Relevant configuration files
options { recursion yes; dnssec-enable yes; dnssec-validation no; version "hakan 181213"; directory "/data/dns/named"; query-source address 194.165.224.190; allow-recursion { norrnod; }; listen-on { interfaces; }; allow-transfer { transferservers; key dns.umea.se.key; }; };
Relevant logs and/or screenshots
named1 15-Dec-2018 12:22:17.925 general: critical: rbtdb.c:1509: fatal error: 15-Dec-2018 12:22:17.925 general: critical: RUNTIME_CHECK(rbtdb->next_serial != 0) failed 15-Dec-2018 12:22:17.925 general: critical: exiting (due to fatal error in library)
named2 15-Dec-2018 13:50:58.260 general: critical: rbtdb.c:1509: fatal error: 15-Dec-2018 13:50:58.260 general: critical: RUNTIME_CHECK(rbtdb->next_serial != 0) failed 15-Dec-2018 13:50:58.260 general: critical: exiting (due to fatal error in library)
Possible fixes
Not relevant