named sevice stoped with SIGABRT errors

[tejas_sarade]

Hi,

I am facing a weird and rare issue. Named service on CentOS 7 stopped all of the sudden with following error message. I am not sure in what conditions ABRT is triggered. Even there is core memory dump but I don't understand that.
I feel like it is bug or something named or related service. Can anyone explain what is happening here.

May 7 00:26:11 localhost abrt-hook-ccpp: Process 23576 (named) of user 25 killed by SIGABRT - dumping core
May 7 00:26:12 localhost abrt-hook-ccpp: Failed to create core_backtrace: waitpid failed: No child processes
May 7 00:26:12 localhost systemd: named.service: main process exited, code=killed, status=6/ABRT

reason: named killed by SIGABRT
cmdline: /usr/sbin/named -u named
executable: /usr/sbin/named
package: bind-9.9.4-38.el7_3.2
component: bind
pid: 23576
pwd: /var/named
hostname: localhost
count: 1
abrt_version: 2.1.11
analyzer: CCpp
architecture: x86_64
event_log:
global_pid: 23576
kernel: 3.10.0-514.10.2.el7.x86_64
last_occurrence: 1494109571
os_release: CentOS Linux release 7.3.1611 (Core)
pkg_arch: x86_64
pkg_epoch: 32
pkg_fingerprint: 24C6 A8A7 F4A8 0EB5
pkg_name: bind
pkg_release: 38.el7_3.2
pkg_vendor: CentOS
pkg_version: 9.9.4
runlevel: N 3
time: Sun 07 May 2017 12:26:11 AM CEST
type: CCpp
uid: 25
username: named
uuid: 155467a37aa3ca9f748855ef6f2a952324d45170

[TrevorH]

package: bind-9.9.4-38.el7_3.2
kernel: 3.10.0-514.10.2.el7.x86_64

There is a bind-9.9.4-38.el7_3.3.x86_64 that fixes the following:

* Wed Apr 12 2017 Petr Menšík <pemensik@redhat.com> - 32:9.9.4-38.3
- Fix CVE-2017-3136 (ISC change 4575)
- Fix CVE-2017-3137 (ISC change 4578)

There's also a much newer kernel than the one you are running kernel-3.10.0-514.16.1.el7.x86_64.

[tejas_sarade]

Yes, that's correct. Thanks for providing specific CVE numbers.
I did a little more digging and found following logs.
Named server indeed exited with 'assertion failure' error as described in CVE-2017-3137. Got to update named.

07-May-2017 00:26:11.604 general: critical: resolver.c:4346: INSIST(fctx->type == ((dns_rdatatype_t)dns_rdatatype_any) || fctx->type == ((dns_rdatatype_t)dns_rdatatype_rrsig) || fctx->type == ((dns_rdatatype_t)dns_rdatatype_sig)) failed, back trace
07-May-2017 00:26:11.605 general: critical: #0 0x7f006f1c5ec0 in ??
07-May-2017 00:26:11.605 general: critical: #1 0x7f006d3a202a in ??
07-May-2017 00:26:11.605 general: critical: #2 0x7f006ea9138b in ??
07-May-2017 00:26:11.605 general: critical: #3 0x7f006d3c4ba6 in ??
07-May-2017 00:26:11.605 general: critical: #4 0x7f006cf75dc5 in ??
07-May-2017 00:26:11.605 general: critical: #5 0x7f006bfee73d in ??
07-May-2017 00:26:11.605 general: critical: exiting (due to assertion failure)