[Gluster-users] nfs setup

[Niels de Vos]

On Thu, Oct 13, 2016 at 02:37:33PM +1300, Thing wrote:
> Hi,
> 
> I have a 3 node gluster setup running with one brick exported,   /gv0
> 
> Centos 7
> 
> ============
> [root at glusterp1 ganesha]# rpm -aq |grep gluster
> glusterfs-client-xlators-3.8.4-1.el7.x86_64
> nfs-ganesha-gluster-2.3.3-1.el7.x86_64
> glusterfs-3.8.4-1.el7.x86_64
> glusterfs-cli-3.8.4-1.el7.x86_64
> glusterfs-api-3.8.4-1.el7.x86_64
> glusterfs-server-3.8.4-1.el7.x86_64
> glusterfs-fuse-3.8.4-1.el7.x86_64
> glusterfs-ganesha-3.8.4-1.el7.x86_64
> centos-release-gluster38-1.0-1.el7.centos.noarch
> glusterfs-libs-3.8.4-1.el7.x86_64
> [root at glusterp1 ganesha]#
> ============
> 
> I am trying to setup NFS but failing,
> 
> So on node1 (glusterp1)  after setting up ganesha I get,
> 
> ==========
> [root at glusterp1 ganesha]# service nfs-ganesha restart
> Redirecting to /bin/systemctl restart  nfs-ganesha.service
> [root at glusterp1 ganesha]# showmount -e localhost
> Export list for localhost:
> /gv0 (everyone)
> ==========
> 
> However for the client showmount -e fails and does a mount,
> 
> ==========
> root at warlocke:/etc/bind# showmount -e glusterp1.graywitch.co.nz
> clnt_create: RPC: Port mapper failure - Timed out

This looks like a firewall problem. Note that NFS uses the portmapper on
the NFS-server (rpcbind service, port 111 tcp+udp). This is not strictly
required for NFSv4, but tools like showmount depend on it.

Have you tried mounting the export from "warlocke"?

The rest of your configuration looks ok after a first glance.

HTH,
Niels


> root at warlocke:/etc/bind#
> ==========
> 
> My config is,
> 
> ==========
> [root at glusterp1 ganesha]# pwd
> /etc/ganesha
> [root at glusterp1 ganesha]# more ganesha.conf
> ###################################################
> #
> # EXPORT
> #
> # To function, all that is required is an EXPORT
> #
> # Define the absolute minimal export
> #
> ###################################################
> 
> EXPORT
> {
>     # Export Id (mandatory, each EXPORT must have a unique Export_Id)
>     Export_Id = 1;
> 
>     # Exported path (mandatory)
>     Path = /gv0;
>     #Path = /nonexistant;
> 
>     # Pseudo Path (required for NFS v4)
>     Pseudo = /gv0;
> 
>     #ssj
>     #allow root access
>     Squash = No_Root_squash;
>         SecType = "sys";
>     #ssj finish
> 
>     # Required for access (default is None)
>     # Could use CLIENT blocks instead
>     Access_Type = RW;
> 
>     # Exporting FSAL
>     FSAL {
>         Name = GLUSTER;
>                 hostname = 192.168.1.31;
>         volume = "gv0";
>     }
> }
> [root at glusterp1 ganesha]#
> ========
> 
> So what is wrong here please?

> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20161013/cd623baa/attachment.sig>