Bug #8418
Updated by François ARMAND about 7 years ago
Edit: the logrotate problem is linked to a configuration file not correctly updated during upgrade. That's why the title does not match the description.
Please have some kind of log-rotation enabled for @non-compliant-reports.log@, otherwise it might get veeery big:
<pre>
ruddersrv:/var/log/rudder/compliance # ll -h non-compliant-reports.log
-rw-r----- 1 root root 7.4G May 30 11:56 non-compliant-reports.log
</pre>
Our for example currently holds the logs since @[2015-10-16 04:39:20+0200]@.