You are not logged in.

#1 2025-09-06 20:13:01

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

[SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

Hi,

Apparently, since 22th of July something broke in my network configuration on two different Arch Linux machines simultaneously.

It doesn't affect that much use, but for example PulseAudio module module-zeroconf-discover stopped working (the audio device can be found on another computer for a split second but disappears). I started to investigate why I can not playback audio over the network with this handy albeit hacky way, and discovered constant spam (as in every minute) of the following kind on both of these computers (I should also probably check my laptop if it has similar problems).

Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: New relevant interface lo.IPv6 for mDNS.
Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: New relevant interface lo.IPv4 for mDNS.
Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: Network interface enumeration completed.
Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: Registering new address record for ::1 on lo.*.
Sep 06 22:37:30 ArkkiVille avahi-daemon[1379]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 06 22:37:31 ArkkiVille avahi-daemon[1379]: Server startup complete. Host name is ArkkiVille.local. Local service cookie is 1763859219.
Sep 06 22:37:33 ArkkiVille avahi-daemon[1379]: Joining mDNS multicast group on interface enp42s0.IPv6 with address fe80::76d9:8b36:b641:793.
Sep 06 22:37:33 ArkkiVille avahi-daemon[1379]: New relevant interface enp42s0.IPv6 for mDNS.
Sep 06 22:37:33 ArkkiVille avahi-daemon[1379]: Registering new address record for fe80::76d9:8b36:b641:793 on enp42s0.*.
Sep 06 22:37:34 ArkkiVille avahi-daemon[1379]: Joining mDNS multicast group on interface enp42s0.IPv4 with address 192.168.66.3.
Sep 06 22:37:34 ArkkiVille avahi-daemon[1379]: New relevant interface enp42s0.IPv4 for mDNS.
Sep 06 22:37:34 ArkkiVille avahi-daemon[1379]: Registering new address record for 192.168.66.3 on enp42s0.IPv4.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Leaving mDNS multicast group on interface enp42s0.IPv6 with address fe80::76d9:8b36:b641:793.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Joining mDNS multicast group on interface enp42s0.IPv6 with address fdd7:991d:5b85:0:edca:6a0d:df2f:1cfa.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for fdd7:991d:5b85:0:edca:6a0d:df2f:1cfa on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for fe80::76d9:8b36:b641:793 on enp42s0.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for 2001:14ba:a885:7700:2ef0:e45f:a24a:dad7 on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for 2001:14ba:a885:7700::bad:face on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for fdd7:991d:5b85::bad:face on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 2001:14ba:a885:7700::bad:face on enp42s0.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 2001:14ba:a885:7700:2ef0:e45f:a24a:dad7 on enp42s0.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for fdd7:991d:5b85:0:edca:6a0d:df2f:1cfa on enp42s0.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 192.168.66.3 on enp42s0.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for ::1 on lo.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 127.0.0.1 on lo.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Host name conflict, retrying with ArkkiVille-2
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for fdd7:991d:5b85::bad:face on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for 2001:14ba:a885:7700::bad:face on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for 2001:14ba:a885:7700:2ef0:e45f:a24a:dad7 on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for fdd7:991d:5b85:0:edca:6a0d:df2f:1cfa on enp42s0.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for 192.168.66.3 on enp42s0.IPv4.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for ::1 on lo.*.
Sep 06 22:37:35 ArkkiVille avahi-daemon[1379]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Server startup complete. Host name is ArkkiVille-2.local. Local service cookie is 1763859219.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Withdrawing address record for fdd7:991d:5b85::bad:face on enp42s0.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 2001:14ba:a885:7700::bad:face on enp42s0.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 2001:14ba:a885:7700:2ef0:e45f:a24a:dad7 on enp42s0.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 192.168.66.3 on enp42s0.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Withdrawing address record for ::1 on lo.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 127.0.0.1 on lo.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Host name conflict, retrying with ArkkiVille-3
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for fdd7:991d:5b85::bad:face on enp42s0.*.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for 2001:14ba:a885:7700::bad:face on enp42s0.*.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for 2001:14ba:a885:7700:2ef0:e45f:a24a:dad7 on enp42s0.*.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for fdd7:991d:5b85:0:edca:6a0d:df2f:1cfa on enp42s0.*.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for 192.168.66.3 on enp42s0.IPv4.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for ::1 on lo.*.
Sep 06 22:37:37 ArkkiVille avahi-daemon[1379]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Server startup complete. Host name is ArkkiVille-3.local. Local service cookie is 1763859219.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Withdrawing address record for fdd7:991d:5b85::bad:face on enp42s0.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 2001:14ba:a885:7700::bad:face on enp42s0.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 2001:14ba:a885:7700:2ef0:e45f:a24a:dad7 on enp42s0.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 192.168.66.3 on enp42s0.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Withdrawing address record for ::1 on lo.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Withdrawing address record for 127.0.0.1 on lo.
Sep 06 22:37:38 ArkkiVille avahi-daemon[1379]: Host name conflict, retrying with ArkkiVille-4

(and this goes on for thousands if not tens of thousands of lines...)

This may be related to having in /etc/avahi/avahi-daemon.conf:

[publish]
disable-publishing=true

However I've had that set to true for ages and things have worked without spam - and the PulseAudio module working without problems.

Now I'm trying to investigate this, scouring the internets and documentation,  but I'd appreciate if anyone has some pointers on where to go on from here. I don't understand the internals of avahi-daemon that well.

EDIT: Also, this has appeared in the logs around the same time (and didn't before July):

Sep 05 12:37:02 ArkkiVille avahi-daemon[1362]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Sep 05 12:37:02 ArkkiVille avahi-daemon[1362]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

But AFAIK I have not touched mDNS on my computer.

I should probably add I'm using NetworkManager on all my computers at this time. Both use DHCP to get addresses, and my router has been set up to give static addresses. Both are on wired connections.

\EDIT

Cheers!

Last edited by Wild Penguin (2025-09-07 14:33:09)

Offline

#2 2025-09-06 20:34:29

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,056

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

https://wiki.archlinux.org/title/Avahi - first blue note.
But the first journal excerpt looks more related to network fluctuations, possibly because of https://bbs.archlinux.org/viewtopic.php?id=307847 / https://bbs.archlinux.org/viewtopic.php?id=307808 which should™ be fixed w/ 6.16.5

Offline

#3 2025-09-06 21:15:53

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

Thanks seth for your reply,

I downgraded to 6.15.1 because of this issue: https://bbs.archlinux.org/viewtopic.php?id=307778  - however I see it should be fixed in 6.15.5.

But I've also just noticed I didn't have nss-mdns installed. Things have worked for, whatever reason fine on my end without it, also local name resolving. Installing it, the PulseAudio over network works again! I've also commented out the disable-publishing line from avahi.com (as it  used to be before I started troubleshooting this).

Systemd-resolved is disabled but for whatever reason still running!:

$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled)
     Active: active (running) since Sat 2025-09-06 23:20:32 EEST; 51min ago
 Invocation: 16b979fd19594f78b1fe0a3466313156
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS
   Main PID: 1270 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 10240)
     Memory: 5.4M (peak: 6.7M)
        CPU: 256ms
     CGroup: /system.slice/systemd-resolved.service
             └─1270 /usr/lib/systemd/systemd-resolved

