[Bugs] [Bug 1213304] nfs-ganesha: using features.enable command the nfs-ganesha process does come up on all four nodes

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1213304



--- Comment #5 from Saurabh <saujain at redhat.com> ---
Putting the response as per the conversation we had yesterday,

"1. In general, there is the issue with rpcbind which we have seen
yesterday. For that there is a 7.1 BZ which unfortunately has not been
opened for 6.6/6.x. I am not sure if it is too late for that but we need
to see. I sent a quick note to Sayan to see what he has to say. Will
need to wait for his inputs.

     But in general there is the ugly workaround of removing the state
associated with rpcbind (especially as it seems to be started with
rpcbind -w) :
     - on RHEL 7.x we need to remove the rpcbind.socket file which
contains the info
     - on RHEL 6.6 after digging around on Saurabh's machine, I believe
the file to delete is /var/cache/rpcbind/* (there are 2 .xdr files in there)

If nothing, this should serve as a possible workaround for us (ugly as
it is).

2. ganesha repeatedly fails to start on nfs1 and I think now that the
reason is that there is someone listening on port 2049 still. I think
the issue happened after the reboots yesterday when someone was
listening on port 2049 preventing ganesha from binding to tcp 2049.

- So first I removed the existing /var/run/ganesha pid.

- next clear rpcbind state by rm -rf /var/cache/rpcbind/*



What I see with the useful -tulpn option is:

[root at nfs1 ~]# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign
Address             State       PID/Program name
tcp        0      0 0.0.0.0:853 0.0.0.0:*                   LISTEN      
1518/glusterfs
tcp        0      0 0.0.0.0:22 0.0.0.0:*                   LISTEN      
1918/sshd
tcp        0      0 127.0.0.1:25 0.0.0.0:*                   LISTEN      
2027/master
tcp        0      0 0.0.0.0:59101 0.0.0.0:*                  
LISTEN      1596/rpc.statd
tcp        0      0 0.0.0.0:2049 0.0.0.0:*                   LISTEN      
1518/glusterfs
tcp        0      0 0.0.0.0:38465 0.0.0.0:*                  
LISTEN      1518/glusterfs
tcp        0      0 0.0.0.0:5666 0.0.0.0:*                   LISTEN      
1940/nrpe


3. I then did the "nfs.disable on" on both the volumes share-vol0 and vol0.

4. [root at nfs1 ~]# netstat -an | grep 2049
[root at nfs1 ~]#


5. ganesha then starts successfully:

[root at nfs1 ~]# service nfs-ganesha start
Starting ganesha.nfsd:                                     [  OK  ]
[root at nfs1 ~]#
[root at nfs1 ~]# ps auxw | grep ganesha
root      3478  0.5  0.1 1496316 8532 ?        Ssl  00:05   0:00
/usr/bin/ganesha.nfsd -L /var/log/ganesha.log -f
/etc/ganesha/ganesha.conf -N NIV_EVENT -p /var/run/ganesha.nfsd.pid
root      3521  0.0  0.0 103252   820 pts/1    S+   00:05   0:00 grep
ganesha


Anand"

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=jw9HaMFZGB&a=cc_unsubscribe