Bug 1249437

Summary: Errors when issuing gluster volume status command
Product: [Community] GlusterFS Reporter: Con Tassios <ct>
Component: glusterdAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.3CC: amukherj, bugs, ct, gluster-bugs, pkarampu
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 03:52:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
etc-glusterfs-glusterd.vol.log 1/3
none
etc-glusterfs-glusterd.vol.log 2/3
none
etc-glusterfs-glusterd.vol.log 3/3 none

Description Con Tassios 2015-08-03 01:33:18 UTC
Since 3.7.3 I get these errors in etc-glusterfs-glusterd.vol.log when running the command : gluster volume status

[2015-08-03 01:05:01.047641] E [glusterd-op-sm.c:252:glusterd_get_txn_opinfo] (-->/usr/lib64/glusterfs/3.7.3/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x30) [0x7f2090e43970] -->/usr/lib64/glusterfs/3.7.3/xlator/mgmt/glusterd.so(__glusterd_handle_stage_op+0x1be) [0x7f2090e455ee] -->/usr/lib64/glusterfs/3.7.3/xlator/mgmt/glusterd.so(glusterd_get_txn_opinfo+0x147) [0x7f2090e566e7] ) 0-management: Unable to get transaction opinfo for transaction ID : 502232c9-36f6-4a9f-bd7f-fe16a63ba44a [Permission denied]

Comment 1 Pranith Kumar K 2015-08-04 12:28:29 UTC
hi Con,
       Could you please add the whole etc-glusterfs-glusterd.vol.log from all the machines in cluster? That should help in finding more about the bug.

Pranith

Comment 2 Con Tassios 2015-08-04 23:41:14 UTC
Created attachment 1059264 [details]
etc-glusterfs-glusterd.vol.log 1/3

Comment 3 Con Tassios 2015-08-04 23:42:07 UTC
Created attachment 1059265 [details]
etc-glusterfs-glusterd.vol.log 2/3

Comment 4 Con Tassios 2015-08-04 23:42:40 UTC
Created attachment 1059266 [details]
etc-glusterfs-glusterd.vol.log 3/3

Comment 5 Con Tassios 2015-08-04 23:43:24 UTC
Logs have been attached for each of 3 cluster members

Comment 6 Atin Mukherjee 2015-08-05 03:52:05 UTC
Functionality wise there is no impact as in the first volume status rpc volume name is not available and for which the txn id is never set and hence the log. BZ 1249461 also tracks the same issue and we already have a patch which is merged mainline and waiting to be backported in 3.7. Given that, I am closing this bug as a duplicate of 1249461

*** This bug has been marked as a duplicate of bug 1249461 ***