Description of problem:
While verifying bug #1451981 ,as mentioned in comment #13,Observed..ganesha service goes to failed state on few nodes after reboot.
Version-Release number of selected component (if applicable):
# rpm -qa | grep ganesha
Steps to Reproduce:
1.Create 6 node ganesha cluster.
2.Reboot all the nodes
When nodes come up,on few nodes Ganesha service goes to failed state.
Ganesha service should start on all the nodes after reboot.
systemctl status nfs-ganesha
● nfs-ganesha.service - NFS-Ganesha file server
Loaded: loaded (/usr/lib/systemd/system/nfs-ganesha.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Thu 2017-07-20 12:16:16 IST; 2h 28min ago
Main PID: 2341 (code=exited, status=2)
Jul 20 12:16:16 dhcp42-127.lab.eng.blr.redhat.com systemd: Starting NFS-Ganesha file server...
Jul 20 12:16:16 dhcp42-127.lab.eng.blr.redhat.com bash: prlimit: invalid PID argument: '--nofile=1048576:1048576'
Jul 20 12:16:16 dhcp42-127.lab.eng.blr.redhat.com systemd: Started NFS-Ganesha file server.
Even though nfs-ganesha didn't start properly, but systemd consider it to be started.
Is there a ganesha log somewhere?
(In reply to Daniel Gryniewicz from comment #2)
> Is there a ganesha log somewhere?
Here ganesha service was not at started because ganesha.conf was not available(for gluster we store ganesha.conf in shared volume). But by somehow systemd interupts it to be started and stopping restarting ganesha service after reboot
Doc text looks good to me