Gluster users - Jun 2015 - Unable to get lock for uuid peers

Hi all,
I two servers with 3.7.1 and have the same problem of this issue:
http://comments.gmane.org/gmane.comp.file-systems.gluster.user/20693

My servers packages:
# rpm -qa | grep gluster | sort
glusterfs-3.7.1-1.el6.x86_64
glusterfs-api-3.7.1-1.el6.x86_64
glusterfs-cli-3.7.1-1.el6.x86_64
glusterfs-client-xlators-3.7.1-1.el6.x86_64
glusterfs-fuse-3.7.1-1.el6.x86_64
glusterfs-geo-replication-3.7.1-1.el6.x86_64
glusterfs-libs-3.7.1-1.el6.x86_64
glusterfs-server-3.7.1-1.el6.x86_64

Command:
# gluster volume status
Another transaction is in progress. Please try again after sometime.


In /var/log/gluster/etc-glusterfs-glusterd.vol.log I found:

[2015-06-09 16:12:38.949842] E [glusterd-utils.c:164:glusterd_lock]
0-management: Unable to get lock for uuid:
99a41a2a-2ce5-461c-aec0-510bd5b37bf2, lock held by:
04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c
[2015-06-09 16:12:38.949864] E [glusterd-syncop.c:1766:gd_sync_task_begin]
0-management: Unable to acquire lock

I check the files:
 From server 1:
# cat /var/lib/glusterd/peers/04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c
uuid=04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c
state=3
hostname1=192.168.61.101

 From server 2:
# cat /var/lib/glusterd/peers/99a41a2a-2ce5-461c-aec0-510bd5b37bf2
uuid=99a41a2a-2ce5-461c-aec0-510bd5b37bf2
state=3
hostname1=192.168.61.100

And they seems correct.

Any hint?

Cheers
Sergio

> Hi all,
> I two servers with 3.7.1 and have the same problem of this issue:
> http://comments.gmane.org/gmane.comp.file-systems.gluster.user/20693
> 
> My servers packages:
> # rpm -qa | grep gluster | sort
> glusterfs-3.7.1-1.el6.x86_64
> glusterfs-api-3.7.1-1.el6.x86_64
> glusterfs-cli-3.7.1-1.el6.x86_64
> glusterfs-client-xlators-3.7.1-1.el6.x86_64
> glusterfs-fuse-3.7.1-1.el6.x86_64
> glusterfs-geo-replication-3.7.1-1.el6.x86_64
> glusterfs-libs-3.7.1-1.el6.x86_64
> glusterfs-server-3.7.1-1.el6.x86_64
> 
> Command:
> # gluster volume status
> Another transaction is in progress. Please try again after sometime.
> 
> 
> In /var/log/gluster/etc-glusterfs-glusterd.vol.log I found:
> 
> [2015-06-09 16:12:38.949842] E [glusterd-utils.c:164:glusterd_lock]
> 0-management: Unable to get lock for uuid:
> 99a41a2a-2ce5-461c-aec0-510bd5b37bf2, lock held by:
> 04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c
> [2015-06-09 16:12:38.949864] E [glusterd-syncop.c:1766:gd_sync_task_begin]
> 0-management: Unable to acquire lock
> 
> I check the files:
>  From server 1:
> # cat /var/lib/glusterd/peers/04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c
> uuid=04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c
> state=3
> hostname1=192.168.61.101
> 
>  From server 2:
> # cat /var/lib/glusterd/peers/99a41a2a-2ce5-461c-aec0-510bd5b37bf2
> uuid=99a41a2a-2ce5-461c-aec0-510bd5b37bf2
> state=3
> hostname1=192.168.61.100
Could you attach the complete glusterd log file and cmd-history.log
file under /var/log/glusterfs directory? Could you provide a more
detailed listing of things you did before hitting this issue?