Hide Forgot
.`nfs-ganesha.service` fails to start after a crash or a process kill of NFS Ganesha When the NFS Ganesha process terminates unexpectedly or it is killed, the `nfs-ganesha.service` daemon fails to start as expected.
Description of problem: After a process kill for Ganesha process, it did not start on it's own and nfs-ganesha.service failed to start. Version-Release number of selected component (if applicable): nfs-ganesha-rgw-2.5.2-13.el7cp.x86_64 ceph version 12.2.1-37.el7cp How reproducible: Everytime Steps to Reproduce: 1. Configure set-up for NFS-ganesha role. 2. Run ansible-playbook and check if the ganesha service has come up. (cmd 'systemctl status nfs-ganesha.service' . It should be up/running) 3. Check for the nfs-ganesha process id (cmd "ps aux | grep ganesha") 4. Kill ganesha process (cmd ' kill <pid> ') 5. The nfs-ganesha.service should come up after few seconds. (It fails to load) Actual results: nfs-ganesha.service fails to start. Expected results: nfs-ganesha.service should to start after sometime. Additional info: As is the case with the ceph-daemons (OSDs and MON), start of nfs-ganesha service should also be handled after a process kill.
At a minimum there is `systemctl enable nfs-ganesha` which will ensure that ganesha.nfsd restarts when the box boots or reboots. There is some systemctl magic for automatically restarting a process that crashes; you'll need to rtfm as I don't know what that is off the top of my head. And FWIW, GlusterFS made a conscious decision not to automatically restart. At some point GlusterFS will revisit that decision. Ceph is not required to copy GlusterFS behavior.