Red Hat Bugzilla – Bug 1015283
rpcbind terminates with an error when unit is stopped
Last modified: 2014-11-18 07:08:47 EST
Description of problem:
During shutdown rpcbind.service prints ugly warnings:
Oct 03 21:25:29 fedora systemd: Stopping RPC bind service...
Oct 03 21:25:29 fedora rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Oct 03 21:25:29 fedora systemd: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 03 21:25:29 fedora systemd: Stopped RPC bind service.
Oct 03 21:25:29 fedora systemd: Unit rpcbind.service entered failed state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. systemctl stop rpcbind
2. look at the logs
Silent shutdown, with messages at most at info priority.
Until the daemon is fixed, SuccessExitStatus=2. At least systemd will not consider it is in failed state.
So restarts and yum updates work rpcbind has to be started with -w
flag which causes all the current port and service state to be
written to a file. So when that file does not exist
during start up, it should be logged.
Sure, the advice to use -w might be solid, this bug is not about that. The problem is that the unit should start and terminate cleanly. So either the daemon or the unit or both should be adjusted so this happens.
rpcbind-0.2.1-3.0.fc21 has been submitted as an update for Fedora 21.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rpcbind-0.2.1-3.0.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
rpcbind-0.2.1-4.0.fc21 has been submitted as an update for Fedora 21.
rpcbind-0.2.1-4.0.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.