It turns out that we had inadvertently disabled IPv6 support. The “ipv6: true” line had been removed from the config. With this config removed, when under heavy load, the error messages occurred. After putting the configuration back, the error messages went away.