Same here with 16.04.2 (4.8.0-58-generic x86_64, no VM) and Realtek8111 (PCI 10ec:8168 rev 06). Worked before with 12.04, now it's shutting down the interface every few days.
Regarding the Networkmanager restart: Not for me, the PID is still the same. Maybe the timing from the latest event may help: Jul 23 13:51:19 braindead5 dhclient[26468]: DHCPREQUEST of 192.168.0.5 on enp8s0 to 192.168.0.1 port 67 (xid=0x75dc0193) Jul 23 13:51:19 braindead5 dhclient[26468]: DHCPACK of 192.168.0.5 from 192.168.0.1 Jul 23 13:51:19 braindead5 dhclient[26468]: bound to 192.168.0.5 -- renewal in 17447 seconds. So the IP is valid for more than 4h. But about an hour later: Jul 23 14:57:51 braindead5 avahi-daemon[907]: Withdrawing address record for 192.168.0.5 on enp8s0. Jul 23 14:57:51 braindead5 avahi-daemon[907]: Leaving mDNS multicast group on interface enp8s0.IPv4 with address 192.168.0.5. Jul 23 14:57:51 braindead5 avahi-daemon[907]: Interface enp8s0.IPv4 no longer relevant for mDNS. Jul 23 14:57:51 braindead5 org.kde.kdeconnect[1675]: "No such interface 'org.freedesktop.DBus.Properties' on object at path /" Jul 23 14:57:56 braindead5 kernel: [1879701.611525] nfs: server 192.168.0.1 not responding, timed out The interface was shut down (no IP, only visible with ifconfig -a), but it had link state (green LED). There were no other messages regarding Networkmanager etc. at that time. It's hard to tell if the NFS problems are caused by the avahi-stuff or both share the same root cause. In my experience, NFS usually "finds" missing connectivity very fast, so it should complain before avahi... Also on all other occurences the avahi message was before NFS. I've now stopped the avahi-daemon. If it happens again, I will look if dhclient runs and if there are increasing RX packets and visible broadcast data from other hosts at the dead interface. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
