We had seen a similar issue and Rajesh has provided a detailed explanation on why at [1]. I'd suggest you to not to change glusterd.vol but execute "gluster volume set <volname> transport.address-family inet" to allow Gluster to listen on IPv4 by default.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1411270#c16
--
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1411270#c16
On Thu, Feb 9, 2017 at 4:07 PM, Benedikt Schindler <benedikt.schindler@xxxxxxxxx> wrote:
Hi,
i have two servers. Both are IPv4 and IPv6 capable.
I installed everything with the defautl values. Creating the cluster worked
fine.
Also creating and starting the volume.
Now, i try to mount the volume. And the mounting fails because the mount
command tries to connect via IPv6.
But GlusterFS is only listening on IPv4.
So I tried to add this line to glusterd.vol
"option transport.address-family inet6"
After that glusterd only listens on IPv6 but it doesn't listen anymore on
IPv4.
But I still have IPv4 only clients that need to mount the volume.
So, I dind't find any documentation on the glusterd.vol file.
(I only found a mail in the maillingslist from the year 2014 who requested a
documentation)
I tried to put something in it like "option transport.address-family inet
inet6" , but then the server didn't start.
So here are my two questions:
1) Is there a way to listen on IPv4 and IPv6 connections? (I mean it is
2017)
2) Could I tell the mount.glusterfs command to use IPv4 ?
Oh, sorry almost forgot:
OS: OpenSuSe Tumbleweed
Kernel: 4.9.7-1-default
GlusterFS: 3.9.1-100.1
(obs://build.opensuse.org/home:kkeithleatredhat )
Best regards
Benedikt Schindler
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
--
~ Atin (atinm)
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
