Bug 1015283

Summary:	rpcbind terminates with an error when unit is stopped
Product:	[Fedora] Fedora	Reporter:	Zbigniew Jędrzejewski-Szmek <zbyszek>
Component:	rpcbind	Assignee:	Steve Dickson <steved>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	marcosfrm, steved
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rpcbind-0.2.1-4.0.fc21	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-18 12:08:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zbigniew Jędrzejewski-Szmek 2013-10-03 19:38:46 UTC

Description of problem:
During shutdown rpcbind.service prints ugly warnings:

Oct 03 21:25:29 fedora systemd[1]: Stopping RPC bind service...
Oct 03 21:25:29 fedora rpcbind[589]: rpcbind terminating on signal. Restart with "rpcbind -w"
Oct 03 21:25:29 fedora systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 03 21:25:29 fedora systemd[1]: Stopped RPC bind service.
Oct 03 21:25:29 fedora systemd[1]: Unit rpcbind.service entered failed state.

Version-Release number of selected component (if applicable):
rpcbind-0.2.1-0.1.fc21.x86_64
systemd-208

How reproducible:
100%

Steps to Reproduce:
1. systemctl stop rpcbind
2. look at the logs

Expected results:
Silent shutdown, with messages at most at info priority.

Comment 1 Marcos Mello 2014-04-21 12:03:33 UTC

Until the daemon is fixed, SuccessExitStatus=2. At least systemd will not consider it is in failed state.

Comment 2 Steve Dickson 2014-10-23 18:04:48 UTC

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.

Comment 3 Zbigniew Jędrzejewski-Szmek 2014-10-23 22:31:18 UTC

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.

Comment 4 Fedora Update System 2014-10-27 15:38:51 UTC

rpcbind-0.2.1-3.0.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/FEDORA-2014-13642/rpcbind-0.2.1-3.0.fc21

Comment 5 Fedora Update System 2014-10-28 10:08:10 UTC

Package rpcbind-0.2.1-3.0.fc21:
* 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:
https://admin.fedoraproject.org/updates/FEDORA-2014-13642/rpcbind-0.2.1-3.0.fc21
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-11-10 17:57:45 UTC

rpcbind-0.2.1-4.0.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/rpcbind-0.2.1-4.0.fc21

Comment 7 Fedora Update System 2014-11-18 12:08:47 UTC

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.