Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: glibc (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: systemd (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
ubuntu@foufoune:~$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
ubuntu@foufoune:~$ apt-cache policy systemd
systemd:
Installed: 234-2ubuntu12.3
Candidate: 234-2ubuntu12.3
Version table:
*** 234-2ubuntu12.3 500
500 http://azure.archive.ubuntu.com/ubuntu artful-up
I'm seeing this on Artful as well, in Azure cloud.
** Also affects: glibc (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status
This bug was fixed in the package systemd - 237-3ubuntu3
---
systemd (237-3ubuntu3) bionic; urgency=medium
* tests/control: drop qemu-system-ppc.
Whilst some tests pass, many regress / fail to boot. This is not a
regression,
as qemu-based tests were not run previously.
--
** Tags added: id-5a4e5d0285ca388b893cf09d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(compared to
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo()
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(compared to Xenial),
** Also affects: glibc (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Invalid
** Also affects: systemd (Ubuntu Bionic)
Importance: High
Status: Triaged
--
You received this bug notification beca
yes, but I'm not uploading systemd until after the build-farm is open.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much lon
Hi,
I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(compared to Xenial), pl
** Summary changed:
- Regression in getaddrinfo(): calls block for much longer on Bionic (compared
to Xenial)
+ Regression in getaddrinfo(): calls block for much longer on Bionic (compared
to Xenial), please disable LLMNR
--
You received this bug notification because you are a member of Kernel
avahi is zeroconf or IPv4LL, which is RFC 3927; whilst LLMNR is RFC
4795. In many aspects LLMNR is like mdns, yet the two are distinct and
resolve different things quite differently, when inspected closer.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
--
You received this
Workaround:
grep -q 'LLMNR=no' /etc/systemd/resolved.conf || \
echo 'LLMNR=no' | sudo tee -a /etc/systemd/resolved.conf
sudo service systemd-networkd restart
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(compared to Xenial)
St
Interesting; the first thing I tried when triaging this was to edit
/etc/nsswitch.conf as follows:
# hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns
... to eliminate the possibility that it was multicast DNS causing the
slowdown. But it appears I'm b
$ time systemd-resolve -p dns not-a-real-hostname
not-a-real-hostname: resolve call failed: No appropriate name servers or
networks for name found
real0m0.003s
user0m0.000s
sys 0m0.004s
$ time systemd-resolve -p llmnr not-a-real-hostname
not-a-real-hostname: resolve call failed: All
> The dns resolution from systemd-resolve is fast; the llmnr one is not.
> We currently have llmnr resolution enabled by default. ...it's a feature?!
It is not a feature for a local DNS resolver to be doing llmnr under the
hood by default. Please disable this.
> What is the use case of resolving
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on
$ systemd-resolve --status
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
The issue is with the systemd resolver not with glibc.
With systemd-resolve IP in /etc/resolv.conf:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
n
$ time ./test not-a-real-hostname
Trying to resolve: not-a-real-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)
real0m10.007s
user0m0.001s
sys 0m0.001s
--
You received this bug notification because you are a mem
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(compared to Xenial)
Status in g
** Description changed:
When testing MAAS on Bionic, we noticed sluggish performance that we
could not immediately explain.
After comparing the results from a run of the test suite on Xenial to a
run on Bionic, we determined that the slowdowns had to do with DNS
lookups. In particular
I just tested with the Xenial kernel and Bionic userspace and observed
that the bug still occurs, so marked Invalid for 'linux'.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
One way to tell if this bug is due to the kernel, is to boot with some
prior kernel versions and see if the bug goes away.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Package
Note: I doubt this bug is in the kernel itself; I initially attempted to
file it under glibc at first, but for some reason the `linux` package
was selected.
I also added `systemd` in case the difference in behavior can be
explained by the addition of resolved.
Note that these tests were run on Bi
31 matches
Mail list logo