We use Ganesha 2.3.0 NFS server in our filesystem, and in a use-case, the
status of Ganesha and rpcbind ended up as follows. Note that only Ganesha
is using rpcbind, RQUOTA port.
- Ganesha is refusing to start
> 03/03/2016 T13:41:25.368197-0800 : nfs-ganesha-16909[main] 335
> :Bind_sockets_V6 :DISP :WARN :Cannot bind RQUOTA udp6 socket, error 98
> (Address already in use)
> 03/03/2016 T13:41:25.370931-0800 : nfs-ganesha-16909[main] 485
> :Bind_sockets :DISP :FATAL :Error binding to V6 interface. Cannot continue.
- netstat is showing that rpcbind is the service process
> udp 0 0 *:875 *:*
> 7908/rpcbind
> udp6 0 0 [::]:875 [::]:*
> 7908/rpcbind
Questions -
- How to clean up rpcbind to stop listening to RQUOTA port?
- How did the state end up as above, is Ganesha supposed to cleanup when
shutting down?
Any help is appreciated.
Thanks.
Regards.
Krishna Harathi
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Nfs-ganesha-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
