Description of problem: After startup in 3.3 , nfs ganesha daemon goes down with any command. ceph version 12.2.12-40.el7cp Steps to Reproduce: 1. Bring up ganesha on 3.3 2. Mount with v3 or v4, try a ls command on mount point 3. The nfs-ganesha daemon goes down Additional info: a]# mkdir test1 mkdir: cannot create directory ‘test1’: Input/output error Ganesha logs: 24/07/2019 04:29:26 : epoch 5d37de9f : magna009 : ganesha.nfsd-19144[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs 24/07/2019 04:29:26 : epoch 5d37de9f : magna009 : ganesha.nfsd-19144[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized 24/07/2019 04:29:26 : epoch 5d37de9f : magna009 : ganesha.nfsd-19144[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists 24/07/2019 04:29:26 : epoch 5d37de9f : magna009 : ganesha.nfsd-19144[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (2:2)
Created attachment 1597470 [details] ganesha.log from last crash (I think it has an extra startup at the beginning)
Created attachment 1597472 [details] re-run with CACHE_INODE = FULL_DEBUG;
This is https://github.com/nfs-ganesha/nfs-ganesha/commit/0beeae7c76dbf43ae388728ddd6e8065fad4c207 I'll backport it.
This has been backported.
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:2538
*** Bug 1732788 has been marked as a duplicate of this bug. ***