Multiple intermittent socket failures during name resolutions

Bug #1804542 reported by Tateru Nino on 2018-11-21
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
Medium
Unassigned

Bug Description

Multiple instances like:

Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file

Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file

[public ipv6 address partially elided for privacy]

Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file

Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677

Tateru Nino (tateru-nino) wrote :
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you could then provide steps to reproduce the problem or otherwise explain why you believe this is a bug in Ubuntu rather than a problem specific to your system or network configuration, and then change the bug status back to New.

Changed in bind9 (Ubuntu):
status: New → Incomplete
Jon Schewe (jpschewe) wrote :

I too am seeing this problem. This is on a computer that I'm using as a router using NAT. I have a dual stack IPv6 setup. My ISP gives me an IPv6 subnet that I use for my internal network. I have attached my configuration files.

I received no errors with this configuration under Ubuntu 16.04, however I do see these errors under Ubuntu 18.04. So I believe it's a change in the bind deamon, perhaps a configuration open that I need to add.

I have tried turning on full debugging and it hasn't been terribly helpful. I can do that again if you have particular debugging options that should be enabled.

What other information can I provide to aide in debugging this?

I do also have this problem:

23-Jan-2019 10:20:25.869 general: error: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
23-Jan-2019 10:20:25.869 general: error: internal_send: ***.***.***.***#52218: Invalid argument
23-Jan-2019 10:20:25.869 client: warning: client @0x7f08800da560 ***.***.***.***#52218 (d3dsirqaj330mb.cloudfront.net): error sending response: invalid file

Please, note that this is a known BIND bug, that I think probably should make its way to the official Ubuntu BIND release:
https://gitlab.isc.org/isc-projects/bind9/issues/180

The main problem for this is that the patch must be backported to BIND 11, because it has marked as resolved only in BIND 13.2:
https://gitlab.isc.org/isc-projects/bind9/milestones/4

Is this patch feasible for the official BIND of the 18.04.1 release?

Andreas Hasenack (ahasenack) wrote :

Thanks for the pointers. I agree we should try to backport this.

Changed in bind9 (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: server-next
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers