The installed logrotate config snippet, located at /etc/logrotate.d/glusterfs, sets some logrotate options (such as weekly, rotate etc.) in the global scope, instead of the (gluster log) file scope. This overwrites user defined settings from /etc/logrotate.conf For example, if one has configured logrotated to rotate the files on a daily basis, /etc/logrotate.d/glusterfs change this setting to a weekly basis. On a busy system this is can be fatal, as it might fill up the available space. Reproducible: Always Steps to Reproduce: head -n 15 /etc/logrotate.d/glusterfs Actual Results: # perform the log rotate every week weekly # keep the backup of 52 weeks rotate 52 missingok # compress the logs, but from the .2 onwards compress delaycompress notifempty # Rotate client logs /var/log/glusterfs/*.log { sharedscripts postrotate Expected Results: Please move all the gluster log file specific logrotate options to: /var/log/glusterfs/*.log { [...] } and # Rotate server logs /var/log/glusterfs/bricks/*.log { [...] } Apart from that, it is questionable if one really wants 52 weeks of back-logs.
Indeed Christian, thanks for your patience. I've shipped a logrotate script with the ebuilds now, it's fixed in tree. + 14 Feb 2014; Ultrabug <ultrabug@gentoo.org> glusterfs-3.4.0-r1.ebuild, + glusterfs-3.4.1.ebuild, glusterfs-3.4.2.ebuild, +files/glusterfs.logrotate: + fix 3.4.x logrotate script #490672 thx to Christian Affolter +
