Comment 3 for bug 1679117

Commenting here as the duplicate parent is Private at the moment.

Main issue is here, hitting rlimit-data which is set by default in the config file to 4M
> kernel: mmap: avahi-daemon (992): VmData 4272128 exceed data ulimit 4194304. Update limits or use boot option ignore_rlimit_data.

Not sure what is causing this to go high on a few machines, possibly number of services on the network. Testing here it looks like avahi needs generally about 2M when publishing 30+ services so this limit is likely way too low given we're over 50% there in common usage.

Main thing to confirm here is that this is simply hitting the limit in normal usage, and not a bug causing runaway memory usage. If anyone would like to test it would be great to:

 (a) Confirm whether this happens constantly (does avahi always crash) or did it happen once-off and not happen again. If restart now does it crash again? systemctl restart avahi-daemon
 (b) Modify /etc/avahi/avahi-daemon.conf and change "rlimit-data=4194304" to "rlimit-data=16777216"
 (c) restart avahi-daemon again: systemctl restart avahi-daemon
 (c) report back if the crash occured both before, and after the change