This issue is now fixed in 3.10.1. On Tue, 21 Mar 2017 at 19:07, David Chin <teew...@hotmail.com> wrote:
> I'm facing the same issue as well. I'm running the version 3.10.0-2 for > both server and client. > > Works fine when the client and server are on the same machine. > > > I did a telnet to the opened port related to gluster from the client-only > instances to server: (eg : > > > # netstat -antop | grep gluster | grep LISTEN > tcp 0 0 0.0.0.0:49153 0.0.0.0:* > LISTEN 19443/glusterfsd off (0.00/0/0) > tcp 0 0 0.0.0.0:24007 0.0.0.0:* > LISTEN 19288/glusterd off (0.00/0/0) > > > I'm able to establish a connection with all of them, so firewall is not > the cause here (my firewall rules are empty anyway). > > > Only after I set "auth.allow = *", then only the client-only instance are > able to connect, but this would have severe security implications. > > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users -- - Atin (atinm)
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
