Bug 1508876 - [RGW:NFS] After a ganesha process kill, nfs-ganesha.service fails to start on it's own.
Summary: [RGW:NFS] After a ganesha process kill, nfs-ganesha.service fails to start on...
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Ceph-Ansible
Version: 3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 3.*
Assignee: Ali Maredia
QA Contact: ceph-qe-bugs
Depends On:
Blocks: 1494421
TreeView+ depends on / blocked
Reported: 2017-11-02 12:35 UTC by vidushi
Modified: 2018-06-26 23:46 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.`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.
Clone Of:
Last Closed: 2018-04-03 21:50:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description vidushi 2017-11-02 12:35:31 UTC
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):
ceph version 12.2.1-37.el7cp

How reproducible:

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.

Comment 6 Kaleb KEITHLEY 2017-11-06 23:13:53 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.