Adding to this:
The snapclient polls Avahi only if no server was explicitly defined via
"-h" and in case "-p" CLI options.
The snapserver needs to announce or have announced itself via Avahi,
else the client keeps polling forever, getting this CACHE_EXHAUSTED
answer for some reason. This also means that the Avahi daemon needs to
run before the snapserver is started, since it does not announce itself
if Avahi was not running at its startup.
These infinite messages are still not great, and CACHE_EXHAUSTED is a
weird answer, which happens even when setting e.g.
"cache-entries-max=1000000" in /etc/avahi/avahi-daemon.conf (default is
4096).
There is an upstream issue which I necroed, probably a new one makes
sense to think about how to enhance the situation if the Avahi daemon is
not running: https://github.com/badaix/snapcast/issues/647
If avahi-daemon is not installed or running (and not triggering on
socket), there is btw another error every second, so that does not make
things better:
```
(Controller) Exception: BrowseAvahi - Failed to create client: Daemon
not running
```
It is a recommendation but no strict dependency, which is somewhat
reasonable. So it is however possible to remove it.
Best regards,
Micha
