Red Hat Bugzilla – Bug 865327
glusterd keeps listening on ipv6 interfaces for volumes when using inet familly address
Last modified: 2014-04-17 07:39:12 EDT
Description of problem:
Using the option "transport.address-family inet" does not force volume to listen on ipv4 addresses.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set ipv6 support on interfaces on 2 machine
2. Set ipv6 addresses to your interfaces
3. Use option transport.address-family inet
4. Probe your machines using the ipv4 addresses
5. Create a single volume (with one brick)
6. Check with netstat command that the volume is listening, port 24011 (for example) is listening on tcp6.
tcp6 0 0 :::24011 :::* LISTEN 0 1563400678 17713/glusterfsd
tcp 0 0 0.0.0:24011 0.0.0.0:* LISTEN 0 1563400678 17713/glusterfsd
DISTRIB_DESCRIPTION="Ubuntu 10.04.4 LTS"
iface vlan140 inet static
up ip route add 10.0.0.0/8 via 10.234.68.33
up ip route add 192.168.0.0/16 via 10.234.68.33
iface vlan140 inet6 static
up ip route add 2a01:c940::/40 via 2a01:c940:b6:140::1
More info about this:
I've disabled ipv6 supports, stopped the volume, restarted glusterd, started back the volume and now I've got:
glusterfs 14242 root 10u IPv4 917544705 0t0 TCP *:24009 (LISTEN)
CHANGE: http://review.gluster.org/3889 (glusterfsd can't listen in a specified address) merged in master by Anand Avati (email@example.com)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.