[NFS-Ganesha-Support] Ganesha 3.2 connection issue

29 May 2020

      Hi. I just built ganesha 3.2, and am trying to set up a PROXY mount. I’m trying to resolve the following error. My server NFSD is up, running, and rpcinfo -p shows the right ports etc.

nfs-ganesha-64067[pxy_rcv_thread] pxy_rpc_recv :FSAL :CRIT :Cannot connect to server 10.151.27.27:2049:2049

My ganesh.conf file is as follows. Please advise on how to proceed. Thanks.

-Jeff

## These are core parameters that affect Ganesha as a whole.
NFS_CORE_PARAM {
                ## Allow NFSv3 to mount paths with the Pseudo path, the same as NFSv4,
                ## instead of using the physical paths.
                mount_path_pseudo = true;

                ## Configure the protocols that Ganesha will listen for.  This is a hard
                ## limit, as this list determines which sockets are opened.  This list
                ## can be restricted per export, but cannot be expanded.
                Protocols = 4;
}

## Configure NFSv4
NFSv4 {
                Alow_Numeric_Owners = true;
                Only_Numeric_Owners = true;
}

## These are defaults for exports.  They can be overridden per-export.
EXPORT_DEFAULTS {
                ## Access type for clients.  Default is None, so some access must be
                ## given either here or in the export itself.
                Access_Type = RW;
}

## Configure settings for the object handle cache
CACHEINODE {
                ## The point at which object cache entries will start being reused.
                Entries_HWMark = 100000;
}

## Configure exports
EXPORT
{
                ## Export Id (mandatory, each EXPORT must have a unique Export_Id)
                Export_Id = 1111;

                ## Exported path (mandatory)
                Path = /nobackupp16/jcbecker;

                ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true)
                Pseudo = /foo;

                ## Restrict the protocols that may use this export.  This cannot allow
                ## access that is denied in NFS_CORE_PARAM.
                #Protocols = 3,4;

                ## Access type for clients.  Default is None, so some access must be
                ## given. It can be here, in the EXPORT_DEFAULTS, or in a CLIENT block
                Access_Type = RW;

                ## Whether to squash various users.
                Squash = root_squash;

                ## Allowed security types for this export
                #Sectype = sys,krb5,krb5i,krb5p;

                ## Exporting FSAL
                FSAL {
                                Name = PROXY;
                                Srv_Addr = 10.151.27.27;
                }
                CLIENT
                {
                                Clients = 10.151.26.24;
                }

}
## Configure logging.  Default is to log to Syslog.  Basic logging can also be
## configured from the command line
LOG {
                ## Default log level for all components
                Default_Log_Level = INFO;

                ## Configure per-component log levels.
                Components {
                                FSAL = INFO;
                                NFS4 = EVENT;
                }

                ## Where to log
                Facility {
                                name = FILE;
                                destination = "/mnt/nbnfs2/jcbecker/reexporter/var/log/ganesha.log";
                                enable = active;
                }
}

[NFS-Ganesha-Support] Ganesha 3.2 connection issue

Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]