syys 06 23:20:32 ArkkiVille systemd[1]: Starting Network Name Resolution...
syys 06 23:20:32 ArkkiVille systemd-resolved[1270]: Positive Trust Anchors:
syys 06 23:20:32 ArkkiVille systemd-resolved[1270]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
syys 06 23:20:32 ArkkiVille systemd-resolved[1270]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16
syys 06 23:20:32 ArkkiVille systemd-resolved[1270]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in->
syys 06 23:20:32 ArkkiVille systemd-resolved[1270]: Using system hostname 'ArkkiVille'.
syys 06 23:20:32 ArkkiVille systemd[1]: Started Network Name Resolution.
syys 06 23:20:50 ArkkiVille systemd-resolved[1270]: enp42s0: Bus client set search domain list to: lan
syys 06 23:20:50 ArkkiVille systemd-resolved[1270]: enp42s0: Bus client set default route setting: yes
syys 06 23:20:50 ArkkiVille systemd-resolved[1270]: enp42s0: Bus client set DNS server list to: 192.168.66.6

I'll investigate what's going on with systemd-resolved, any idea who might be pulling it up? Perhaps something took it up since I was missing nss-mdns?

Network stuff is ... annoying! I just set up stuff once and then forget everything XD

Offline

#4 2025-09-06 21:25:45

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,056

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

