# Gradle daemon produces a lot of logs

**URL:** <https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905>\
**Category:** Help/Discuss\
**Created:** [June 1, 2015, 6:50pm UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905 "2015-06-01T18:50:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jk1](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/jk1/32/2441_2.png) [@jk1](https://discuss.gradle.org/u/jk1)\
**Post date:** [June 1, 2015, 6:50pm UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905/1 "2015-06-01T18:50:40Z")

</div>

We’re using gradle daemon for some time and are quite happy with it, as it significantly speeds up the build.

It turned out, however, that gradle daemon logs every build within ~/.gradle/daemon/2.4/daemon-XXXX.out and these files are never cleared. Given that our build produces ~250M of debug output, these logs may ate up the entire partition, just like like it happened on our build server today. Of course it’s possible to remove-d option from buildserver builds, but I’d prefer to keep it to ease failed builds investigation.

Q: Is there a way I can prevent gradle daemon from logging into it’s own folder? Or at least enforce some policy to rotate/cleanup these files?

Thanks in advance for your time and effort.

---

<div class="post-metadata">

**Author:** ![luke\_daley](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/luke_daley/32/9890_2.png) [@luke\_daley](https://discuss.gradle.org/u/luke_daley)\
**Post date:** [June 2, 2015, 12:51am UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905/2 "2015-06-02T00:51:35Z")

</div>

Hi,

There’s no hygiene around this right now unfortunately. You’ll have to implement your own cleanup procedure.

---

<div class="post-metadata">

**Author:** ![jk1](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/jk1/32/2441_2.png) [@jk1](https://discuss.gradle.org/u/jk1)\
**Post date:** [June 3, 2015, 8:33pm UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905/3 "2015-06-03T20:33:31Z")

</div>

Hi Luke,

Thanks for clarification on that matter.  
I ended up with the following cleaning routine in my build script:

```
def gradle = project.getGradle()
new File("${gradle.getGradleUserHomeDir().getAbsolutePath()}/daemon/${gradle.getGradleVersion()}").listFiles().each {
    if (it.getName().endsWith('.out.log')) {
        logger.debug("Cleaning up daemon log file $it")
        it.delete()
    }
}
```

---

<div class="post-metadata">

**Author:** ![briemla](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@briemla](https://discuss.gradle.org/u/briemla)\
**Post date:** [March 1, 2021, 8:56am UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905/4 "2021-03-01T08:56:52Z")

</div>

Hi,

has there been any progress on hygiene around the gradle-daemon?

---

<div class="post-metadata">

**Author:** ![busitech](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@busitech](https://discuss.gradle.org/u/busitech)\
**Post date:** [March 30, 2022, 1:26am UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905/5 "2022-03-30T01:26:34Z")

</div>

These logs are huge. Progress should be made in this area.

---

<div class="post-metadata">

**Author:** ![sflothow](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sflothow/32/12016_2.png) [@sflothow](https://discuss.gradle.org/u/sflothow)\
**Post date:** [July 14, 2026, 1:01pm UTC](https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905/6 "2026-07-14T13:01:28Z")

</div>

Automatic cleanup has been implemented in 9.4: [https://docs.gradle.org/9.4.0/release-notes.html#daemon-logging-improvements](https://docs.gradle.org/9.4.0/release-notes.html#daemon-logging-improvements)