Hide Forgot
Description of problem: I've seen a number of reports of multiple rpc.statds being started.. Description of problem: commit d92017cccaffb02f7f4e00d0fdd6ef5042bb6341 Author: NeilBrown <neilb> Date: Sat Jan 16 12:09:50 2016 -0500 start-statd: don't run multiple rpc.statds on the one host. If rpc.statd is running but slow to respond, mount.nfs will run "start-statd" which might start a new statd. This is not a good ideas as can result in lots of rpc.statds. So inf start-statd check the pid file and if rpc.statd seems to be running, exit with success. (also "cd /" before running rpc.statd, just in case). Signed-off-by: NeilBrown <neilb> Signed-off-by: Steve Dickson <steved>
*** Bug 1224357 has been marked as a duplicate of this bug. ***
The upstream commit... http://marc.info/?l=linux-nfs&m=146644251031055&w=2
commit 8fef90084f3d19e90ba1bb22b8cd1d58ddaf6ef3 Author: Steve Dickson <steved> Date: Tue Jun 21 12:06:06 2016 -0400 start-statd: Use flock to serialize the running of this script
Move to VERIFIED as test logs in comment 12. Continue to run the automatic case.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2383.html