# Elasticsearch 1.7 logrotation crashes for clusters with low logging
**URL:** https://discuss.elastic.co/t/elasticsearch-1-7-logrotation-crashes-for-clusters-with-low-logging/216017
**Category:** Elasticsearch
**Created:** [January 22, 2020, 9:27am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-logrotation-crashes-for-clusters-with-low-logging/216017 "2020-01-22T09:27:59Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@workaround](https://discuss.elastic.co/u/workaround)
#### Post date: [January 22, 2020, 9:27am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-logrotation-crashes-for-clusters-with-low-logging/216017/1 "2020-01-22T09:27:59Z")
Hello,
We have specific active Elasticsearch clusters whose logrotation crushes frequently.
We have more than 100 elasticsearch clusters and just some specific keep crushing their logrotation.
After investigation, I have come to conclude that it has something to do with the small amount of logging to those clusters. Some days there are no logs to those clusters.
I have two suspects:
1. either log4j.properties minimum size, which I could not locate ( as a file ) somewhere in the installation. Thus I wonder wether it is overriden by something or has some kind of defaults if not present.
2. The conversion pattern of the logs which looks something like this:
**log4j or logging.yml?**
Thanks!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 19, 2020, 9:35am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-logrotation-crashes-for-clusters-with-low-logging/216017/2 "2020-02-19T09:35:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.