invalid PID argument: --nofile=1048576:1048576 encountered at nfs-ganesha.service on 1 node when the whole cluster is rebooted
Issue
We sometimes encounter the following error at nfs-ganesha.service on 1 node when the whole cluster is rebooted at the same time:
prlimit: invalid PID argument: '--nofile=1048576:1048576'
● nfs-ganesha.service - NFS-Ganesha file server
Loaded: loaded (/usr/lib/systemd/system/nfs-ganesha.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Mon 2018-03-26 07:35:42 EST; 6min ago
Docs: http://github.com/nfs-ganesha/nfs-ganesha/wiki
Process: 1503 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: 1489 ExecStartPost=/bin/bash -c prlimit --pid $MAINPID --nofile=$NOFILE:$NOFILE (code=exited, status=1/FAILURE)
Process: 1445 ExecStart=/bin/bash -c ${NUMACTL} ${NUMAOPTS} /usr/bin/ganesha.nfsd ${OPTIONS} ${EPOCH} (code=exited, status=0/SUCCESS)
Mar 26 07:35:42 gluster01 systemd[1]: Starting NFS-Ganesha file server...
Mar 26 07:35:42 gluster01 bash[1489]: prlimit: invalid PID argument: '--nofile=1048576:1048576'
Mar 26 07:35:42 gluster01 systemd[1]: Started NFS-Ganesha file server.
Environment
- Red Hat Gluster Storage 3.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
