Krishna Harathi [[email protected]] wrote: > 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?
Just restarting rpcbind should free up, right? > - How did the state end up as above, is Ganesha supposed to cleanup when > shutting down? I think so. commit 5ca600a1d81562b9b0c7c371d6e818f76bd8567c made some effort in that regard. Regards, Malahal. PS: I can use "kill -9" to ganesha process, it gets killed but "rpcinfo -p" reports all ports being serviced. But I can restart ganesha without any issues though (I need to look at if it is cleaning up before re-using ports...) ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval _______________________________________________ Nfs-ganesha-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
