I remember seeing this when another NFS server is running (or rpcbind), but I shut these off before starting Ganesha.

 

From: "Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] via Support" <support@lists.nfs-ganesha.org>
Reply-To: "Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]" <jeffrey.c.becker@nasa.gov>
Date: Tuesday, December 1, 2020 at 4:50 PM
To: "support@lists.nfs-ganesha.org" <support@lists.nfs-ganesha.org>
Subject: [EXTERNAL] [NFS-Ganesha-Support] How to avoid these UDP errors on Ganesha startup

 

I haven’t seen these before. However I just rebooted the system, so maybe something else needs to be set up? Thanks.

 

-Jeff

 

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] fsal_save_ganesha_credentials :FSAL :INFO :Ganesha uid=0 gid=0 ngroups=0

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] nfs_Init_svc :DISP :INFO :NFS INIT: using TIRPC

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] nfs_Init_svc :DISP :INFO :NFS INIT: Using IPv6

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] Bind_sockets :DISP :INFO :Bind sockets successful, v6disabled = 1, vsock = 0, rdma = 0

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] __Register_program :DISP :INFO :Registering NFS V4/UDP

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] __Register_program :DISP :MAJ :Cannot register NFS V4 on UDP

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] __Register_program :DISP :INFO :Registering RQUOTA V1/UDP

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] __Register_program :DISP :MAJ :Cannot register RQUOTA V1 on UDP

02/12/2020 00:31:50 : epoch 5fc6e076 : linux : ganesha.nfsd-34[main] unregister_fsal :FSAL :CRIT :Unregister FSAL PROXY with non-zero refcount=21