I have restarted docker daemon, and it don't want to start - probably because of the filebeat, last log from docker service is: Feb 05 11:30:30 server.address.com dockerd[86573]: time="2021-02-05T11:30:30.700507408Z" level=info msg="Loading containers: start.
Docker commands are unresponsive, restarting docker service is getting me the same situation, kill -9 filebeat-process-id/kill filebeat-process-id is not working. Do you have any ideas besides restarting of the server?
Last log that I have from filebeat container is: 2021-02-02T12:35:14.380Z ERROR pipeline/output.go:121 Failed to publish events: 400 Bad Request: {"error":{"root_cause":[{"type":"remote_transport_exception","reason":"[elastic-ingest-1][ip-address:9300][indices:data/write/bulk]"}],"type":"illegal_argument_exception","reason":"no write index is defined for alias [alias-name]. The write index may be explicitly disabled using is_write_index=false or the alias points to multiple indices without one being designated as a write index"},"status":400}
Can you even docker run sth? If your docker daemon is not responding you can try to restart it, otherwise your system is problematic in general and a restart may be the way to go regardless of Filebeat's involvement.
I don't think that Filebeat as a container could make docker daemon crash/stall directly. Maybe sth else went wrong on the system (could be related to filebeat's container) but cannot assume what.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.