nss-mdns is only relevant for the domain.local resolution, not avahi for service detection, but the latter might have been provided by the colliding resolved service.
Are you sure you've been using avahi instead of resolved at all?

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

And I think NM will run resolved if resolv.conf is a resp. symlink, https://wiki.archlinux.org/title/Networ … forwarding

Offline

#5 2025-09-06 21:31:29

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

Ok, seems like it's partially resolved. The original problem (or symptom) with the PulseAudio modules not working is now solved.

However log is still spammed by avahi-daemon withdrawing and registering address records. The host name conflicts are also spammed. I can see that this issue started exactly on 22th of July, and I get hundreds or a few thousand of host name conflicts per boot. And the changes - installing nss-mdns - did not fix this issue. And systemd-resolved is still running (despite being disabled)!

$ for N in $(seq -78 0) ; do echo -n BOOT $N, $(LANG=C date)\ :\  ; LANG=C journalctl -b$N -u avahi-daemon | grep -i "host name conflict" | tail -n 1 ;  done
BOOT -78, Sun Sep 7 00:28:06 EEST 2025 : 
BOOT -77, Sun Sep 7 00:28:06 EEST 2025 : Jul 20 13:28:45 ArkkiVille avahi-daemon[1359]: Host name conflict, retrying with ArkkiVille-2
BOOT -76, Sun Sep 7 00:28:06 EEST 2025 : 
BOOT -75, Sun Sep 7 00:28:07 EEST 2025 : 
BOOT -74, Sun Sep 7 00:28:07 EEST 2025 : Jul 21 17:33:35 ArkkiVille avahi-daemon[1359]: Host name conflict, retrying with ArkkiVille-2
BOOT -73, Sun Sep 7 00:28:07 EEST 2025 : Jul 21 23:49:41 ArkkiVille avahi-daemon[1362]: Host name conflict, retrying with ArkkiVille-2
BOOT -72, Sun Sep 7 00:28:07 EEST 2025 : 
BOOT -71, Sun Sep 7 00:28:07 EEST 2025 : Jul 22 13:37:19 ArkkiVille avahi-daemon[1386]: Host name conflict, retrying with ArkkiVille-91
BOOT -70, Sun Sep 7 00:28:07 EEST 2025 : Jul 22 18:44:24 ArkkiVille avahi-daemon[1356]: Host name conflict, retrying with ArkkiVille-321
BOOT -69, Sun Sep 7 00:28:07 EEST 2025 : Jul 22 20:34:13 ArkkiVille avahi-daemon[1352]: Host name conflict, retrying with ArkkiVille-134
BOOT -68, Sun Sep 7 00:28:07 EEST 2025 : Jul 23 23:41:10 ArkkiVille avahi-daemon[1362]: Host name conflict, retrying with ArkkiVille-559
BOOT -67, Sun Sep 7 00:28:08 EEST 2025 : Jul 25 16:56:29 ArkkiVille avahi-daemon[1369]: Host name conflict, retrying with ArkkiVille-50
BOOT -66, Sun Sep 7 00:28:08 EEST 2025 : Jul 26 02:02:31 ArkkiVille avahi-daemon[1357]: Host name conflict, retrying with ArkkiVille-114
BOOT -65, Sun Sep 7 00:28:08 EEST 2025 : Jul 27 05:58:55 ArkkiVille avahi-daemon[1372]: Host name conflict, retrying with ArkkiVille-403
BOOT -64, Sun Sep 7 00:28:08 EEST 2025 : Jul 27 17:47:04 ArkkiVille avahi-daemon[1366]: Host name conflict, retrying with ArkkiVille-528
BOOT -63, Sun Sep 7 00:28:08 EEST 2025 : Jul 27 22:51:25 ArkkiVille avahi-daemon[1280]: Host name conflict, retrying with ArkkiVille-464
BOOT -62, Sun Sep 7 00:28:08 EEST 2025 : Jul 28 23:40:20 ArkkiVille avahi-daemon[1368]: Host name conflict, retrying with ArkkiVille-1096
BOOT -61, Sun Sep 7 00:28:08 EEST 2025 : Jul 29 01:03:21 ArkkiVille avahi-daemon[1378]: Host name conflict, retrying with ArkkiVille-171
BOOT -60, Sun Sep 7 00:28:08 EEST 2025 : Jul 30 00:13:47 ArkkiVille avahi-daemon[1357]: Host name conflict, retrying with ArkkiVille-1033
BOOT -59, Sun Sep 7 00:28:09 EEST 2025 : Jul 30 07:55:55 ArkkiVille avahi-daemon[1368]: Host name conflict, retrying with ArkkiVille-506
BOOT -58, Sun Sep 7 00:28:09 EEST 2025 : Jul 31 00:43:04 ArkkiVille avahi-daemon[1369]: Host name conflict, retrying with ArkkiVille-1408
BOOT -57, Sun Sep 7 00:28:09 EEST 2025 : Jul 31 14:38:58 ArkkiVille avahi-daemon[1363]: Host name conflict, retrying with ArkkiVille-249
BOOT -56, Sun Sep 7 00:28:09 EEST 2025 : Aug 01 17:57:06 ArkkiVille avahi-daemon[1376]: Host name conflict, retrying with ArkkiVille-877
BOOT -55, Sun Sep 7 00:28:09 EEST 2025 : Aug 02 15:37:53 ArkkiVille avahi-daemon[1367]: Host name conflict, retrying with ArkkiVille-1077
BOOT -54, Sun Sep 7 00:28:10 EEST 2025 : Aug 03 17:51:40 ArkkiVille avahi-daemon[1371]: Host name conflict, retrying with ArkkiVille-388
BOOT -53, Sun Sep 7 00:28:10 EEST 2025 : Aug 03 21:15:58 ArkkiVille avahi-daemon[1351]: Host name conflict, retrying with ArkkiVille-154
BOOT -52, Sun Sep 7 00:28:10 EEST 2025 : Aug 05 02:32:04 ArkkiVille avahi-daemon[1424]: Host name conflict, retrying with ArkkiVille-1131
BOOT -51, Sun Sep 7 00:28:10 EEST 2025 : Aug 06 01:47:16 ArkkiVille avahi-daemon[1359]: Host name conflict, retrying with ArkkiVille-1677
BOOT -50, Sun Sep 7 00:28:10 EEST 2025 : Aug 07 04:20:21 ArkkiVille avahi-daemon[1381]: Host name conflict, retrying with ArkkiVille-1280
BOOT -49, Sun Sep 7 00:28:10 EEST 2025 : Aug 08 01:11:18 ArkkiVille avahi-daemon[1369]: Host name conflict, retrying with ArkkiVille-1342
BOOT -48, Sun Sep 7 00:28:11 EEST 2025 : Aug 08 17:05:15 ArkkiVille avahi-daemon[1383]: Host name conflict, retrying with ArkkiVille-766
BOOT -47, Sun Sep 7 00:28:11 EEST 2025 : Aug 09 02:30:22 ArkkiVille avahi-daemon[1411]: Host name conflict, retrying with ArkkiVille-805
BOOT -46, Sun Sep 7 00:28:11 EEST 2025 : Aug 10 04:46:29 ArkkiVille avahi-daemon[1356]: Host name conflict, retrying with ArkkiVille-44
BOOT -45, Sun Sep 7 00:28:11 EEST 2025 : Aug 12 00:44:56 ArkkiVille avahi-daemon[1362]: Host name conflict, retrying with ArkkiVille-2582
BOOT -44, Sun Sep 7 00:28:11 EEST 2025 : Aug 13 02:18:44 ArkkiVille avahi-daemon[1374]: Host name conflict, retrying with ArkkiVille-2047
BOOT -43, Sun Sep 7 00:28:12 EEST 2025 : Aug 13 12:55:40 ArkkiVille avahi-daemon[1337]: Host name conflict, retrying with ArkkiVille-364
BOOT -42, Sun Sep 7 00:28:12 EEST 2025 : Aug 13 21:16:37 ArkkiVille avahi-daemon[1328]: Host name conflict, retrying with ArkkiVille-544
BOOT -41, Sun Sep 7 00:28:12 EEST 2025 : Aug 14 09:07:19 ArkkiVille avahi-daemon[1365]: Host name conflict, retrying with ArkkiVille-11
BOOT -40, Sun Sep 7 00:28:12 EEST 2025 : Aug 15 04:22:54 ArkkiVille avahi-daemon[1351]: Host name conflict, retrying with ArkkiVille-1366
BOOT -39, Sun Sep 7 00:28:12 EEST 2025 : Aug 16 02:45:56 ArkkiVille avahi-daemon[1364]: Host name conflict, retrying with ArkkiVille-1565
BOOT -38, Sun Sep 7 00:28:12 EEST 2025 : Aug 16 15:30:22 ArkkiVille avahi-daemon[1382]: Host name conflict, retrying with ArkkiVille-295
BOOT -37, Sun Sep 7 00:28:12 EEST 2025 : Aug 17 01:47:34 ArkkiVille avahi-daemon[1372]: Host name conflict, retrying with ArkkiVille-212
BOOT -36, Sun Sep 7 00:28:13 EEST 2025 : Aug 17 13:32:52 ArkkiVille avahi-daemon[1371]: Host name conflict, retrying with ArkkiVille-136
BOOT -35, Sun Sep 7 00:28:13 EEST 2025 : Aug 18 02:02:10 ArkkiVille avahi-daemon[1372]: Host name conflict, retrying with ArkkiVille-360
BOOT -34, Sun Sep 7 00:28:13 EEST 2025 : Aug 19 16:31:54 ArkkiVille avahi-daemon[1368]: Host name conflict, retrying with ArkkiVille-2715
BOOT -33, Sun Sep 7 00:28:13 EEST 2025 : Aug 19 18:49:19 ArkkiVille avahi-daemon[1354]: Host name conflict, retrying with ArkkiVille-146
BOOT -32, Sun Sep 7 00:28:13 EEST 2025 : Aug 21 01:08:45 ArkkiVille avahi-daemon[1416]: Host name conflict, retrying with ArkkiVille-2024
BOOT -31, Sun Sep 7 00:28:13 EEST 2025 : Aug 22 03:28:03 ArkkiVille avahi-daemon[1365]: Host name conflict, retrying with ArkkiVille-1953
BOOT -30, Sun Sep 7 00:28:14 EEST 2025 : Aug 22 13:21:19 ArkkiVille avahi-daemon[1374]: Host name conflict, retrying with ArkkiVille-431
BOOT -29, Sun Sep 7 00:28:14 EEST 2025 : Aug 22 17:00:40 ArkkiVille avahi-daemon[1358]: Host name conflict, retrying with ArkkiVille-129
BOOT -28, Sun Sep 7 00:28:14 EEST 2025 : Aug 23 21:32:18 ArkkiVille avahi-daemon[1378]: Host name conflict, retrying with ArkkiVille-1175
BOOT -27, Sun Sep 7 00:28:14 EEST 2025 : Aug 24 09:32:34 ArkkiVille avahi-daemon[1370]: Host name conflict, retrying with ArkkiVille-89
BOOT -26, Sun Sep 7 00:28:14 EEST 2025 : Aug 25 05:41:33 ArkkiVille avahi-daemon[1371]: Host name conflict, retrying with ArkkiVille-1896
BOOT -25, Sun Sep 7 00:28:14 EEST 2025 : Aug 26 04:36:21 ArkkiVille avahi-daemon[1341]: Host name conflict, retrying with ArkkiVille-1583
BOOT -24, Sun Sep 7 00:28:15 EEST 2025 : Aug 26 07:23:45 ArkkiVille avahi-daemon[1358]: Host name conflict, retrying with ArkkiVille-290
BOOT -23, Sun Sep 7 00:28:15 EEST 2025 : Aug 27 02:46:17 ArkkiVille avahi-daemon[1382]: Host name conflict, retrying with ArkkiVille-1626
BOOT -22, Sun Sep 7 00:28:15 EEST 2025 : Aug 27 05:32:43 ArkkiVille avahi-daemon[1356]: Host name conflict, retrying with ArkkiVille-129
BOOT -21, Sun Sep 7 00:28:15 EEST 2025 : Aug 28 03:12:13 ArkkiVille avahi-daemon[1359]: Host name conflict, retrying with ArkkiVille-1573
BOOT -20, Sun Sep 7 00:28:15 EEST 2025 : Aug 28 21:17:57 ArkkiVille avahi-daemon[1354]: Host name conflict, retrying with ArkkiVille-1178
BOOT -19, Sun Sep 7 00:28:15 EEST 2025 : Aug 29 11:01:34 ArkkiVille avahi-daemon[1382]: Host name conflict, retrying with ArkkiVille-268
BOOT -18, Sun Sep 7 00:28:15 EEST 2025 : Aug 30 03:55:48 ArkkiVille avahi-daemon[1373]: Host name conflict, retrying with ArkkiVille-1458
BOOT -17, Sun Sep 7 00:28:15 EEST 2025 : Aug 30 17:26:19 ArkkiVille avahi-daemon[1366]: Host name conflict, retrying with ArkkiVille-903
BOOT -16, Sun Sep 7 00:28:16 EEST 2025 : Aug 31 01:33:27 ArkkiVille avahi-daemon[1363]: Host name conflict, retrying with ArkkiVille-650
BOOT -15, Sun Sep 7 00:28:16 EEST 2025 : Aug 31 13:31:00 ArkkiVille avahi-daemon[1350]: Host name conflict, retrying with ArkkiVille-106
BOOT -14, Sun Sep 7 00:28:16 EEST 2025 : Sep 01 23:48:43 ArkkiVille avahi-daemon[1367]: Host name conflict, retrying with ArkkiVille-2488
BOOT -13, Sun Sep 7 00:28:16 EEST 2025 : Sep 02 11:56:21 ArkkiVille avahi-daemon[1347]: Host name conflict, retrying with ArkkiVille-286
BOOT -12, Sun Sep 7 00:28:16 EEST 2025 : Sep 03 03:22:30 ArkkiVille avahi-daemon[1410]: Host name conflict, retrying with ArkkiVille-1098
BOOT -11, Sun Sep 7 00:28:16 EEST 2025 : Sep 03 07:54:24 ArkkiVille avahi-daemon[1357]: Host name conflict, retrying with ArkkiVille-77
BOOT -10, Sun Sep 7 00:28:16 EEST 2025 : Sep 03 23:58:05 ArkkiVille avahi-daemon[1350]: Host name conflict, retrying with ArkkiVille-1031
BOOT -9, Sun Sep 7 00:28:16 EEST 2025 : Sep 04 12:23:54 ArkkiVille avahi-daemon[1341]: Host name conflict, retrying with ArkkiVille-396
BOOT -8, Sun Sep 7 00:28:16 EEST 2025 : Sep 04 21:10:29 ArkkiVille avahi-daemon[1381]: Host name conflict, retrying with ArkkiVille-58
BOOT -7, Sun Sep 7 00:28:17 EEST 2025 : Sep 05 01:42:17 ArkkiVille avahi-daemon[1377]: Host name conflict, retrying with ArkkiVille-548
BOOT -6, Sun Sep 7 00:28:17 EEST 2025 : Sep 05 12:07:37 ArkkiVille avahi-daemon[1359]: Host name conflict, retrying with ArkkiVille-723
BOOT -5, Sun Sep 7 00:28:17 EEST 2025 : 
BOOT -4, Sun Sep 7 00:28:17 EEST 2025 : 
BOOT -3, Sun Sep 7 00:28:17 EEST 2025 : Sep 06 22:29:30 ArkkiVille avahi-daemon[80718]: Host name conflict, retrying with ArkkiVille-2
BOOT -2, Sun Sep 7 00:28:17 EEST 2025 : Sep 06 22:42:09 ArkkiVille avahi-daemon[1379]: Host name conflict, retrying with ArkkiVille-20
BOOT -1, Sun Sep 7 00:28:17 EEST 2025 : Sep 07 00:06:42 ArkkiVille avahi-daemon[10277]: Host name conflict, retrying with ArkkiVille-2
BOOT 0, Sun Sep 7 00:28:17 EEST 2025 : Sep 07 00:21:22 ArkkiVille avahi-daemon[1379]: Host name conflict, retrying with ArkkiVille-15

