Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1266993

Summary:	restarting rpbind also restart the the nfs server
Product:	Red Hat Enterprise Linux 7	Reporter:	Steve Dickson <steved>
Component:	nfs-utils	Assignee:	Steve Dickson <steved>
Status:	CLOSED ERRATA	QA Contact:	Yongcheng Yang <yoyang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	eguan, fs-qe, steved, tlavigne
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nfs-utils-1.3.0-0.21.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1279526 (view as bug list)		Environment:
Last Closed:	2015-11-19 04:30:25 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:
Bug Depends On:
Bug Blocks:	1279526

Description Steve Dickson 2015-09-28 18:43:03 UTC

Description of problem:
bz1171603 introduce an regression that cause the starting
and stop of rpcbind  to cause the NFS servers to be
restarted as well...

The starting and stopping of rpcbind should be
independent of the NFS server especially in
NFS v4 only environments  

The starting of the NFS server should start rpcbind
but bring rpcbind down should not bring the NFS
server down. 

Version-Release number of selected component (if applicable):
Latest RHEL7.2 

How reproducible:
100%

Steps to Reproduce:
1. systemctl restart rpcbind

Additional info:
The fix
--- nfs-server.service.orig	2015-09-24 10:50:59.000000000 -0400
+++ nfs-server.service	2015-09-28 14:30:22.497552233 -0400
@@ -1,7 +1,7 @@
 [Unit]
 Description=NFS server and services
 DefaultDependencies=no
-Requires= network.target proc-fs-nfsd.mount rpcbind.service
+Requires= network.target proc-fs-nfsd.mount rpcbind.target
 Requires= nfs-mountd.service
 Wants=rpc-statd.service nfs-idmapd.service
 Wants=rpc-statd-notify.service

Comment 5 Yongcheng Yang 2015-09-30 09:33:44 UTC

There exist an issue: stooping of the NFS server can start rpcbind.
Don't know whether it make sense or not.

Steps to Reproduce:
1. service nfs start; service rpcbind stop; service rpcbind status
   ^^^^^^^^^^^^^^^^^ make sure nfs.service is active
2. service nfs stop; service rpcbind status
   ^^^^^^^^^^^^^^^^^ stopping nfs.service can start rpcbind.service

[root@ibm-x3650m4-08 ~]# rpm -q nfs-utils
nfs-utils-1.3.0-0.21.el7.x86_64
[root@ibm-x3650m4-08 ~]# service nfs start; service rpcbind stop; service rpcbind status
Redirecting to /bin/systemctl start  nfs.service
Redirecting to /bin/systemctl stop  rpcbind.service
Warning: Stopping rpcbind.service, but it can still be activated by:
  rpcbind.socket
Redirecting to /bin/systemctl status  rpcbind.service
● rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
   Active: inactive (dead) since Wed 2015-09-30 17:23:23 CST; 18ms ago
  Process: 20978 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS)
 Main PID: 20981 (code=exited, status=0/SUCCESS)

Sep 30 17:21:27 ibm-x3650m4-08.rhts.eng.pek2.redhat.com systemd[1]: Starting RPC bind service...
Sep 30 17:21:27 ibm-x3650m4-08.rhts.eng.pek2.redhat.com systemd[1]: Started RPC bind service.
Sep 30 17:23:23 ibm-x3650m4-08.rhts.eng.pek2.redhat.com systemd[1]: Stopping RPC bind service...
Sep 30 17:23:23 ibm-x3650m4-08.rhts.eng.pek2.redhat.com systemd[1]: Stopped RPC bind service.
[root@ibm-x3650m4-08 ~]# service nfs stop; service rpcbind status
Redirecting to /bin/systemctl stop  nfs.service
Redirecting to /bin/systemctl status  rpcbind.service
● rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
   Active: active (running) since Wed 2015-09-30 17:23:30 CST; 7ms ago
  Process: 21089 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS)
 Main PID: 21091 (rpcbind)
   CGroup: /system.slice/rpcbind.service
           └─21091 /sbin/rpcbind -w

Sep 30 17:23:30 ibm-x3650m4-08.rhts.eng.pek2.redhat.com systemd[1]: Starting RPC bind service...
Sep 30 17:23:30 ibm-x3650m4-08.rhts.eng.pek2.redhat.com systemd[1]: Started RPC bind service.
[root@ibm-x3650m4-08 ~]#

Comment 7 Steve Dickson 2015-09-30 11:34:00 UTC

(In reply to Yongcheng Yang from comment #5)
> There exist an issue: stooping of the NFS server can start rpcbind.
> Don't know whether it make sense or not.
> 
> Steps to Reproduce:
> 1. service nfs start; service rpcbind stop; service rpcbind status
>    ^^^^^^^^^^^^^^^^^ make sure nfs.service is active
> 2. service nfs stop; service rpcbind status
>    ^^^^^^^^^^^^^^^^^ stopping nfs.service can start rpcbind.servicer
rpcbind is started because one of the daemon tried to access it.

A while back systemd socket activation support was added which
means if a daemon tries to connect to port 111 systemd will
start rpcbind automaticly.

So this does make sense

Comment 9 errata-xmlrpc 2015-11-19 04:30:25 UTC

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-2015-2196.html