[Gluster-users] Glusterfs denied mount

Lalatendu Mohanty lmohanty at redhat.com
Wed Nov 20 13:04:07 UTC 2013


On 11/19/2013 06:04 PM, French Teddy wrote:
> I'm using GlusterFS 3.3.2. Two servers, a brick on each one. The Volume
> is "ARCHIVE80"
>
> I can mount the volume on Server2; if I touch a new file, it appears
> inside the brick on Server1.
>
> However, if I try to mount the volume on Server1, I have an error:
>
>      Mount failed. Please check the log file for more details.
>
> The log gives:
>
>      [2013-11-11 03:33:59.796431] I [rpc-clnt.c:1654:rpc_clnt_reconfig]
> 0-ARCHIVE80-client-0: changing port to 24011 (from 0)
>      [2013-11-11 03:33:59.796810] I [rpc-clnt.c:1654:rpc_clnt_reconfig]
> 0-ARCHIVE80-client-1: changing port to 24009 (from 0)
>      [2013-11-11 03:34:03.794182] I
> [client-handshake.c:1614:select_server_supported_programs]
> 0-ARCHIVE80-client-0: Using Program GlusterFS 3.3.2, Num (1298437),
> Version (330)
>      [2013-11-11 03:34:03.794387] W
> [client-handshake.c:1320:client_setvolume_cbk] 0-ARCHIVE80-client-0:
> failed to set the volume (Permission denied)
>      [2013-11-11 03:34:03.794407] W
> [client-handshake.c:1346:client_setvolume_cbk] 0-ARCHIVE80-client-0:
> failed to get 'process-uuid' from reply dict
>      [2013-11-11 03:34:03.794418] E
> [client-handshake.c:1352:client_setvolume_cbk] 0-ARCHIVE80-client-0:
> SETVOLUME on remote-host failed: Authentication failed
>      [2013-11-11 03:34:03.794426] I
> [client-handshake.c:1437:client_setvolume_cbk] 0-ARCHIVE80-client-0:
> sending AUTH_FAILED event
>      [2013-11-11 03:34:03.794443] E [fuse-bridge.c:4256:notify] 0-fuse:
> Server authenication failed. Shutting down.
>
> How comes I can mount on one server and not on the other one???
>
>
> TIA
>
> greg
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
Which OS/distribution you are using for deploying gluster? If you are 
using CentOS , plz disable the selinux and make sure your iptable rule 
is not blocking the gluster process communication.

Thanks,
Lala



More information about the Gluster-users mailing list