I've disabled disable-publishing temporarily at boot -5, which seems to resolve this log spamming issue. However I feel I don't know what is really going on here...

Offline

#6 2025-09-06 21:33:20

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

Here are the enabled services:

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
atd.service                              | multi-user.target.wants
avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
ckb-next-daemon.service                  | multi-user.target.wants
clamav-daemon.service                    | multi-user.target.wants
clamav-freshclam-once.timer              | timers.target.wants
clamav-freshclam.service                 | multi-user.target.wants
coolercontrold.service                   | multi-user.target.wants
cpupower.service                         | multi-user.target.wants
cronie.service                           | multi-user.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.NetworkManager.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
display-manager.service                  | system
fan-control.service                      | multi-user.target.wants
fangfrisch.timer                         | timers.target.wants
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
gpm.service                              | multi-user.target.wants
linux-modules-cleanup.service            | basic.target.wants
lm_sensors.service                       | multi-user.target.wants
lock-optdrive-suspend.service            | suspend.target.wants
monitorix.service                        | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nfsv4-server.service                     | multi-user.target.wants
ntpd.service                             | multi-user.target.wants
nvidia-hibernate.service                 | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-suspend.service.wants
nvidia-resume.service                    | systemd-suspend-then-hibernate.service.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
p11-kit-server.socket                    | sockets.target.wants
paccache.timer                           | timers.target.wants
pacredir.service                         | multi-user.target.wants
pacserve.service                         | multi-user.target.wants
pcscd.socket                             | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
postfix.service                          | multi-user.target.wants
rasdaemon.service                        | multi-user.target.wants
ras-mc-ctl.service                       | multi-user.target.wants
reflector.timer                          | timers.target.wants
remote-fs.target                         | multi-user.target.wants
sensord.service                          | multi-user.target.wants
smartd.service                           | multi-user.target.wants
snapper-timeline.timer                   | timers.target.wants
sshd.service                             | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

