[Bug 1799265] Re: avahi-daemon high cpu, unusable networking

Philkav1989 philkav1989 at gmail.com
Wed Sep 25 12:37:59 UTC 2019 

Hi, I'm hitting this quite consistently on Pop!_OS 19.04 in Virtualbox
(Windows 10 host) on Lenovo T460.

Essentially, the CPU usage goes up to 100% for avahi-daemon, and the
strace shows it stuck in a loop, reading/writing to a named pipe, like
so:

poll([{fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8, events=POLLIN}], 8, 0) = 3 ([{fd=14, revents=POLLIN|POLLERR}, {fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)                        = 1
write(7, "W", 1)                        = 1
read(6, "WW", 10)                       = 2
poll([{fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8, events=POLLIN}], 8, 0) = 3 ([{fd=14, revents=POLLIN|POLLERR}, {fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)                        = 1
write(7, "W", 1)                        = 1
write(7, "W", 1)                        = 1
write(7, "W", 1)                        = 1
read(6, "WWWW", 10)                     = 4
poll([{fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8, events=POLLIN}], 8, 0) = 3 ([{fd=14, revents=POLLIN|POLLERR}, {fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
^Cstrace: Process 782 detached


root at pop-os:/# ls -ltr /proc/782/fd
total 0
lrwx------ 1 root root 64 Sep 25 13:03 14 -> 'socket:[20288]'
lrwx------ 1 root root 64 Sep 25 13:03 13 -> 'socket:[20287]'
lrwx------ 1 root root 64 Sep 25 13:03 12 -> 'socket:[20286]'
lr-x------ 1 root root 64 Sep 25 13:03 11 -> anon_inode:inotify
lrwx------ 1 root root 64 Sep 25 13:03 10 -> 'socket:[20154]'
l-wx------ 1 root root 64 Sep 25 13:03 9 -> 'pipe:[20153]'
lr-x------ 1 root root 64 Sep 25 13:03 8 -> 'pipe:[20153]'
l-wx------ 1 root root 64 Sep 25 13:03 7 -> 'pipe:[20152]'
lr-x------ 1 root root 64 Sep 25 13:03 6 -> 'pipe:[20152]'
lrwx------ 1 root root 64 Sep 25 13:03 5 -> 'socket:[20141]'
lrwx------ 1 root root 64 Sep 25 13:03 4 -> 'socket:[19687]'
lrwx------ 1 root root 64 Sep 25 13:03 3 -> 'socket:[17872]'
lrwx------ 1 root root 64 Sep 25 13:03 2 -> 'socket:[19192]'
lrwx------ 1 root root 64 Sep 25 13:03 1 -> 'socket:[19192]'
lr-x------ 1 root root 64 Sep 25 13:03 0 -> /dev/null
root at pop-os:/# 


My avahi config is:

    ## /etc/avah/avahi-daemon.conf
    [server]
    use-ipv4=yes
    use-ipv6=no

    ratelimit-interval-usec=1000000
    ratelimit-burst=1000

    [wide-area]
    enable-wide-area=yes

    [publish]
    publish-hinfo=no
    publish-workstation=no

    [reflector]
    [rlimits]


The journal log is overgrown with messages like so: (I've replaced parts of the ipv6 addresses with XXXX)
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:485e:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:28d5:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:61:28d5:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:fca2:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:61:fca2:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:90ab:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:61:90ab:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:61:5855:XXXX:XXXX:XXXX9 on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:5855:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:94aa:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:61:94aa:XXXX:XXXX:XXXX on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for 2606:b400:818:64:e973:XXXX:XXXX:XXXX on enp0s8.*.


I've managed to gather the 'perf' data, that was requested by lathiat.

Let me know if this info is of use.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1799265

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  New
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   LD_PRELOAD=<set>
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/1799265/+subscriptions

More information about the foundations-bugs mailing list