This bug was fixed in the package bind9 - 1:9.11.3+dfsg-1ubuntu1.10
---
bind9 (1:9.11.3+dfsg-1ubuntu1.10) bionic; urgency=medium
* d/p/fix-socket-failures-during-name-resolution.patch: fix socket failures
due to uninitialized memory during name resolution (LP: #1804542)
-- Luc
I've installed the patch on a 2nd server with heavy traffic, and all run
as flawlessly as with the previous patch. I think this patch totally fix
the issue and it does not introduce bad behaviours (as far as I've
seen).
** Tags removed: verification-needed-bionic
** Tags added: verification-done-b
Had this problem on one of my servers (the only one running bind on
Bionic), installed this proposed-update package on Thursday morning,
31st, and have not seen this error since then. Searching through my logs
I saw this error appearing at least every second day - often more than
once a day - and h
Hi,
I had the same problem on bionic and after using the proposed version
from this bug report the error does not display anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU]
Please remember that in order for this update to be released, the tags
need to be updated, as explained in comment #16.
Thanks for testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title
Hi Łukasz,
I'm testing the proposed patch
(https://launchpad.net/ubuntu/+source/bind9/1:9.11.3+dfsg-1ubuntu1.10/+build/17958751).
As with the previous patch by Bryce
(https://launchpad.net/~bryce/+archive/ubuntu/bind9-sru-1804542),
everything seems ok by now, with correct operation and absence of
Roberto, could you re-verify if the changes fix your bug by using the
packages in bionic-proposed? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU] Multiple intermittent so
Hello Tateru, or anyone else affected,
Accepted bind9 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bind9/1:9.11.3+dfsg-
1ubuntu1.10 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Lucas has a MP prepared at
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/bind9/+git/bind9/+merge/373431
** Changed in: bind9 (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/bind9/+git/bind9/+merge/373431
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU] Multiple int
** Description changed:
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
- TBD
+ There is no known self contained test case for this bug. However, after the
feedback of the bug reporter [1][2] looks the proposed patch is properly fixing
the bug.
+
** Changed in: bind9 (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU] Multiple intermittent socket f
Bryce, I think this can perhaps be proposed and uploaded, given the
previous comments. For the actual [test] section of the sru, perhaps
point at the comments above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I've tested the patch in two servers with heavy dns traffic showing the
problem, and it has totally disappeared after installation. Also I
haven't noticed any issue in the service after applying the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Thanks for the patch!
I've installed it on a server that showed the problem and it hasn't appeared
anymore.
In next days I'll apply it to another server showing the problem with more
traffic, and I'll let you know the conclusions.
--
You received this bug notification because you are a member o
I've packaged the patch from comment #9 into a PPA for testing purposes:
https://launchpad.net/~bryce/+archive/ubuntu/bind9-sru-1804542
To test with this, first ensure you can reproduce the issue in a
reliably consistent way, then install this package and run it for a
similar period with simila
Can someone help define steps to reproduce this issue? Ideally in a
vanilla install or ideally in a container.
The SRU process requires a test case for validating the change, that
flags the error before the package installation, and checks the absence
of the error after the package installation.
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU] Multiple intermittent socket failures during name resolutions
To manage notifications about this bug go
The originally flagged patch was [2/2] of a 2-patch set (AIUI), and the
second doesn't make much sense to include without the first. The two
patches also had a tiny dependence on a one tiny piece of an earlier
third patch that was a smorgasbord of valgrind memcheck fixes. Applying
these three com
** Changed in: bind9 (Ubuntu)
Status: Triaged => Fix Released
** Also affects: bind
Importance: Undecided
Status: New
** Changed in: bind
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Description changed:
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
TBD
[Regression Potential]
- Things to watch for would include memory-related issues and faults relating
to long names or addresses. The patch changes memory managemen
** Also affects: bind9 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: bind9 (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU] Multiple intermittent socket failures during name resolutions
To manage notifications about this bug go to:
h
The upstream commit message is vague in explaining what was going on,
but I'm gathering there was uninitialized data in a variable that would
trigger the error message? The fix appears to be switching to a static
buffer and initializing it to {0}.
** Description changed:
+ [Impact]
+ Socket fail
** Patch added: "The upstream commit"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804542/+attachment/5269458/+files/49f90025a07be39d1236504d46db3ce73f1578ee.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Looks like the patch that was applied is https://gitlab.isc.org/isc-
projects/bind9/merge_requests/409, but it doesn't apply cleanly, so it's
not an immediate candidate for the server-next queue.
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubun
** Summary changed:
- Multiple intermittent socket failures during name resolutions
+ [SRU] Multiple intermittent socket failures during name resolutions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
27 matches
Mail list logo
