just notice some warning in my logs in unraid a little over a week ago

Dec 5 20:05:14: avahi-daemon[2437]: avahi_normalize_name() failed.

Dec 5 20:05:14 avahi-daemon[2437]: avahi_key_new() failed.

chatgpt gave this response

you’re seeing this on Unraid. This is actually a pretty common Avahi/mDNS issue on Unraid servers, especially after updates. In Unraid, Avahi is used mainly for network discovery (like for SMB/AFP or mDNS host/service announcements).

Specifically:

• avahi_normalize_name() failed → Unraid tried to advertise a service or hostname, but the name had invalid characters. Often this happens if your server name, share name, or Docker/VM hostname contains spaces, underscores, or special characters.

• avahi_key_new() failed → Avahi can’t create an internal identifier for that invalid name.

Typical Unraid triggers:

1. Server/host name issues:

   • Check the main server name in Settings → Identification. Only letters, numbers, and hyphens are safe.

2. Shares with unusual names:

   • If a share has spaces, dots, or special characters, Avahi may try to announce it and fail.

3. Docker or VM hostnames:

   • Some containers or VMs register themselves with Avahi. Invalid names here can trigger this.

How to fix:

1. Make sure the server name has only letters, numbers, and hyphens.

2. Check your shares, VMs, and Docker containers for names with invalid characters. Rename them if needed.

3. Restart Avahi to clear the error:

i did find a share that had a a space in it. i changed the name to not have spaces but it came back later today. i have not rebooted the server. it did say you could use this in the terminal

/etc/rc.d/rc.avahi restart

anyone deal with this before?

Please post the diagnostics