Hide Forgot
Description of problem: This happened before restarting Version-Release number of selected component (if applicable): avahi version 0.6.32 tried on 4.7.9-200.fc24.x86_64 kernel as well as before rebooting on 4.7.7-200.fc24.x86_64 kernel How reproducible: every time on reboot Additional info: Oct 24 15:38:31 ourdomain avahi-daemon[2832]: Out of memory, aborting ... Oct 24 15:38:31 ourdomain systemd[1]: avahi-daemon.service: Main process exited, code=killed, status=6/ABRT Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Process 2832 died: No such process; trying to remove PID file. (/var/run/avahi-daemon//pid) Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Found user 'avahi' (UID 497) and group 'avahi' (GID 497). Oct 24 15:38:31 ourdomain systemd[1]: avahi-daemon.service: Unit entered failed state. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Successfully dropped root privileges. Oct 24 15:38:31 ourdomain systemd[1]: avahi-daemon.service: Failed with result 'signal'. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: avahi-daemon 0.6.32 starting up. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Successfully called chroot(). Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Successfully dropped remaining capabilities. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Loading service file /services/udisks.service. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::21e:c9ff:feab:7ef0. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: New relevant interface eth0.IPv6 for mDNS. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Joining mDNS multicast group on interface eth0.IPv4 with address 150.108.64.52. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: New relevant interface eth0.IPv4 for mDNS. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Network interface enumeration completed. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Registering new address record for fe80::21e:c9ff:feab:7ef0 on eth0.*. Oct 24 15:38:31 ourdomain avahi-daemon[2865]: Registering new address record for ip on eth0.IPv4. Oct 24 15:38:32 ourdomain avahi-daemon[2865]: Server startup complete. Host name is ourdomain.local. Local service cookie is 3216231522. Oct 24 15:38:33 ourdomain avahi-daemon[2865]: ourdomain (/services/udisks.service) successfully established. Here is a snip of top: top - 15:51:15 up 18 min, 1 user, load average: 1.24, 1.08, 0.88 Tasks: 249 total, 2 running, 247 sleeping, 0 stopped, 0 zombie %Cpu(s): 4.0 us, 8.6 sy, 0.0 ni, 86.6 id, 0.9 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 8170440 total, 6168936 free, 690580 used, 1310924 buff/cache KiB Swap: 8191996 total, 8191996 free, 0 used. 7194552 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2865 avahi 20 0 58072 7948 3836 R 100.0 0.1 12:42.18 avahi-daemon 3685 root 20 0 48612 3952 3216 R 0.7 0.0 0:00.02 top Lots of httpd processes: systemctl status dbus * dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled) Active: active (running) since Mon 2016-10-24 15:33:25 EDT; 20min ago Docs: man:dbus-daemon(1) Main PID: 1379 (dbus-daemon) Tasks: 1 (limit: 512) CGroup: /system.slice/dbus.service `-1379 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only Oct 24 15:37:06 ourdomain dbus-daemon[1379]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.37' (uid=48 pid=1952 comm="/usr/sbin/httpd -DFOREGROUND ") Oct 24 15:37:06 ourdomain dbus-daemon[1379]: [system] Successfully activated service 'org.freedesktop.Avahi' Oct 24 15:37:38 ourdomain dbus-daemon[1379]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.40' (uid=48 pid=2647 comm="/usr/sbin/httpd -DFOREGROUND ") Oct 24 15:37:38 ourdomain dbus-daemon[1379]: [system] Successfully activated service 'org.freedesktop.Avahi' Oct 24 15:37:54 ourdomain dbus-daemon[1379]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.42' (uid=48 pid=2647 comm="/usr/sbin/httpd -DFOREGROUND ") Oct 24 15:37:54 ourdomain dbus-daemon[1379]: [system] Successfully activated service 'org.freedesktop.Avahi' Oct 24 15:38:14 ourdomain dbus-daemon[1379]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.44' (uid=48 pid=2647 comm="/usr/sbin/httpd -DFOREGROUND ") Oct 24 15:38:14 ourdomain dbus-daemon[1379]: [system] Successfully activated service 'org.freedesktop.Avahi' Oct 24 15:38:31 ourdomain dbus-daemon[1379]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.46' (uid=48 pid=2647 comm="/usr/sbin/httpd -DFOREGROUND ") Oct 24 15:38:31 ourdomain dbus-daemon[1379]: [system] Successfully activated service 'org.freedesktop.Avahi' systemctl status systemd-logind.service * systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled) Active: active (running) since Mon 2016-10-24 15:33:27 EDT; 36min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 1421 (systemd-logind) Status: "Processing requests..." Tasks: 1 (limit: 512) CGroup: /system.slice/systemd-logind.service `-1421 /usr/lib/systemd/systemd-logind Oct 24 16:07:41 ourdomain systemd-logind[1421]: New session 25 of user root. Oct 24 16:07:41 ourdomain systemd-logind[1421]: Removed session 25. Oct 24 16:07:41 ourdomain systemd-logind[1421]: New session 26 of user root. Oct 24 16:09:00 ourdomain systemd-logind[1421]: Removed session 26. Oct 24 16:09:00 ourdomain systemd-logind[1421]: New session 27 of user root. Oct 24 16:09:04 ourdomain systemd-logind[1421]: Removed session 27. Oct 24 16:09:04 ourdomain systemd-logind[1421]: New session 28 of user root. Oct 24 16:09:07 ourdomain systemd-logind[1421]: Removed session 28. Oct 24 16:09:07 ourdomain systemd-logind[1421]: New session 29 of user root. Oct 24 16:09:07 ourdomain systemd-logind[1421]: Removed session 29. NIS errors: Oct 24 15:46:33 ourdomain ypserv[1601]: refused connect from 150.108.64.52:57768 to procedure ypproc_match (ourdomain,shadow.byname;-1) Oct 24 15:46:34 ourdomain ypserv[1601]: refused connect from 150.108.64.52:41431 to procedure ypproc_match (ourdomain,shadow.byname;-1) Oct 24 15:46:36 ourdomain ypserv[1601]: refused connect from 150.108.64.52:44496 to procedure ypproc_match (ourdomain,shadow.byname;-1) Oct 24 15:46:36 ourdomain ypserv[1601]: refused connect from 150.108.64.52:40068 to procedure ypproc_match (ourdomain,shadow.byname;-1) Oct 24 15:46:38 ourdomain ypserv[1601]: refused connect from 150.108.64.52:54735 to procedure ypproc_match (ourdomain,shadow.byname;-1) Oct 24 15:46:39 ourdomain ypserv[1601]: refused connect from 150.108.64.52:49616 to procedure ypproc_match (ourdomain,shadow.byname;-1)
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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 25 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.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.