I was looking to upgrade to 9.18 from ISC's repo, since we're interested
in DOT/DOH here, but I'll hold off on that until after 22.04.01 just in
case you get some time to dig into this again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the feedback, Michael.
First of all, let me say that we appreciate the help you've been
providing here. Given that we are not able to reproduce the bug here,
we depend on your reports in order to make progress and take decisions
regarding it.
Unfortunately, I think it will be hard
It's been a month now, and no crashes on any of my three servers with this
version of bind. Looks like this version is good (for me).
If you want to bisect, I'll keep helping with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just finished adding that ppa and upgrading bind9 to 9.16.15 from there on all
my servers. Removed the other one too.
Give it another month to see what happens now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello, here is the PPA:
https://launchpad.net/~paride/+archive/ubuntu/lp1954854-bind9
The package built fine on Focal without modifications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954854
Hello Michael, thanks for reporting back. Honestly I'm not sure on how
to proceed on debugging this. I'll go back my first comment and suggest
trying a newer version of bind9 to check if the issue is gone in the
newer upstream releases.
I'm preparing a PPA with Jammy's bind9 (1:9.16.15-1ubuntu3)
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954854
Title:
bind 9.16.1-ubuntu on ubuntu 20.04 randomly exits with segfault signal
To manage notifications
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954854
Title:
bind 9.16.1-ubuntu on ubuntu 20.04 randomly exits with segfault signal
To manage notifications
And the other server:
Jan 29 07:15:54 dc-dns-01 named[648]: client @0x7f67b057e930
10.126.63.77#51569: view internal: update '63.126.10.IN-ADDR.ARPA/IN' denied
Jan 29 07:15:55 dc-dns-01 named[648]: tcp.c:855:
REQUIRE((__builtin_expect(!!((sock) != ((void *)0)), 1) &&
Bind crashed again, this time the log is much different.
Jan 28 22:04:44 dc-dns-02 named[647]: network unreachable resolving
'q-seeqcview.com/A/IN': 2600:9000:5302:fc00::1#53
Jan 28 22:04:47 dc-dns-02 named[647]: tcp.c:855:
REQUIRE((__builtin_expect(!!((sock) != ((void *)0)), 1) &&
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954854
Title:
bind 9.16.1-ubuntu on ubuntu 20.04 randomly exits with segfault signal
To manage notifications
I have just finished adding that ppa and updating bind from there. I'll
give it a month, since it seems it can be that long between crashes, and
let you know the results; if not sooner.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
With Bryce's initial analysis in mind, I started digging to see what
upstream has done to fix this problem. I could not find upstream bug
reports similar to this one, but I did notice that they're being more
careful when accessing some variables in the code mentioned above
(things under
From the 114 crash file:
(gdb) bt
#0 isc__nm_tcp_send (handle=0x7eff7522dbb0, region=0x7eff7d39a9b8,
cb=0x7eff887675a0 ,
cbarg=0x7eff7d39a9a8) at tcp.c:852
#1 0x7eff88a2e707 in client_sendpkg (client=client@entry=0x7eff754c31b0,
buffer=,
buffer=) at client.c:331
#2
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954854
Title:
bind 9.16.1-ubuntu on ubuntu 20.04 randomly exits with segfault signal
To manage notifications
** Attachment added: "Crash file from another server, apport posts to follow."
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1954854/+attachment/5551855/+files/_usr_sbin_named.114.crash
** Description changed:
$ lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release:
** Attachment added: "bind9 crash file"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1954854/+attachment/5551831/+files/_usr_sbin_named.115.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
$ 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
Thanks for the info Michael,
without steps to reproduce I see two paths from here.
## #1 trying different versions
As Paride asked it might be worth to check different versions.
There is no super-convenient way to downgrade bind9
You can add all of Bionics (or any other release in between
This started happening when I upgraded the server from Ubuntu 18.04 to
20.04. Is there a convenient way to downgrade to 9.10.3?
As far as triggering the crash, I'm not sure. As I said it seems to happen
randomly. I suspect it's related to the amount of load on the service.
Here's a grep from
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
21 matches
Mail list logo
