Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#922630: avahi-daemon high cpu usage
120 views
Skip to first unread message
David Miguel Susano Pinto
Feb 18, 2019, 11:20:03 AM2/18/19
to
Package: avahi-daemon
Version: 0.7-4+b1
Severity: normal
Dear Maintainer,
avahi-dameon shows a very high cpu usage and I found no useful
messages on the logs. Restarting the daemon does nothing. When I ran
the daemon with '--debug' option, I see hundreds of lines like this on
syslog:
Received response from host 10.31.19.92 with invalid source port 63227
Received response from host 10.31.20.38 with invalid source port 57554
Received response from host 10.31.40.164 with invalid source port 58307
Received response from host 10.31.44.4 with invalid source port 54151
It's always those four IP addresses and those four ports. There's
many other entries but those are the ones that look the most like an
error.
This issue only happens at a specific network (eduroam wifi network at
my university). There are no problems on many other networks so I
think there may be something odd with this specific university.
However, I also think that avahi should be a bit more resilient. Even
if there is an issue on the network, it should not bring a laptop to a
halt. avahi-daemon goes at 100% CPU usage nonstop. The only reason I
can do any work at all is that this is a quite beffy quadcore laptop.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages avahi-daemon depends on:
ii adduser 3.118
ii bind9-host [host] 1:9.11.5.P1+dfsg-1
ii dbus 1.12.12-1
ii libavahi-common3 0.7-4+b1
ii libavahi-core7 0.7-4+b1
ii libc6 2.28-6
ii libcap2 1:2.25-2
ii libdaemon0 0.14-7
ii libdbus-1-3 1.12.12-1
ii libexpat1 2.2.6-1
ii lsb-base 10.2018112800
Versions of packages avahi-daemon recommends:
ii libnss-mdns 0.14.1-1
Versions of packages avahi-daemon suggests:
ii avahi-autoipd 0.7-4+b1
-- no debconf information
Version: 0.7-4+b1
Severity: normal
Dear Maintainer,
avahi-dameon shows a very high cpu usage and I found no useful
messages on the logs. Restarting the daemon does nothing. When I ran
the daemon with '--debug' option, I see hundreds of lines like this on
syslog:
Received response from host 10.31.19.92 with invalid source port 63227
Received response from host 10.31.20.38 with invalid source port 57554
Received response from host 10.31.40.164 with invalid source port 58307
Received response from host 10.31.44.4 with invalid source port 54151
It's always those four IP addresses and those four ports. There's
many other entries but those are the ones that look the most like an
error.
This issue only happens at a specific network (eduroam wifi network at
my university). There are no problems on many other networks so I
think there may be something odd with this specific university.
However, I also think that avahi should be a bit more resilient. Even
if there is an issue on the network, it should not bring a laptop to a
halt. avahi-daemon goes at 100% CPU usage nonstop. The only reason I
can do any work at all is that this is a quite beffy quadcore laptop.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages avahi-daemon depends on:
ii adduser 3.118
ii bind9-host [host] 1:9.11.5.P1+dfsg-1
ii dbus 1.12.12-1
ii libavahi-common3 0.7-4+b1
ii libavahi-core7 0.7-4+b1
ii libc6 2.28-6
ii libcap2 1:2.25-2
ii libdaemon0 0.14-7
ii libdbus-1-3 1.12.12-1
ii libexpat1 2.2.6-1
ii lsb-base 10.2018112800
Versions of packages avahi-daemon recommends:
ii libnss-mdns 0.14.1-1
Versions of packages avahi-daemon suggests:
ii avahi-autoipd 0.7-4+b1
-- no debconf information
Peter Berntsen
May 28, 2019, 11:10:02 PM5/28/19
to
Followup-For: Bug #922630
Package: avahi-daemon
Version: 0.7-4+b1
Dear Maintainer,
* What led up to the situation?
eduroam WIFI connected to the internet at a university.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing.
* What was the outcome of this action?
Slow computer, fan running on and off at full speed.
* What outcome did you expect instead?
That the avahi-daemon wasn't acting like a magnet to all my CPU.
-- System Information:
Debian Release: 10.0
Package: avahi-daemon
Version: 0.7-4+b1
Dear Maintainer,
* What led up to the situation?
eduroam WIFI connected to the internet at a university.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing.
* What was the outcome of this action?
Slow computer, fan running on and off at full speed.
* What outcome did you expect instead?
That the avahi-daemon wasn't acting like a magnet to all my CPU.
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages avahi-daemon depends on:
ii adduser 3.118
ii adduser 3.118
ii bind9-host [host] 1:9.11.5.P4+dfsg-5
ii dbus 1.12.12-1
ii libavahi-common3 0.7-4+b1
ii libavahi-core7 0.7-4+b1
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libdaemon0 0.14-7
ii libdbus-1-3 1.12.12-1
ii libexpat1 2.2.6-1
ii lsb-base 10.2019051400
Peter Berntsen
May 28, 2019, 11:20:02 PM5/28/19
to
Package: avahi-daemon
Version: 0.7-4+b1
Followup-For: Bug #922630
Dear Maintainer,
* What led up to the situation?
eduroam WIFI connected to the internet at a university.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing.
* What was the outcome of this action?
Slow computer, fan running on and off at full speed.
* What outcome did you expect instead?
That the avahi-daemon wasn't acting like a magnet to all my CPU.
-- System Information:
Debian Release: 10.0
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Version: 0.7-4+b1
Followup-For: Bug #922630
Dear Maintainer,
* What led up to the situation?
eduroam WIFI connected to the internet at a university.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing.
* What was the outcome of this action?
Slow computer, fan running on and off at full speed.
* What outcome did you expect instead?
That the avahi-daemon wasn't acting like a magnet to all my CPU.
Debian Release: 10.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages avahi-daemon depends on:
ii adduser 3.118
ii bind9-host [host] 1:9.11.5.P4+dfsg-5
LSM: AppArmor: enabled
Versions of packages avahi-daemon depends on:
ii adduser 3.118
ii dbus 1.12.12-1
ii libavahi-common3 0.7-4+b1
ii libavahi-core7 0.7-4+b1
ii libc6 2.28-10
ii libavahi-common3 0.7-4+b1
ii libavahi-core7 0.7-4+b1
ii libcap2 1:2.25-2
ii libdaemon0 0.14-7
ii libdbus-1-3 1.12.12-1
ii libexpat1 2.2.6-1
ii lsb-base 10.2019051400
ii libdaemon0 0.14-7
ii libdbus-1-3 1.12.12-1
ii libexpat1 2.2.6-1
Vincent Lefevre
Mar 3, 2022, 10:20:03 AM3/3/22
to
Control: found -1 0.8-5
On 2019-02-18 16:10:35 +0000, David Miguel Susano Pinto wrote:
> avahi-dameon shows a very high cpu usage and I found no useful
> messages on the logs.
Same issue. The htop utility shows:
PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command
634 avahi 20 0 36172 31724 3936 R 99.9 0.1 32h20:44 avahi-daemon: running [cventin.local]
> This issue only happens at a specific network (eduroam wifi network at
> my university).
Here this is at my lab, for a machine connected via an Ethernet cable.
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
On 2019-02-18 16:10:35 +0000, David Miguel Susano Pinto wrote:
> avahi-dameon shows a very high cpu usage and I found no useful
> messages on the logs.
PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command
634 avahi 20 0 36172 31724 3936 R 99.9 0.1 32h20:44 avahi-daemon: running [cventin.local]
> This issue only happens at a specific network (eduroam wifi network at
> my university).
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Vincent Lefevre
Mar 3, 2022, 10:40:03 AM3/3/22
to
On 2022-03-03 16:12:57 +0100, Vincent Lefevre wrote:
> On 2019-02-18 16:10:35 +0000, David Miguel Susano Pinto wrote:
> > avahi-dameon shows a very high cpu usage and I found no useful
> > messages on the logs.
>
> Same issue. The htop utility shows:
>
> PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command
> 634 avahi 20 0 36172 31724 3936 R 99.9 0.1 32h20:44 avahi-daemon: running [cventin.local]
>
> > This issue only happens at a specific network (eduroam wifi network at
> > my university).
>
> Here this is at my lab, for a machine connected via an Ethernet cable.
I've looked at the atop logs since the machine got rebooted.
> On 2019-02-18 16:10:35 +0000, David Miguel Susano Pinto wrote:
> > avahi-dameon shows a very high cpu usage and I found no useful
> > messages on the logs.
>
> Same issue. The htop utility shows:
>
> PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command
> 634 avahi 20 0 36172 31724 3936 R 99.9 0.1 32h20:44 avahi-daemon: running [cventin.local]
>
> > This issue only happens at a specific network (eduroam wifi network at
> > my university).
>
> Here this is at my lab, for a machine connected via an Ethernet cable.
The CPU usage actually increases during the first 24 hours
to reach about 100%:
00:30 1%
00:40 2%
01:00 3%
01:10 4%
01:20 5%
02:00 6%
03:00 8%
04:00 11%
05:00 9%
06:00 11%
07:00 12%
08:00 14%
09:00 10%
10:00 10%
11:00 12%
12:00 16%
13:00 17%
14:00 18%
15:00 20%
16:00 21%
17:00 24%
18:00 29%
19:00 38%
20:00 42%
21:00 49%
21:30 59%
22:00 68%
22:30 86%
23:00 93%
24:00 96%
So bug 922630 looks like the same bug as bug 993051.
Mathieu ROY
Jun 5, 2022, 11:20:03 AM6/5/22
to
Hi there,
On at least 3 different computer I hit this bug.
Do anyone made a patched .deb or is there any notion that there could be
an updated package anytime soon?
(or any alternative software suggest)
Regards,
On at least 3 different computer I hit this bug.
Do anyone made a patched .deb or is there any notion that there could be
an updated package anytime soon?
(or any alternative software suggest)
Regards,
Michael Biebl
Jun 5, 2022, 11:30:03 AM6/5/22
to
Am 05.06.22 um 17:10 schrieb Mathieu ROY:
> Hi there,
>
> On at least 3 different computer I hit this bug.
>
> Do anyone made a patched .deb or is there any notion that there could be
> an updated package anytime soon?
I don't see anyone having provided a patch for this issue.
>
> On at least 3 different computer I hit this bug.
>
> Do anyone made a patched .deb or is there any notion that there could be
> an updated package anytime soon?
My recommendation would be to file this issue upstream at
https://github.com/lathiat/avahi/issues
Upstream can probably help you with debugging this issue.
Once a fix/patch is available, we can cherry-pick that in the Debian
package.
Michael
Mathieu ROY
Jun 6, 2022, 6:00:04 AM6/6/22
to
Hi,
This bug is very likely the same as 993051 that you fixed yesterday.
Thanks!
Regards,
This bug is very likely the same as 993051 that you fixed yesterday.
Thanks!
Regards,
Vincent Lefevre
Jun 6, 2022, 8:00:04 AM6/6/22
to
On 2022-06-06 11:51:17 +0200, Mathieu ROY wrote:
> This bug is very likely the same as 993051 that you fixed yesterday.
I agree. With the absence of additional information (and a vague
> This bug is very likely the same as 993051 that you fixed yesterday.
bug title), these bugs should be regarded as being the same.
Before the upgrade to 0.8-6 (i.e. containing the 993051 bug fix),
I'm trying to reproduce the issue with 0.8-5[*], but I do not
notice it any longer. I suppose that on the network, there was a
machine that triggered the issue, but it is no longer there. So,
unfortunately, I can't say more on the issue I got at that time.
[*] Same machine, same network, same avahi-daemon version as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922630#20
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922630#27
0 new messages