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 1293430 - Add localhost:111 to rpcbind socket activation
Summary: Add localhost:111 to rpcbind socket activation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpcbind
Version: 7.3
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
: 1290601 (view as bug list)
Depends On: 1359592 1370241
Blocks: 1274917 1364088
TreeView+ depends on / blocked
 
Reported: 2015-12-21 18:24 UTC by Benjamin Coddington
Modified: 2018-01-06 10:14 UTC (History)
9 users (show)

Fixed In Version: rpcbind-0.2.0-35.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 02:09:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1359592 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1370241 0 high CLOSED NFS mounts don't work on diskless clients when ipv6 is disabled 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1377055 0 medium CLOSED rpcbind.socket warn "Failed to parse address value, ignoring: [::]:111" after updating to 0.2.0-35 with ipv6 disabled 2021-06-10 11:32:30 UTC
Red Hat Bugzilla 1405878 0 medium CLOSED Rpcbind is making systemd capture 111 port 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1411412 0 high CLOSED 7.3 upgrade of rpcbind breaks IPA, systemd, dbus 2021-06-10 11:48:19 UTC
Red Hat Bugzilla 1425758 1 None None None 2021-09-09 12:09:09 UTC
Red Hat Product Errata RHBA-2016:2274 0 normal SHIPPED_LIVE rpcbind bug fix and enhancement update 2016-11-03 13:35:05 UTC


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
Note You need to log in before you can comment on or make changes to this bug.