Bug 952193
Summary: | avahi-daemon takes 100% CPU right after boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rick Richardson <rickrich> |
Component: | avahi | Assignee: | Lennart Poettering <lpoetter> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | dkelson, j, lpoetter, mjc, pb, rdieter, stefw, twaugh |
Target Milestone: | --- | Keywords: | Patch, Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | avahi-0.6.31-32.fc22 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-29 01:50:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rick Richardson
2013-04-15 11:11:27 UTC
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. I observed this problem on F19. avahi-daemon went to 100%, causing avahi-browse to fail and cups-1.6 printers not to be shared. [root@ulmo ~]# avahi-browse -a Failed to create client object: Daemon not running even though: [root@ulmo ~]# systemctl status avahi-daemon.service avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled) Active: active (running) since Thu 2013-07-18 18:24:11 EDT; 17h ago Kill the process manually and then restarting avahi-daemon.service, and then cups.service, restored my print server to normal operation. Does avahi-0.6.31-11.fc19.x86_64 have the patch mentioned in https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1059286? Bumping version from F17 to F19. after upgrade from Fedora 18 to 19 this bug hits me also. Any hints/recommendations for debugging available? Also it looks like that xsane is broken to my HP Print/Scan system, which is configured via Zeroconf...can this be caused by running mad avahi-daemon? after kill -9 to both avahi processes and restart avahi service with # service avahi-daemon start everything works fine (even xsane and the HP Print/Scan system)...looks like somehting during bootup cause a deadlock or something similar After a reboot, CPU #1 was at 100% usage on a quad core machine. All wireless nodes would not work. Scratched my head and did "killall avahi-daemon". Whammo, all wireless nodes worked again. So I did a "systemctl disable avahi-daemon". Fool me once, shame on you; fool me twice, shame on me. (In reply to Michael J. Chudobiak from comment #2) > Does avahi-0.6.31-11.fc19.x86_64 have the patch mentioned in > https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1059286? $ pwd /home/rick/tmp/avahi-master $ ll total 52 -rw-rw-r--. 1 rick rick 5168 Aug 26 08:32 avahi-0.6.30-mono-libdir.patch -rw-rw-r--. 1 rick rick 37970 Aug 26 08:32 avahi.spec -rw-rw-r--. 1 rick rick 54 Aug 26 08:32 sources It does not! But Ubuntu (2012-10-09) and SUSE (2012-09-09) have it. This is effecting RHEL7 public beta (and current snapshot). Fix here: http://lists.freedesktop.org/archives/avahi/2012-September/002188.html This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. I'm reopening this, because I ran into it today on F22 and the patch from comment 7 appears to fix my problem completely. Is there any particular problem with the patch? I found that SuSE has been carrying that patch since at least 2013, and it appears to solve my problem so I'm just going to go ahead and push it. avahi-0.6.31-32.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/avahi-0.6.31-32.fc22 How about Fedora 21??? I haven't seen this problem on F21 (ran an F21 print server in the same environment with no issues) and have no way of testing it there any longer. The F21 package is identical to the F22 package, though, so I'll merge it back and do a build for you. I won't push it without karma, though. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 avahi-0.6.31-32.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/avahi-0.6.31-32.fc21 Package avahi-0.6.31-32.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing avahi-0.6.31-32.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11670/avahi-0.6.31-32.fc21 then log in and leave karma (feedback). avahi-0.6.31-32.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. avahi-0.6.31-32.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |