Description of problem: ----------------------- While executing 'gluster volume status' command, the following error message was seen, <snip> [2015-06-18 15:16:40.377993] E [glusterd-op-sm.c:251:glusterd_get_txn_opinfo] (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7fc835252fc0] (--> /usr/lib64/glusterfs/3.7.1/xlator/mgmt/glusterd.so(glusterd_get_txn_opinfo+0x197)[0x7fc829c80d67] (--> /usr/lib64/glusterfs/3.7.1/xlator/mgmt/glusterd.so(__glusterd_handle_stage_op+0x1f0)[0x7fc829c611a0] (--> /usr/lib64/glusterfs/3.7.1/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x3f)[0x7fc829c5e53f] (--> /usr/lib64/libglusterfs.so.0(synctask_wrap+0x12)[0x7fc8352935f2] ))))) 0-management: Unable to get transaction opinfo for transaction ID : c1d215cb-2b61-4ad4-828a-643f634a9e98 </snip> Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHEL 6.7 Beta + glusterfs-3.7.1 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Create a volume of any type and start it 2. Execute 'gluster volume status' command 3. Check glusterd logs Actual results: --------------- Error messages as described earlier in the description was seen Expected results: ----------------- There shouldn't be any error messages
I was managing gluster nodes in oVirt, which uses 'gluster volume status' periodically to get the status/health of the gluster node As a result, the error messages as indicated in comment0 gets filled all over the glusterd logs.
*** This bug has been marked as a duplicate of bug 1249461 ***