Description of problem: We're getting warnings like this: [2018-08-13 09:38:45.428086] W [socket.c:3352:socket_connect] 0-glustershd: Error disabling sockopt IPV6_V6ONLY: "Operation not supported" Therefore glusterfs listen on both IPv6 and IPv6 Glusterfs compiled with --with-ipv6-default. And the server has IPv6 address. Actually glusterfs already use socket with v6only:0: ~ $ sudo ss -ltnep | grep 24007 LISTEN 0 10 :::24007 :::* users:(("glusterd",pid=13103,fd=10)) ino:317954466 sk:f8 v6only:0 <-> ~ $ sudo sysctl net.ipv6.bindv6only net.ipv6.bindv6only = 0 Version-Release number of selected component (if applicable): 4.1.2 Steps to Reproduce: 1. assign IPv6 address for network interface 2. compile glusterfs with --with-ipv6-default option 3. setup glusterfs cluster Actual results: Warnings about disabling IPV6_V6ONLY for socket Expected results: Disable IPV6_V6ONLY for socket without errors
We did few fixes for IPv6 in glusterfs-5.x and glusterfs-6.x releases. Can you confirm if higher version fixed these issues?
Looks like issue still persists in v5.5: in cli.log and heal.log: /var/log/glusterfs/cli.log:[2019-06-16 00:29:26.797461] W [socket.c:3367:socket_connect] 0-glusterfs: Error disabling sockopt IPV6_V6ONLY: "Operation not supported" /var/log/glusterfs/glfsheal-st.log:[2019-06-16 00:31:53.930463] W [socket.c:3367:socket_connect] 0-gfapi: Error disabling sockopt IPV6_V6ONLY: "Operation not supported"
Is anyone looking at this?
REVIEW: https://review.gluster.org/23383 (transport: fix error not supported for ipv6) posted (#1) for review on master by Rinku Kothiya
This bug is moved to https://github.com/gluster/glusterfs/issues/1068, and will be tracked there from now on. Visit GitHub issues URL for further details
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days