Persistent i/o timeout errors on all beats

Hi folks, I know, there's plenty of these topics around but they're either old, or have no resolution; and I'm looking for one. I'm seeing persistent i/o errors and connection reset by peer errors across all beats I run.

Setup is quite simple; beats feeding to a single logstash ingest storing to elasticsearch.

There's no real reason why this should happen, the beats running on the same machine as logstash have absolutely 0 problems; only beats connecting remotely seem to be affected. It's a little disheartening since we put a lot of time and effort into getting our Elastic stack going, and having it stop functioning 15 minutes or so after restarting all beats is not really making it look like a sound investment.

Anyone have any idea, at all, how to proceed? It's driving me batty.

This topic was automatically closed after 21 days. New replies are no longer allowed.