That seemed to be it, having 'auth.allow = all' lets all 3.9 clients in, updating it to 'auth.allow = *' lets 3.10 clients connect as well. Thanks, Andrew Kester The Storehouse https://sthse.co On 03/14/2017 12:03 AM, Atin Mukherjee wrote: > "gluster volume set <volname> auth.allow all" looks to be the culprit. > However I am just wondering if the same option is set for a volume in > 3.9.1 how is it working for you. This is not a regression. I just tested > it in both 3.10 & 3.9.1 and the mount doesn't succeed. Is there any > specific reason you want to mark 'auth.allow = all' which actually is > equivalent of having this option reset. auth.allow expects certain IPs > which are allowed to be authenticated. When this option is set to 'all' > Gluster doesn't handle this keyword specially and assume it's mentioned > as one of the IP/Host & then the mount request fails with authentication > failure. > > On Mon, Mar 13, 2017 at 9:10 PM, Atin Mukherjee <amukherj@xxxxxxxxxx > <mailto:amukherj@xxxxxxxxxx>> wrote: > > Can you please mention the client version of the mount which you > were unable to mount? Did you upgrade from 3.9 yo 3.10? Once I have > these informations, I'll try to reproduce this issue and get back. > > On Fri, 10 Mar 2017 at 22:42, Andrew Kester <aikester@xxxxxxxxxxxx > <mailto:aikester@xxxxxxxxxxxx>> wrote: > > I have a Gluster volume that I'm unable to mount from some > clients. The client process on the servers are able to mount > the volume without issue, but other clients are unable to. All > nodes are running Debian 8 and Gluster 3.10.0. > > I see a couple lines in the log that have "Using Program > GlusterFS 3.3", this is a pretty old volume definition but I've > updated the operating mode as it's been upgraded, setting it to > 31000 with this most recent update. Could that be the issue? > > Any help or guidance is appreciated. Thanks! > > glusterfs --version: > glusterfs 3.10.0 > Repository revision: git://git.gluster.org/glusterfs.git > <http://git.gluster.org/glusterfs.git> > Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/> > GlusterFS comes with ABSOLUTELY NO WARRANTY. > It is licensed to you under your choice of the GNU Lesser > General Public License, version 3 or any later version (LGPLv3 > or later), or the GNU General Public License, version 2 (GPLv2), > in all cases as published by the Free Software Foundation. > > Volume Info: > Volume Name: gv0 > Type: Replicate > Volume ID: ---- > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: pegasus.sthse.co:/mnt/brick > Brick2: atlantia.sthse.co:/mnt/brick > Options Reconfigured: > server.allow-insecure: on > transport.address-family: inet > nfs.disable: on > server.root-squash: off > auth.allow: all > features.scrub-freq: weekly > features.scrub-throttle: normal > features.scrub: Active > features.bitrot: on > performance.io-thread-count: 16 > > Log entries on clients: > [2017-03-10 16:43:13.659555] I > [rpc-clnt.c:1964:rpc_clnt_reconfig] 0-gv0-client-2: changing > port to 49153 (from 0) > [2017-03-10 16:43:13.659672] I [MSGID: 114057] > [client-handshake.c:1451:select_server_supported_programs] > 0-gv0-client-1: Using Program GlusterFS 3.3, Num (1298437), > Version (330) > [2017-03-10 16:43:13.660189] I [MSGID: 114057] > [client-handshake.c:1451:select_server_supported_programs] > 0-gv0-client-2: Using Program GlusterFS 3.3, Num (1298437), > Version (330) > [2017-03-10 16:43:13.660192] W [MSGID: 114043] > [client-handshake.c:1105:client_setvolume_cbk] 0-gv0-client-1: > failed to set the volume [Permission denied] > [2017-03-10 16:43:13.660249] W [MSGID: 114007] > [client-handshake.c:1134:client_setvolume_cbk] 0-gv0-client-1: > failed to get 'process-uuid' from reply dict [Invalid argument] > [2017-03-10 16:43:13.660266] E [MSGID: 114044] > [client-handshake.c:1140:client_setvolume_cbk] 0-gv0-client-1: > SETVOLUME on remote-host failed [Permission denied] > [2017-03-10 16:43:13.660282] I [MSGID: 114049] > [client-handshake.c:1243:client_setvolume_cbk] 0-gv0-client-1: > sending AUTH_FAILED event > [2017-03-10 16:43:13.660321] E [fuse-bridge.c:5322:notify] > 0-fuse: Server authenication failed. Shutting down. > [2017-03-10 16:43:13.660345] I [fuse-bridge.c:5802:fini] 0-fuse: > Unmounting '/gv0'. > [2017-03-10 16:43:13.660814] W [MSGID: 114043] > [client-handshake.c:1105:client_setvolume_cbk] 0-gv0-client-2: > failed to set the volume [Permission denied] > [2017-03-10 16:43:13.660850] W [MSGID: 114007] > [client-handshake.c:1134:client_setvolume_cbk] 0-gv0-client-2: > failed to get 'process-uuid' from reply dict [Invalid argument] > [2017-03-10 16:43:13.660869] E [MSGID: 114044] > [client-handshake.c:1140:client_setvolume_cbk] 0-gv0-client-2: > SETVOLUME on remote-host failed [Permission denied] > [2017-03-10 16:43:13.660884] I [MSGID: 114049] > [client-handshake.c:1243:client_setvolume_cbk] 0-gv0-client-2: > sending AUTH_FAILED event > [2017-03-10 16:43:13.673681] E [fuse-bridge.c:5322:notify] > 0-fuse: Server authenication failed. Shutting down. > [2017-03-10 16:43:13.673997] W > [glusterfsd.c:1329:cleanup_and_exit] > (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) > [0x7f81c866e064] > -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) > [0x56191158cdb5] -->/usr/sbin/glusterfs(cleanup_and_exit+0x57) > [0x56191158cc27] ) 0-: received signum (15), shutting down > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx> > http://lists.gluster.org/mailman/listinfo/gluster-users > <http://lists.gluster.org/mailman/listinfo/gluster-users> > > -- > - Atin (atinm) > > > > > -- > > ~ Atin (atinm) _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