EDIT: I can see systemd-resolved has started to be run also exactly on 22th of July. Maybe it's a stray .pacnew (I know... I'm lazy and messy sometimes). I'm checking them next.

Last edited by Wild Penguin (2025-09-06 21:39:59)

Offline

#7 2025-09-06 22:47:20

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,056

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

stat /etc/resolv.conf

Offline

#8 2025-09-07 11:38:15

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

I've checked all my .pacnew, none had networking-related changes and most (if all) were only comment changes.

$ LANG=C stat /etc/resolv.conf
  File: /etc/resolv.conf
  Size: 65              Blocks: 8          IO Block: 4096   regular file
Device: 0,30    Inode: 43835670    Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2025-09-07 14:21:46.418941235 +0300
Modify: 2025-09-07 14:21:46.398941339 +0300
Change: 2025-09-07 14:21:46.401275047 +0300
 Birth: 2025-09-07 14:21:46.398941339 +0300

Last edited by Wild Penguin (2025-09-07 11:38:46)

Offline

#9 2025-09-07 12:48:07

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,056

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

So that looks innocent…

grep -riE '(dns|resolv)' /etc/NetworkManager/conf.d/

If that doesn't show up anything, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

- maybe we can spot the trigger from the context.
You could also try to enforce

dns=default
rc-manager=file

