March 9, 20242 yr I’ve searched the forums, Reddit, Google, etc. I’m struggling what’s causing avahi daemon to spam my logs with “withdrawing/registering” over and over. there are no host-name conflicts that I am aware of on my network. nothing else is using .local TLD either. there are no static IPv6 addresses assigned to any of my devices. It’s even set to automatic/dhcp in my network settings on unraid. attached are the diagnostics. tower-diagnostics-20240309-1118.zip Edited March 9, 20242 yr by MowMdown
March 11, 20242 yr Author @JorgeB I went ahead and disabled IPv6 and that seemed to have worked however, It's not the most ideal solution as it doesn't fix the underlying cause. Here's some more log from yesterday before I shut IPv6 off. I'm thinking whatever is causing the WARNING is the cause for the log spam. The only docker I can think of that would maybe cause this is pi-hole? Do you see anything else in my diags pointing to a culprit? Mar 9 22:11:34 Tower emhttpd: Starting services... Mar 9 22:11:34 Tower emhttpd: shcmd (265570): chmod 0777 '/mnt/user/docker' Mar 9 22:11:34 Tower emhttpd: shcmd (265571): chown 'nobody':'users' '/mnt/user/docker' Mar 9 22:11:34 Tower emhttpd: shcmd (265574): /etc/rc.d/rc.avahidaemon restart Mar 9 22:11:34 Tower root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Mar 9 22:11:34 Tower avahi-daemon[17101]: Got SIGTERM, quitting. Mar 9 22:11:34 Tower avahi-daemon[17101]: Leaving mDNS multicast group on interface br0.IPv6 with address fdf0:6a76:b27e:1:ec4:7aff:fe64:9e01. Mar 9 22:11:34 Tower avahi-daemon[17101]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.4.100. Mar 9 22:11:34 Tower avahi-dnsconfd[17111]: read(): EOF Mar 9 22:11:34 Tower avahi-daemon[17101]: avahi-daemon 0.8 exiting. Mar 9 22:11:35 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Mar 9 22:11:35 Tower avahi-daemon[26563]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Mar 9 22:11:35 Tower avahi-daemon[26563]: Successfully dropped root privileges. Mar 9 22:11:35 Tower avahi-daemon[26563]: avahi-daemon 0.8 starting up. Mar 9 22:11:35 Tower avahi-daemon[26563]: Successfully called chroot(). Mar 9 22:11:35 Tower avahi-daemon[26563]: Successfully dropped remaining capabilities. Mar 9 22:11:35 Tower avahi-daemon[26563]: Loading service file /services/sftp-ssh.service. Mar 9 22:11:35 Tower avahi-daemon[26563]: Loading service file /services/ssh.service. Mar 9 22:11:35 Tower avahi-daemon[26563]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Mar 9 22:11:35 Tower avahi-daemon[26563]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Mar 9 22:11:35 Tower avahi-daemon[26563]: Joining mDNS multicast group on interface br0.IPv6 with address fdf0:6a76:b27e:1:ec4:7aff:fe64:9e01. Mar 9 22:11:35 Tower avahi-daemon[26563]: New relevant interface br0.IPv6 for mDNS. Mar 9 22:11:35 Tower avahi-daemon[26563]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.4.100. Mar 9 22:11:35 Tower avahi-daemon[26563]: New relevant interface br0.IPv4 for mDNS. Mar 9 22:11:35 Tower avahi-daemon[26563]: Network interface enumeration completed. Mar 9 22:11:35 Tower avahi-daemon[26563]: Registering new address record for fdf0:6a76:b27e:1:ec4:7aff:fe64:9e01 on br0.*. Mar 9 22:11:35 Tower avahi-daemon[26563]: Registering new address record for 2604:2d80:968e:b300:ec4:7aff:fe64:9e01 on br0.*. Mar 9 22:11:35 Tower avahi-daemon[26563]: Registering new address record for 192.168.4.100 on br0.IPv4. Mar 9 22:11:35 Tower emhttpd: shcmd (265575): /etc/rc.d/rc.avahidnsconfd restart Mar 9 22:11:35 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Mar 9 22:11:35 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Mar 9 22:11:35 Tower avahi-dnsconfd[26572]: Successfully connected to Avahi daemon. Mar 9 22:11:35 Tower avahi-daemon[26563]: Server startup complete. Host name is Tower.local. Local service cookie is 2084411687. Mar 9 22:11:36 Tower avahi-daemon[26563]: Registering new address record for fd91:1ac0:7f43:c44:ec4:7aff:fe64:9e01 on br0.*. Mar 9 22:11:36 Tower avahi-daemon[26563]: Service "Tower" (/services/ssh.service) successfully established. Mar 9 22:11:36 Tower avahi-daemon[26563]: Service "Tower" (/services/sftp-ssh.service) successfully established.
March 11, 20242 yr 21 minutes ago, MowMdown said: The only docker I can think of that would maybe cause this is pi-hole? Maybe, I'm not familiar with it, but I don't think this is normal: 21 minutes ago, MowMdown said: *** WARNING: Detected another IPv4 mDNS stack running on this host. 21 minutes ago, MowMdown said: *** WARNING: Detected another IPv6 mDNS stack running on this host.
March 12, 20242 yr Author I think I found the culprit maybe? nobody 19635 0.8 2.3 1609296 388820 ? Ssl 10:06 5:39 python3 -m homeassistant -c /config Before and After stopping HA docker and restarting unraid mDNS: After, clearly homeassinstant is what I think is the source for the mDNS conflicting issue Edited March 12, 20242 yr by MowMdown
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.