On 03/08/2013 08:45 PM, Nux! wrote:
Hello,
After the recent upgrade to 3.4 alpha 2 blew up in my face, I started
from scratch, removing all packages, deleting /var/lib/gluster* and
formatting the bricks partition.
First problem: Enabling quota on a new empty volume fails:
[root@2216 ~]# gluster volume quota internalad enable
Quota command failed
BUT, info shows quota is on:
gluster volume info internalad
Volume Name: internalad
Type: Replicate
Volume ID: bfdedbae-c990-4e2f-b0d6-ab35ad8e8a66
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 2216.storage.domeniu.net:/bricks/internalad
Brick2: 1631.storage.domeniu.net:/bricks/internalad
Options Reconfigured:
features.quota: on
Can you please provide the o/p of:
gluster system:: fsm log <peername>
Do you have any firewall rules on the nodes of the cluster? Connection
refused errors seem to indicate so.
-Vijay
What I see in the logs is:
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log
[2013-03-07 12:39:13.457127] E [socket.c:2767:socket_connect]
0-management: connection attempt failed (Connection refused)
[2013-03-07 12:39:16.457511] E [socket.c:2767:socket_connect]
0-management: connection attempt failed (Connection refused)
[2013-03-07 12:39:19.457873] E [socket.c:2767:socket_connect]
0-management: connection attempt failed (Connection refused)
[2013-03-07 12:39:22.458293] E [socket.c:2767:socket_connect]
0-management: connection attempt failed (Connection refused)
[2013-03-07 12:39:25.458715] E [socket.c:2767:socket_connect]
0-management: connection attempt failed (Connection refused)
[2013-03-07 12:39:28.459122] E [socket.c:2767:socket_connect]
0-management: connection attempt failed (Connection refused)
(and goes on and on)
