# /tmp filling up with core dumps in Elastic Synthetics

**URL:** <https://discuss.elastic.co/t/tmp-filling-up-with-core-dumps-in-elastic-synthetics/370713>\
**Category:** Elastic Agent\
**Created:** [November 18, 2024, 6:08pm UTC](https://discuss.elastic.co/t/tmp-filling-up-with-core-dumps-in-elastic-synthetics/370713 "2024-11-18T18:08:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)\
**Post date:** [November 18, 2024, 6:08pm UTC](https://discuss.elastic.co/t/tmp-filling-up-with-core-dumps-in-elastic-synthetics/370713/1 "2024-11-18T18:08:30Z")

</div>

I am using Elastic Agent in our EKS cluster. Today I was notified by the cluster admin that the Synthetics nodes, which currently run `elastic-agent-complete:8.15.3` are periodically filling the available disk space on the nodes, causing them to crash. When diving into it, we are finding that when this occurs, it is the result of core dumps filling up the available disk space.

I find a reference to a similar situation [here](https://discuss.elastic.co/t/elastic-agent-heartbeat-folder-filled-with-core-dumps/301262), along with the suggestion to disable coredumps. This is a workable solution for me. However, I am not able to find any specific instructions on how to do this.

Help?
