Bug 1293430

Summary:	Add localhost:111 to rpcbind socket activation
Product:	Red Hat Enterprise Linux 7	Reporter:	Benjamin Coddington <bcodding>
Component:	rpcbind	Assignee:	Steve Dickson <steved>
Status:	CLOSED ERRATA	QA Contact:	Yongcheng Yang <yoyang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	bcodding, chunwang, eguan, fs-qe, jlayton, mjudeiki, orion, tgummels, woodard
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rpcbind-0.2.0-35.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 02:09:57 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:	1359592, 1370241
Bug Blocks:	1274917, 1364088

Description Benjamin Coddington 2015-12-21 18:24:36 UTC

Systemd currently starts rpcbind via socket activation when connecting to /var/run/rpcbind.sock, however some programs expect to talk to rpcbind via a localhost socket 111.


I think this is a pretty easy fix: we want /usr/lib/systemd/system/rpcbind.socket to contain:

[Unit]
Description=RPCbind Server Activation Socket

[Socket]
ListenStream=/var/run/rpcbind.sock
ListenStream=[::1]:111
ListenStream=127.0.0.1:111
BindIPv6Only=ipv6-only

[Install]
WantedBy=sockets.target

Comment 2 Benjamin Coddington 2016-01-17 10:51:35 UTC

Actually, fixing this may not be that simple. I just found my RHEL7 system with this modification caused rpcbind to not be able to receive external requests on TCP:111..  I'll try to get to the bottom of it..

Comment 3 Benjamin Coddington 2016-01-17 11:28:49 UTC

(In reply to Benjamin Coddington from comment #2)
> Actually, fixing this may not be that simple. I just found my RHEL7 system
> with this modification caused rpcbind to not be able to receive external
> requests on TCP:111..  I'll try to get to the bottom of it..

^^^ disregard comment 2..  false alarm.  I had a broken networking setup that made me think this wasn't working properly.

Comment 4 Steve Dickson 2016-01-25 16:28:16 UTC

*** Bug 1290601 has been marked as a duplicate of this bug. ***

Comment 5 Benjamin Coddington 2016-03-09 15:01:00 UTC

OK.. /actually/ we want

[Unit]
Description=RPCbind Server Activation Socket

[Socket]
ListenStream=/var/run/rpcbind.sock
ListenStream=[::1]:111
ListenStream=0.0.0.0:111
BindIPv6Only=ipv6-only

[Install]
WantedBy=sockets.target

Otherwise, rpcbind won't listen for external ipv4!  Found this braino while my ipv6 stack was broken.

Comment 10 Yongcheng Yang 2016-06-14 10:22:44 UTC

Move to VERIFIED as comment 9, and continue to run the automatic case.

Comment 20 errata-xmlrpc 2016-11-04 02:09:57 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-2016-2274.html