Why nfs-ganesha service fail to start if seliux is in enforcing mode in RHGS 3.2

Solution Verified - Updated -

Issue

  • Could not start nfs-ganesha service with selinux in enforcing mode
  • Systemctl status for nfs-ganesha showing "failed" status

    [root@rhgsnode5 ~]# systemctl status nfs-ganesha
    ● nfs-ganesha.service - NFS-Ganesha file server
    Loaded: loaded (/usr/lib/systemd/system/nfs-ganesha.service; disabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Mon 2017-05-29 08:55:08 EDT; 25s ago
     Docs: http://github.com/nfs-ganesha/nfs-ganesha/wiki
    Process: 15443 ExecStop=/bin/dbus-send --system --dest=org.ganesha.nfsd --type=method_call /org/ganesha/nfsd/admin org.ganesha.nfsd.admin.shutdown (code=exited, status=0/SUCCESS)
    Process: 15432 ExecStartPost=/bin/bash -c prlimit --pid $MAINPID --nofile=$NOFILE:$NOFILE (code=exited, status=0/SUCCESS)
    Process: 15430 ExecStart=/bin/bash -c ${NUMACTL} ${NUMAOPTS} /usr/bin/ganesha.nfsd ${OPTIONS} ${EPOCH} (code=exited, status=0/SUCCESS)
    Main PID: 15431 (code=exited, status=2)
    

Environment

  • Red Hat Gluster Storage 3.2
  • Red Hat Enterprise Linux 7.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.