# The logstash container crashes the network of the host machine and then exit with OOM killer **URL:** \ **Category:** Logstash\ **Tags:** docker\ **Created:** [January 26, 2022, 3:36pm UTC](https://discuss.elastic.co/t/the-logstash-container-crashes-the-network-of-the-host-machine-and-then-exit-with-oom-killer/295477 "2022-01-26T15:36:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ahmad\_BenMaallem](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@Ahmad\_BenMaallem](https://discuss.elastic.co/u/Ahmad_BenMaallem)\ **Post date:** [January 26, 2022, 3:36pm UTC](https://discuss.elastic.co/t/the-logstash-container-crashes-the-network-of-the-host-machine-and-then-exit-with-oom-killer/295477/1 "2022-01-26T15:36:51Z")
Hello, I am trying to run a logstash 7.14.1 with docker-compose to collect logs from multiple files and write them to a remote Elasticsearch. After starting, logstash manages to send my logs to Elasticsearch without problems but after a while, my machine's network crashes for a few minutes (5 to 10 minutes) until there is an OOM kill signal for the logstash container. I tried to limit the memory and cpu usage for my logstash container but still I will have the same problem. knowing that the docker stats command does not show a memory/cpu overload. It seems that the Out Of Memory is like a side effect and is not the origin of the problem. Other information may be useful, I had the problem on a "Red Hat Enterprise Linux 8.3 (Ootpa)" and I could not reproduce the problem on a centos 8. Thank you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 23, 2022, 3:37pm UTC](https://discuss.elastic.co/t/the-logstash-container-crashes-the-network-of-the-host-machine-and-then-exit-with-oom-killer/295477/2 "2022-02-23T15:37:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.