Hide Forgot
Description of problem: ----------------------- Installed the latest RHGS 3.1.3 ( glusterfs-3.7.9-1.el7rhgs ) After a weekend, logrotation of logfile has happened and observed error messages in glusterd log file Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHEL 7.2 RHGS 3.1.3 nightly build ( glusterfs-3.7.9-1.el7rhgs ) How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Install RHGS 3.1.3 nightly build and start glusterd 2. Perform few gluster operations and make sure that the glusterd log file has been updated with the logs 3. After a week, logrotation ( as per glusterfs logrotate conf ) Actual results: --------------- Observed error messages in glusterd logfile as follows : "[2016-03-28 08:25:48.232584] C [MSGID: 101012] [logging.c:2460:gf_cmd_log] 0-management: failed to open logfile "/var/log/glusterfs/cmd_history.log" [Invalid argument]" Expected results: ----------------- No errors should be seen in glusterd logs post logrotate
This has been introduced by the fix for BZ 1276219 which has been targeted for 3.1.3 which makes this bug a mandatory fix for 3.1.3. An upstream patch http://review.gluster.org/#/c/13829/ has been posted for review.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Mainline patch : http://review.gluster.org/#/c/13829/ 3.7 patch : http://review.gluster.org/13847 downstream patch : https://code.engineering.redhat.com/gerrit/71161
Verified this bug using the nightly build "glusterfs-3.7.9-2" No critical error message observed related to cmd_history log rotate mentioned in description section. Moving to verified state.
Removed the blocker BZ tagged.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1240