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.
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
...
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
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 ...