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.
DescriptionBenjamin 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 2Benjamin 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 3Benjamin 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.
*** Bug 1290601 has been marked as a duplicate of this bug. ***
Comment 5Benjamin 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.
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