[Gluster-users] Gluster client can't connect to Gluster volume
David Coulson
david at davidcoulson.net
Sat May 5 17:46:17 UTC 2012
There's probably not a whole lot of 'fixing' since the two versions are
so different.
You can tell the package maintainer to make a 3.2.6 build. That'll help.
On 5/5/12 1:43 PM, Eric wrote:
> Thanks, David:
>
> But I'd rather see if I can fix the problem with the Mageia client
> (|glusterfs-client-3.0.0-2.mga1|):
>
> * This will allow me to file a bug report with the package
> maintainer (if necessary).
> * I already know that the systems that have Gluster 3.2.6 from
> source [i.e., the storage nodes] are able to mount the volume.
> * I'd rather keep my daily-driver (i.e., the host system) 100% Mageia.
>
> Eric Pretorious
> Truckee, CA
>
> ------------------------------------------------------------------------
> *From:* David Coulson <david at davidcoulson.net>
> *To:* Eric <epretorious at yahoo.com>
> *Cc:* "gluster-users at gluster.org" <gluster-users at gluster.org>
> *Sent:* Saturday, May 5, 2012 9:16 AM
> *Subject:* Re: [Gluster-users] Gluster client can't connect to
> Gluster volume
>
> That's way old documentation.
>
> Start by installing 3.2.6 on your client and see if it works then.
> I don't think anyone expects 3.2 and 3.0 to work correctly.
>
> On 5/5/12 12:09 PM, Eric wrote:
>> Thanks, David:
>>
>> Yes...
>>
>> * iptables has been disabled on all three systems.
>> * SELinux is set to permissive on the two systems that employ
>> it - the two CentOS nodes.
>> * Port #6996 is referenced in the Troubleshooting section of
>> the Gluster User Guide
>> <http://www.gluster.org/community/documentation/index.php/User_Guide#Troubleshooting>.
>>
>> FWIW: All of this except the SELinux question is already
>> documented in my post on the Mageia Forum
>> <https://forums.mageia.org/en/viewtopic.php?f=7&t=2358&p=17517>.
>>
>> Eric Pretorious
>> Truckee, CA
>>
>> ------------------------------------------------------------------------
>> *From:* David Coulson <david at davidcoulson.net>
>> <mailto:david at davidcoulson.net>
>> *To:* Eric <epretorious at yahoo.com>
>> <mailto:epretorious at yahoo.com>
>> *Cc:* "gluster-users at gluster.org"
>> <mailto:gluster-users at gluster.org>
>> <gluster-users at gluster.org> <mailto:gluster-users at gluster.org>
>> *Sent:* Saturday, May 5, 2012 5:44 AM
>> *Subject:* Re: [Gluster-users] Gluster client can't connect
>> to Gluster volume
>>
>> Do you have any firewall rules enabled? I'd start by
>> disabling iptables (or at least setting everything to ACCEPT)
>> and as someone else suggested setting selinux to
>> permissive/disabled.
>>
>> Why are your nodes and client using different versions of
>> Gluster? Why not just use the 3.2.6 version for everything?
>> Also, I'm not sure where port 6996 comes from - Gluster uses
>> 24007 for it's core communications and ports above that for
>> individual bricks.
>>
>> David
>>
>> On 5/5/12 12:27 AM, Eric wrote:
>>> Hi, All:
>>>
>>> I've built a Gluster-based storage cluster on a pair of
>>> CentOS 5.7 (i386) VM's. The nodes are using Gluster 3.2.6
>>> (from source) and the host is using Gluster 3.0.0 (from the
>>> Mageia package repositories):
>>>
>>> |[eric at node1 ~]$ sudo /usr/local/sbin/gluster --version
>>> glusterfs 3.2.6 built on May 3 2012 15:53:02
>>>
>>> ||[eric at localhost ~]$ rpm -qa | grep glusterfs|
>>> |glusterfs-common-3.0.0-2.mga1|
>>> |glusterfs-client-3.0.0-2.mga1|
>>> |glusterfs-server-3.0.0-2.mga1|
>>> |libglusterfs0-3.0.0-2.mga1|
>>>
>>> None of the systems (i.e., neither the two storage nodes nor
>>> the client) can connect to Port 6996 of the cluster
>>> (node1.example.com <http://node1.example.com> &
>>> node2.example.com <http://node2.example.com>) but the two
>>> storage nodes can mount the shared volume using the Gluster
>>> helper and/or NFS:
>>>
>>> |[eric at node1 ~]$ sudo /sbin/lsmod | grep fuse
>>>
>>> [eric at node1 ~]$ sudo /sbin/modprobe fuse
>>>
>>> [eric at node1 ~]$ sudo /sbin/lsmod | grep fuse
>>> fuse 49237 0
>>>
>>> [eric at node1 ~]$ sudo mount -t glusterfs node1:/mirror-1 /mnt
>>>
>>> [eric at node1 ~]$ sudo grep gluster /etc/mtab
>>> glusterfs#node1:/mirror-1 /mnt fuse
>>> rw,allow_other,default_permissions,max_read=131072 0 0|
>>>
>>> ...but the host system is only able to connect using NFS:
>>>
>>> |[eric at localhost ~]$ sudo glusterfs --debug -f
>>> /tmp/glusterfs.vol /mnt
>>> [2012-05-04 19:09:09] D [glusterfsd.c:424:_get_specfp]
>>> glusterfs: loading volume file /tmp/glusterfs.vol
>>> ================================================================================
>>> Version : glusterfs 3.0.0 built on Apr 10 2011 19:12:54
>>> git: 2.0.1-886-g8379edd
>>> Starting Time: 2012-05-04 19:09:09
>>> Command line : glusterfs --debug -f /tmp/glusterfs.vol /mnt
>>> PID : 30159
>>> System name : Linux
>>> Nodename : localhost.localdomain
>>> Kernel Release : 2.6.38.8-desktop586-10.mga
>>> Hardware Identifier: i686
>>>
>>> Given volfile:
>>> +------------------------------------------------------------------------------+
>>> 1: volume mirror-1
>>> 2: type protocol/client
>>> 3: option transport-type tcp
>>> 4: option remote-host node1.example.com
>>> 5: option remote-subvolume mirror-1
>>> 6: end-volume
>>> +------------------------------------------------------------------------------+
>>> [2012-05-04 19:09:09] D [glusterfsd.c:1335:main] glusterfs:
>>> running in pid 30159
>>> [2012-05-04 19:09:09] D [client-protocol.c:6581:init]
>>> mirror-1: defaulting frame-timeout to 30mins
>>> [2012-05-04 19:09:09] D [client-protocol.c:6592:init]
>>> mirror-1: defaulting ping-timeout to 42
>>> [2012-05-04 19:09:09] D [transport.c:145:transport_load]
>>> transport: attempt to load file
>>> /usr/lib/glusterfs/3.0.0/transport/socket.so
>>> [2012-05-04 19:09:09] D [transport.c:145:transport_load]
>>> transport: attempt to load file
>>> /usr/lib/glusterfs/3.0.0/transport/socket.so
>>> [2012-05-04 19:09:09] D [client-protocol.c:7005:notify]
>>> mirror-1: got GF_EVENT_PARENT_UP, attempting connect on
>>> transport
>>> [2012-05-04 19:09:09] D [client-protocol.c:7005:notify]
>>> mirror-1: got GF_EVENT_PARENT_UP, attempting connect on
>>> transport
>>> [2012-05-04 19:09:09] D [client-protocol.c:7005:notify]
>>> mirror-1: got GF_EVENT_PARENT_UP, attempting connect on
>>> transport
>>> [2012-05-04 19:09:09] D [client-protocol.c:7005:notify]
>>> mirror-1: got GF_EVENT_PARENT_UP, attempting connect on
>>> transport
>>> [2012-05-04 19:09:09] N [glusterfsd.c:1361:main] glusterfs:
>>> Successfully started
>>> [2012-05-04 19:09:09] E [socket.c:760:socket_connect_finish]
>>> mirror-1: connection to failed (Connection refused)
>>> [2012-05-04 19:09:09] D
>>> [fuse-bridge.c:3079:fuse_thread_proc] fuse:
>>> pthread_cond_timedout returned non zero value ret: 0 errno: 0
>>> [2012-05-04 19:09:09] N [fuse-bridge.c:2931:fuse_init]
>>> glusterfs-fuse: FUSE inited with protocol versions:
>>> glusterfs 7.13 kernel 7.16
>>> [2012-05-04 19:09:09] E [socket.c:760:socket_connect_finish]
>>> mirror-1: connection to failed (Connection refused)|
>>>
>>> I've read through the Troubleshooting section of the Gluster
>>> Administration Guide
>>> <http://download.gluster.com/pub/gluster/glusterfs/3.2/Documentation/AG/html/chap-Administration_Guide-Troubleshooting.html>
>>> and the Gluster User Guide
>>> <http://www.gluster.org/community/documentation/index.php/User_Guide#Troubleshooting>but
>>> can't seem to resolve the problem. (See my post on the
>>> Mageia Forum
>>> <https://forums.mageia.org/en/viewtopic.php?f=7&t=2358&p=17517>
>>> for all the troubleshooting details:
>>> https://forums.mageia.org/en/viewtopic.php?f=7&t=2358&p=17517 <https://forums.mageia.org/en/viewtopic.php?f=7&t=2358&p=17517>)
>>>
>>>
>>> What might be causing this?
>>>
>>> TIA,
>>> Eric Pretorious
>>> Truckee, CA
>>>
>>> https://forums.mageia.org/en/viewtopic.php?f=7&t=2358&p=17517 <https://forums.mageia.org/en/viewtopic.php?f=7&t=2358&p=17517>
>>>
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org <mailto:Gluster-users at gluster.org>
>>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>>
>>
>
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120505/099e01bc/attachment.html>
More information about the Gluster-users
mailing list