Same symptoms, same result on a headless always-on box running 16.04.
Made worse by the fact that I have to hard-power off the box and hook it
up to monitor for troubleshooting. Every couple weeks the machine will
lose connection to the network.
Last time I thought I lost the on-board NIC and went and
bought/installed a new NIC card (another Realtek). Two weeks later,
same result: syslog shows this:
May 24 22:40:14 phaedrus avahi-daemon[857]: Withdrawing address record for
192.168.0.201 on enp4s1.
May 24 22:40:14 phaedrus avahi-daemon[857]: Leaving mDNS multicast group on
interface enp4s1.IPv4 with address 192.168.0.201.
May 24 22:40:14 phaedrus avahi-daemon[857]: Interface enp4s1.IPv4 no longer
relevant for mDNS.
## System:
Host: phaedrus Kernel: 4.4.0-78-generic x86_64 (64 bit) Console: tty 9 Distro:
Ubuntu 16.04 xenial
## Network: (from `inxi -F`)
Card-1: Device 000c:d051
IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
Card-2: Realtek RTL8169 PCI Gigabit Ethernet Controller driver: r8169
IF: enp4s1 state: up speed: 1000 Mbps duplex: full mac: 00:0a:cd:2c:93:5f
Looks like it might be Realtek 8168/9 related?
--
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