https://wiki.archlinux.org/title/Networ … management

Offline

#10 2025-09-07 14:01:25

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

There is nothing in /etc/NetworkManager/conf.d/ on this computer (the other one does have system-wide configurations, since it's more like a server, but is also having the same symptoms). This is a desktop computer so I manage the little network connections I need via a NetworkManager GUI (I occasionally need to use a VPN for university stuff). It's a simple wired connection to my router. IIRC NetworkManager - per default  - makes a simple DHCP connection to any wired connection it can find?

My router gives static leases for IPv4 and IPv6 addressess via DHCP as I've configured them - in case you are wondering my L337 adressing.

$ nmcli connection 
NAME                                                 UUID                                  TYPE      DEVICE  
Wired connection 2                                   3e22b6c3-c3cb-3707-91d4-7febdcc2cff4  ethernet  enp42s0 
lo                                                   82ca21cf-0b69-4182-bf7f-476d5fbfe274  loopback  lo      
openvpn.oulu.fi_student_20250905_YO-OpenVPN-Student  fef6a0af-2332-43a7-b53e-2110809773da  vpn       --      
Wired connection 1                                   7c2d789e-8905-3627-aec0-bd705a5f9efb  ethernet  --      

Here is a log from this ongoing boot: http://0x0.st/KqN3.txt . 546 Host name conflicts so far.

Offline

#11 2025-09-07 14:06:23

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

Hmm, I searched for systemd-resolved in the log and noticed this:

syys 07 08:39:44 ArkkiVille systemd-resolved[1276]: /etc/hosts:1: address '<<<<<<<' is invalid, ignoring: Invalid argument
syys 07 08:39:44 ArkkiVille systemd-resolved[1276]: /etc/hosts:12: address '=======' is invalid, ignoring: Invalid argument
syys 07 08:39:44 ArkkiVille systemd-resolved[1276]: /etc/hosts:17: address '>>>>>>>' is invalid, ignoring: Invalid argument

I don't know what happened to hosts file. I must have messed up with some .pacnew update somehow. I've fixed it now, but probably this has nothing to do with the issue.

Offline

#12 2025-09-07 14:32:29

Wild Penguin
Member
Registered: 2015-03-19
Posts: 382

Re: [SOLVED] Avahi-daemon spams log with conflicting address and mDNS stck

Well, I did a:

sudo grep -Hirn resolved /etc

To see if there's something peculiar and found:

$ dog 01-pacredir-MulticastDNS-yes.conf 
# This file is shipped by pacredir to enable multicast DNS in
# systemd-resolved globally. That functionality is required, though
# you may want to enable it on specific interfaces only.
# See systemd-resolved(8) and resolved.conf(5) for details.
#
# If you need avahi-daemon running on your system install
# optional package 'pacredir-avahi' for compatibility.

[Resolve]
MulticastDNS=yes

So I believe pacredir is starting systemd-resolved. I did not have installed pacredir-avahi. I had somehow missed this:

pacman.log:382134:[2025-07-22T12:13:41+0300] [ALPM] upgraded pacredir (0.6.0-1 -> 0.7.2-1)
pacman.log:382135:[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  > This upgrade to pacredir 0.7.2-1 changes the backend used for service discovery,
pacman.log-382136-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  > it depends on systemd-resolved now. By default that is used to announce the
pacman.log-382137-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  > service as well, so disable and stop avahi, and reload systemd-resolved:
pacman.log-382138-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  >   # systemctl disable avahi-daemon.socket avahi-daemon.service
pacman.log-382139-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  >   # systemctl stop avahi-daemon.socket avahi-daemon.service
pacman.log-382140-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  >   # systemctl reload systemd-resolved.service
pacman.log-382141-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  > Alternatively install the optional avahi compatibility package
pacman.log:382142:[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  > 'pacredir-avahi' on top.
pacman.log-382143-[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  > Finally restart the services:
pacman.log:382144:[2025-07-22T12:13:41+0300] [ALPM-SCRIPTLET]  >   # systemctl restart pacredir.service pacserve.service

(well, it's actually quite easy to miss stuff on upgrades, and it's my PC after all. Whoops!)

Thanks seth for getting me on the right track. Marking as [SOLVED]!

EDIT: There is still a singular host name conflict in the log and the host name is changed to ArkkiVille-2. However the log is not noisy anymore and I can live with that, and it's certainly not perfect. Perhaps some slight adjustment could be made on pacredir  / pacserve....

EDIT2: Seems like my other computer does not get even the singular host name conflict while the other one does. I suspect an Avahi bug. The issue seems very similar to this one: https://bbs.archlinux.org/viewtopic.php?id=284081

EDIT3: Without any other information, the singular host name conflict also disappeared after some subsequent boot.

Last edited by Wild Penguin (2025-09-16 18:40:07)

Offline

Board footer

Powered by FluxBB