Description of problem: ----------------------- After cmd_history log file got rotate, the next executed gluster commands are not present in the latest cmd_history.log file. Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs-3.7.5-0.3 How reproducible: ----------------- Always and Observed this issue on two nodes. Steps to Reproduce: ------------------- 1.Once cmd_history.log file got rotated. 2.Execute the new gluster commands 3.Check the commands executed in step-2 are present in cmd_history.log file (/var/log/glusterfs/cmd_history.log) Actual results: --------------- After log rotate, next executed gluster commands are not present in the latest cmd_history.log file Expected results: ----------------- After log rotate, next executed gluster commands should present in the latest cmd_history.log file Additional info:
Aren't you able to see none of the gluster CLI commands or few of them?
(In reply to Atin Mukherjee from comment #2) > Aren't you able to see none of the gluster CLI commands or few of them? Only empty cmd_history.log file i saw after log rotate.
What all gluster commands were run post upgrade? The reason I am asking all these questions is because not all of the gluster cli commands are logged in cmd_history log file.
(In reply to Atin Mukherjee from comment #4) > What all gluster commands were run post upgrade? The reason I am asking all > these questions is because not all of the gluster cli commands are logged in > cmd_history log file. 1. All volume type creation. 2. New peer probe 3. Brick add, remove, replace 4. Volume delete
upstream patch for this bug available: http://review.gluster.org/#/c/12832/
Changing the bug state to POST as the patch is available upstream as seen in comment6
The fix is now available in rhgs-3.1.3 branch, hence moving the state to Modified.
Verification of this bug depends on the Fix of BZ-1321509..
Verified this bug using the build "glusterfs-3.7.9-2". Fix is working good, after log rotate(cmd_history file),next executed commands are populating to the new log file. Moving to verified state.
LGTM :)
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