January 3, 20242 yr Not sure what changed but my logs are being flooded with the following all of a sudden: Jan 2 23:57:12 Tower avahi-daemon[4533]: Registering new address record for 192.168.1.2 on bond0.IPv4. Jan 2 23:57:32 Tower avahi-daemon[4533]: Host name conflict, retrying with Tower-213 Jan 2 23:57:32 Tower avahi-daemon[4533]: Registering new address record for 192.168.1.2 on bond0.IPv4. Jan 2 23:57:52 Tower avahi-daemon[4533]: Host name conflict, retrying with Tower-214 I did some googling and found the following thread which suggests running the following `lsof -i -P -n | grep 5353` to identify what is using avahi-daemon service. When I do the following I get the results below: root@Tower:~# lsof -i -P -n | grep 5353 lsof: no pwd entry for UID 105 lsof: no pwd entry for UID 105 homebridg 431 root 36u IPv4 11114528 0t0 UDP *:5353 homebridg 431 root 37u IPv4 11114531 0t0 UDP *:5353 homebridg 431 root 38u IPv4 11114534 0t0 UDP *:5353 homebridg 431 root 39u IPv4 11114537 0t0 UDP *:5353 homebridg 431 root 41u IPv4 11095682 0t0 UDP *:5353 avahi-dae 4533 avahi 14u IPv4 5688774 0t0 UDP *:5353 python3 24788 root 13u IPv4 72963 0t0 UDP *:5353 node 26312 root 31u IPv4 64934 0t0 UDP *:5353 node 26312 root 32u IPv4 64935 0t0 UDP *:5353 lsof: no pwd entry for UID 105 lsof: no pwd entry for UID 105 avahi-dae 27626 105 10u IPv4 65043 0t0 UDP *:5353 I have attached my diagnostics. Would anyone be able to help with this issue? Thank you so much and Happy New Year!! tower-diagnostics-20240103-0001.zip
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.