+++ This bug was initially created as a clone of Bug #1170814 +++ Description of problem: The supplied logrotate configuration in extras/glusterfs-georep-logrotate causes errors for every logrotate execution due to the definition of "/var/log/glusterfs/geo-replication-slaves/*/*.log". The missingok directive is inbetween postrotate and endscript, it needs to be mmoved before the postrotate directive. Version-Release number of selected component (if applicable): 3.6.1 How reproducible: Every time. Steps to Reproduce: Call `logrotate /etc/logrotate.conf' with glusterfs logrotate config from: extras/glusterfs-georep-logrotate in "/etc/logrotate.d/". Actual results: error: glusterfs-georep:31 glob failed for /var/log/glusterfs/geo-replication-slaves/*/*.log: No such file or directory error: found error in file glusterfs-georep, skipping Expected results: No error message at all. Additional info: --- Additional comment from Anand Avati on 2014-12-04 23:46:39 CET --- REVIEW: http://review.gluster.org/9239 (Stop logrotate from complaining about missing files.) posted (#1) for review on release-3.6 by Jan-Hendrik Zab (zab)
REVIEW: http://review.gluster.org/9264 (Stop logrotate from complaining about missing files.) posted (#1) for review on master by Jan-Hendrik Zab (zab)
COMMIT: http://review.gluster.org/9264 committed in master by Niels de Vos (ndevos) ------ commit e679d6417d39a696126e3f7ede1f2f38afc6e44c Author: Jan-Hendrik Zab <zab> Date: Thu Dec 4 23:41:09 2014 +0100 Stop logrotate from complaining about missing files. Previously logrotate reported errors for files missing in "/var/log/glusterfs/geo-replication-slaves/*/*.log". Fixed by reordering directives in the example config. Change-Id: I7cdb9e0d82f08aa27d5e26664660204fdeb8e98e BUG: 1170825 Signed-off-by: Jan-Hendrik Zab <zab> Reviewed-on: http://review.gluster.org/9264 Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Lalatendu Mohanty <lmohanty>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user