On Tue, Mar 18, 2014 at 1:51 PM, Franco Broi wrote:
>
> Sorry, didn't think to look in the log file, I can see I have bigger
> problems. Last time I saw this was because I had changed an IP address
> but this time all I did was reboot the server. I've checked all the
> files in vols and everything
Sorry, didn't think to look in the log file, I can see I have bigger
problems. Last time I saw this was because I had changed an IP address
but this time all I did was reboot the server. I've checked all the
files in vols and everything looks good.
[2014-03-18 08:09:18.117040] E
[glusterd-store.
The lock is an in-memory structure which isn't persisted. Restarting
should reset the lock. You could possibly reset the lock by gdbing
into the glusterd process.
Since this is happening to you consistently, there is something else
that is wrong. Could you please give more details on your cluster?
Restarted the glusterd daemons on all 4 servers, still the same.
It only and always fails on the same server and it always works on the
other servers.
I had to reboot the server in question this morning, perhaps it's got
itself in a funny state.
Is the lock something that can be examined? And r
This mostly occurs when you run two gluster commands simultaneously.
Gluster uses a lock on each peer to synchronize commands. Any command
which would need to do operations on multiple peers, would first
acquire this lock, and release it after doing the operation. If a
command cannot acquire a lock
What causes this error? And how do I get rid of it?
[root@nas4 ~]# gluster vol status
Another transaction could be in progress. Please try again after sometime.
Looks normal on any other server.
___
Gluster-users mailing list
Gluster-users@gluster.or
