Red Hat Bugzilla – Bug 1114574
nfs-ganesha: rpcinfo -p displays running nfs info, even though nfs-ganesha process is stopped
Last modified: 2016-01-27 02:15:40 EST
Description of problem: for stopping nfs-ganesha, we use the command gluster volume set <dist-rep> nfs-ganesha.enable off This stops the nfs-ganesha process, still the rpcinfo -p displays the information about nfs. Hence, even if nfs-ganehsa is stopped from glusterfs point of view, the glusterfs-nfs could not be started. Version-Release number of selected component (if applicable): glusterfs-3.6.0.22-1.el6rhs.x86_64 nfs-ganesha-2.1.0.2-4.el6rhs.x86_64 How reproducible: always Actual results: [root@nfs1 ~]# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 42790 status 100024 1 tcp 59211 status 100003 3 udp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 udp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 49710 mountd 100005 1 tcp 33435 mountd 100005 3 udp 49710 mountd 100005 3 tcp 33435 mountd 100021 4 udp 35307 nlockmgr 100021 4 tcp 34680 nlockmgr 100011 1 udp 875 rquotad 100011 1 tcp 875 rquotad 100011 2 udp 875 rquotad 100011 2 tcp 875 rquotad [root@nfs1 ~]# ps -eaf | grep ganesha root 11829 1906 0 06:12 pts/0 00:00:00 grep ganesha Expected results: rpcinfo should be clear of the nfs information once nfs-ganesha is stopped. Additional info:
This issue is not always seen in our setup. The workaround is to use "rpcinfo -d" to cleanup the ports and is also part of RHS3.0 Documentation for NFS-Ganesha. We will check with the QA setup. Since there is a workaround, we will fix this issue in the next release.
Please review and sign-off edited doc text.
Meghana reviewed the text during online review meeting. Hence removing need_info.
*** This bug has been marked as a duplicate of bug 1227169 ***