Description of problem:
for /usr/lib/glusterfs/.unsupported/rhs-nfs_ganesha.sh ip of a node has to be given as input, the IP should be of the same system on which the script is executed.
Presently trying to give IP input as IP of someother node, the script throws error, but the nfs process is started.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1./usr/lib/glusterfs/.unsupported/rhs-nfs_ganesha.sh -l /root/nfs-ganesha/server.log -n NIV_FULL_DEBUG -v dist-rep -i <IP of some other node> -f /usr/lib/glusterfs/.unsupported/nfs-ganesha.conf -o start
[root@rhsauto016 ~]# /usr/lib/glusterfs/.unsupported/rhs-nfs_ganesha.sh -l /root/nfs-ganesha/server.log -n NIV_FULL_DEBUG -v dist-rep -i 10.70.37.4 -f /usr/lib/glusterfs/.unsupported/nfs-ganesha.conf -o start
NFS-ganesha server started.
clnt_create: RPC: Program not registered
[root@rhsauto016 ~]# ps -eaf | grep nfs
root 10629 1 0 10:35 ? 00:00:00 /usr/bin/ganesha.nfsd -f /usr/lib/glusterfs/.unsupported/nfs-ganesha.conf -L /root/nfs-ganesha/server.log -N NIV_FULL_DEBUG -d
root 10704 14606 0 10:39 pts/1 00:00:00 grep nfs
if the IP as input is required of same node then it should not start nfs process when a wrong IP is given.
Fixed in Version and patch URL ?
Fixed in nfs-ganesha-188.8.131.52-5.el6rhs.x86_64 rpms
tested on nfs-ganesha-184.108.40.206-5.el6rhs.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.