Description of problem: Every some minutes (varies from 1 to 60) avahi-daemon logs this output: Registering new address record for [ipv6addr] on enp2s0.*. and about 5 seconds later Withdrawing address record for [ipv6addr] on enp2s0. Where [ipv6addr] is my ipv6 addr and enp2s0 is my ethernet connection's name. Version-Release number of selected component (if applicable): avahi 0.6.31-30.fc22 How reproducible: This is happening for weeks.
This is still a problem with avahi-0.6.31-43.fc23.x86_64 and IPv6 addresses. For inexplicable reasons, it'll just start going nuts withdrawing and registering the same address over and over again every couple of seconds, totally filling up the journal or log file (fully 80% of the space is full of these messages).
Created attachment 1117826 [details] journalctl -b -o short-monotonic -l
Log starts at Jan 23 13:16:18, and it's fine for about 24 hours, and then suddenly constant: Jan 24 13:06:44 f23s.localdomain avahi-daemon[740]: Registering new address record for 2601:282:702:b65c:d4a7:16d9:b02a:f775 on enp3s0.*. Jan 24 13:06:46 f23s.localdomain avahi-daemon[740]: Withdrawing address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0. Jan 24 13:06:47 f23s.localdomain avahi-daemon[740]: Registering new address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0.*. Jan 24 13:06:47 f23s.localdomain avahi-daemon[740]: Withdrawing address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0. repeats until the service is stopped. My only guess is maybe that this coincides with the 2nd IPv6 address expiring, as it's a temporary (RFC 4941) address, and avahi just isn't expecting it to be yanked away from it...so it flips out. 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:ae:ed:77:ea:51 brd ff:ff:ff:ff:ff:ff inet 10.0.0.15/24 brd 10.0.0.255 scope global dynamic enp3s0 valid_lft 481503sec preferred_lft 481503sec inet6 2601:282:702:b65c:d4a7:16d9:b02a:f775/64 scope global temporary dynamic valid_lft 48389sec preferred_lft 48300sec inet6 2601:282:702:b65c:6467:7c36:316d:1486/64 scope global temporary deprecated dynamic valid_lft 48389sec preferred_lft 0sec inet6 2601:282:702:b65c:baae:edff:fe77:ea51/64 scope global mngtmpaddr noprefixroute dynamic valid_lft 48389sec preferred_lft 48389sec inet6 fe80::baae:edff:fe77:ea51/64 scope link valid_lft forever preferred_lft forever The :316d:1486 address is "deprecated" and lft is 0sec. The current temporary public IP is :b02a:f775 Even after stopping it, and starting it again, it doesn't recover, it's immediately pissed: Jan 24 23:35:38 f23s.localdomain avahi-daemon[9339]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Jan 24 23:35:38 f23s.localdomain avahi-daemon[9339]: Registering new address record for 2601:282:702:b65c:baae:edff:fe77:ea51 on enp3s0.*. Jan 24 23:35:38 f23s.localdomain avahi-daemon[9339]: Registering new address record for 2601:282:702:b65c:d4a7:16d9:b02a:f775 on enp3s0.*. Jan 24 23:35:38 f23s.localdomain avahi-daemon[9339]: Registering new address record for 10.0.0.15 on enp3s0.IPv4. Jan 24 23:35:38 f23s.localdomain polkitd[745]: Unregistered Authentication Agent for unix-process:9333:12356145 (system bus name :1.121, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Jan 24 23:35:39 f23s.localdomain avahi-daemon[9339]: Server startup complete. Host name is f23s.local. Local service cookie is 2805285060. Jan 24 23:35:40 f23s.localdomain avahi-daemon[9339]: Registering new address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0.*. Jan 24 23:35:40 f23s.localdomain avahi-daemon[9339]: Withdrawing address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0. Jan 24 23:35:43 f23s.localdomain avahi-daemon[9339]: Registering new address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0.*. Jan 24 23:35:43 f23s.localdomain avahi-daemon[9339]: Withdrawing address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0. Jan 24 23:35:46 f23s.localdomain avahi-daemon[9339]: Registering new address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0.*. Jan 24 23:35:46 f23s.localdomain avahi-daemon[9339]: Withdrawing address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0. Jan 24 23:35:49 f23s.localdomain avahi-daemon[9339]: Registering new address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0.*. Jan 24 23:35:49 f23s.localdomain avahi-daemon[9339]: Withdrawing address record for 2601:282:702:b65c:6467:7c36:316d:1486 on enp3s0. It seems to be angry about the deprecated IPv6 address.
Hm, I'm not seeing this issue any more. I only see the message once or twice per boot, mostly after suspend and resume. Are you running F23?
It's a problem on two different baremetal systems, one is running Fedora 23 Server, the other is running Fedora 23 Workstations. The problem is the same on both. The IPv6 address Avahi is complaining about is the deprecated one.
(In reply to Christian Stadelmann from comment #4) > Hm, I'm not seeing this issue any more. I only see the message once or twice > per boot, mostly after suspend and resume. Are you running F23? Probably the reason you're not seeing this on Fedora 23 is due to bug 1279242. By default Fedora 23 doesn't enable privacy extensions, therefore you never get a deprecated IPv6 (and you're also leaking your MAC address publicly). This can't be changed with NetworkManager, it doesn't support it yet. So: nmcli c nmcli c modify <nameofinterface> ipv6.ip6-privacy 2
Koji lists avahi-0.6.32-0.4.rc.fc23 rdieter 2015-11-19 19:10:50 Why isn't this in updates or updates-testing for two months? Anyway, this bug still applies to that version. Every second I'm getting journal messages. Jan 25 10:50:47 f23m.localdomain avahi-daemon[15925]: Registering new address record for 2601:282:702:b65c:3c32:c570:6607:a8c on enp2s0f0.*. Jan 25 10:50:47 f23m.localdomain avahi-daemon[15925]: Withdrawing address record for 2601:282:702:b65c:3c32:c570:6607:a8c on enp2s0f0. ... ...
Still present in Fedora 25. Any chance to get this 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.
I'm not 100% sure but I think I don't see this bug on Fedora 26 and 27 any more.
Anyway, upstream is still not fixed, so please change the version info.
It still happens for me on Fedora 27, but it is no where near as frequent or consistent even. $ journalctl | grep -i withdraw Nov 11 20:31:05 f27s.localdomain avahi-daemon[730]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 11 20:38:01 f27s.localdomain avahi-daemon[706]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 11 21:04:38 f27s.localdomain avahi-daemon[716]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 15 14:34:01 f27s.localdomain avahi-daemon[636]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 15 14:57:51 f27s.localdomain avahi-daemon[655]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 15 20:37:56 f27s.localdomain avahi-daemon[795]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 16 14:18:57 f27s.localdomain avahi-daemon[824]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. Nov 16 16:05:38 f27s.localdomain avahi-daemon[791]: Withdrawing address record for fe80::91f1:7594:6bae:99ea on enp3s0. [chris@f27s ~]$ It's not even happening every day, which is kinda weird.
Ahh I know why it doesn't happen as often. For whatever reason, I've got the same IPv6 address assigned for much longer periods of time than previous versions of Fedora and I think it has to do with changes related to IPv6 privacy. ipv6.ip6-privacy: -1 (unknown) I'm not sure the address rotation frequency is happening correctly anymore; previously this was getting switched out quite often, and that's what was causing the avahi messages.
Haha, I reference this bug in comment 6. Time flies. https://bugzilla.redhat.com/show_bug.cgi?id=1279242#c8 This article has a good IPv6 section explaining the current state of things. https://fedoramagazine.org/networkmanager-changes-improvements/
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.