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 1303751 - Upgrade of rpcbind does not restart rpcbind.socket
Summary: Upgrade of rpcbind does not restart rpcbind.socket
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpcbind
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
Marie Hornickova
URL:
Whiteboard:
: 1278468 (view as bug list)
Depends On:
Blocks: 1203710 1295577 1306824 1313485 1325769
TreeView+ depends on / blocked
 
Reported: 2016-02-01 20:27 UTC by Frank Sorenson
Modified: 2019-11-14 07:23 UTC (History)
12 users (show)

Fixed In Version: rpcbind-0.2.0-35.el7
Doc Type: Bug Fix
Doc Text:
After an upgrage of the rpcbind packages, the automounted file systems became inaccessible, which also caused an unexpected termination of running applications dependant on these file systems. The provided patch ensures that the rpcbind.socket is restarted. As a result, rpcinfo is able to connect to rpcbind locally, and automounted file systems are accessible as expected.
Clone Of:
: 1306824 1325769 (view as bug list)
Environment:
Last Closed: 2016-11-04 02:10:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
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 Frank Sorenson 2016-02-01 20:27:00 UTC 
Description of problem:

When upgrading rpcbind, rpcbind.socket is not restarted, so rpcbind cannot be queried locally


Version-Release number of selected component (if applicable):

rpcbind-0.2.0-32.el7.x86_64.rpm


How reproducible:

see below


Steps to Reproduce:

begin with lower-version rpcbind

# rpm -qa rpcbind:
rpcbind-0.2.0-26.el7.x86_64

verify rpcinfo works:
# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
...

upgrade rpcinfo:
# rpm -Fvh rpcbind-0.2.0-34.el7.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:rpcbind-0.2.0-34.el7             ################################# [ 50%]
Cleaning up / removing...
   2:rpcbind-0.2.0-26.el7             ################################# [100%]

test rpcinfo:
# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused


Actual results:

rpcinfo is unable to connect to rpcbind locally


Expected results:

rpcinfo continues to work after upgrade


Additional info:

rpcinfo is connecting using the socket at /var/run/rpcbind.sock:

# strace -fttT -etrace=connect rpcinfo -p
20:14:59.801429 connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/rpcbind.sock"}, 23) = -1 ECONNREFUSED (Connection refused) <0.000044>
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
20:14:59.802120 +++ exited with 1 +++


restarting rpcbind.socket makes things work again:

# systemctl restart rpcbind.socket

# strace -fttT -etrace=connect rpcinfo -p
20:15:19.438648 connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/rpcbind.sock"}, 23) = 0 <0.000188>
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    4   tcp    111  portmapper
...
Comment 5 Steve Dickson 2016-02-11 19:26:54 UTC 
This is the needed patch which also needs to go into fedora

diff --git a/rpcbind.spec b/rpcbind.spec
index 92824f0..8389f1a 100644
--- a/rpcbind.spec
+++ b/rpcbind.spec
@@ -157,8 +157,9 @@ fi
 /sbin/chkconfig --del rpcbind >/dev/null 2>&1 || :
 /bin/systemctl try-restart rpcbind.service >/dev/null 2>&1 || :
 
-%triggerun -- rpcbind > 0.2.0-26
+%triggerin -- rpcbind > 0.2.0-26
 /bin/systemctl enable rpcbind.socket >/dev/null 2>&1 || :
+/bin/systemctl restart rpcbind.socket >/dev/null 2>&1 || :
 
 %triggerpostun -- rpcbind < -2.2.0-29
 [ ! -d /run/rpcbind ] && mkdir /run/rpcbind || :
Comment 10 Steve Dickson 2016-04-04 20:49:15 UTC 
Fedora commit:

ommit c0f80c5a6720c12c710e444714be7eae388c1460
Author: Steve Dickson <steved>
Date:   Mon Apr 4 11:01:08 2016 -0400

    Restart rpcbind.socket on restarts (bz 1306824)
Comment 11 Steve Dickson 2016-04-09 14:42:26 UTC 
*** Bug 1278468 has been marked as a duplicate of this bug. ***
Comment 14 Joseph Kachuck 2016-04-11 17:42:26 UTC 
Hello,

This bug has been copied as 7.2 z-stream (EUS) bug #1325769 

Thank You
Joe Kachuck
Comment 17 errata-xmlrpc 2016-11-04 02:10:07 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.