bind 9.16.1-ubuntu on ubuntu 20.04 randomly exits with segfault signal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
$ lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04
$ apt-cache policy bind9
bind9:
Installed: 1:9.16.1-0ubuntu2.9
Candidate: 1:9.16.1-0ubuntu2.9
Version table:
*** 1:9.16.1-0ubuntu2.9 500
500 http://
500 http://
From syslog:
Dec 14 16:19:10 dc-dns-02 kernel: [519037.010692] isc-worker0000[
t at 8 ip 00007f2e512d6166 sp 00007f2e4dfe4530 error 4 in libisc.
e512b4000+46000]
Dec 14 16:19:10 dc-dns-02 kernel: [519037.010706] Code: 00 00 48 8d 3d ab b4 02
00 e8 66 39 fe ff 66 0f 1f 44 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 53 48
83 ec 08 4c 8b 67 10 <41> 83 7c 24 08 02 0f 85 be 00 00 00 49 89 fd 49 8b 7c 24
10 48 89
Dec 14 16:19:18 dc-dns-02 systemd[1]: named.service: Main process exited, code=k
illed, status=11/SEGV
Dec 14 16:19:18 dc-dns-02 systemd[1]: named.service: Failed with result 'signal'
.
Checking the address gets:
00007f2e512d6166 – 7f2e512b4000 = 22166
Checking that far into libisc.so.1601.0.0 gets:
$ addr2line -e /usr/lib/
isc_lfsr_init
??:?
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-08-27 (131 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: bind9 1:9.16.1-0ubuntu2.9
PackageArchitec
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
bind9utils N/A
apparmor 2.13.3-7ubuntu5.1
Tags: focal uec-images
Uname: Linux 5.4.0-91-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
mtime.conffile.
mtime.conffile.
mtime.conffile.
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-08-27 (131 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2)
Package: bind9 1:9.16.1-0ubuntu2.9
PackageArchitec
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
bind9utils N/A
apparmor 2.13.3-7ubuntu5.1
Tags: focal uec-images
Uname: Linux 5.4.0-89-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
mtime.conffile.
mtime.conffile.
mtime.conffile.
tags: | added: server-triage-discuss |
tags: | removed: server-triage-discuss |
tags: | added: server-triage-discuss |
tags: | removed: server-triage-discuss |
Thank you for taking the time to report this bug. While segmentation fault definitely shouldn't happen, there isn't really enough information here for a developer to confirm this is a bug in Ubuntu and not some other kind of system corruption, especially given that there are no other reports of similar crashes, at least that I'm aware of.
Useful information would be:
* Did this start happening after upgrading to 1:9.16. 1-0ubuntu2. 9? Does downgrading to 1:9.16.1-0ubuntu2.8 (or to the version you were using before) stop the crashes? This is very important for us to know.
* Did you identify some minimal steps that are able to trigger the crash?
* Does the crash always happen at the same address?
I'm marking this bug report as Incomplete for the moment.