Bug 1413538 - mountd port registration lost after rpcbind restarts
Summary: mountd port registration lost after rpcbind restarts
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpcbind
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-16 10:33 UTC by Tom Hughes
Modified: 2017-01-16 19:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-16 19:08:53 UTC
Type: Bug


Attachments (Terms of Use)

Description Tom Hughes 2017-01-16 10:33:26 UTC
Description of problem:

The rpcbind package restarts the rpcbind daemon whenever it is updated which causes the nfs mountd port registration to be forgotten and mounts to fail because clients can no longer look up the mountd port number.

Yes I know newer clients will just go ahead and use the default port in that case but older ones don't and will just refuse to mount until mountd is restarted to trigger a new registration of the port.

Ordinarily I would suggest using BindsTo in the systemd unit to cause mountd to restart when rpcbind restarts but as it's valid to run mountd without rpcbind I don't think that will work so I'm not entirely sure what the solution is here unless there is some way for mountd to notice the restart of rpcbind and reregister?

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

nfs-utils-1.3.4-1.rc3.fc24.x86_64

Comment 1 Steve Dickson 2017-01-16 19:08:53 UTC
This is actually due to rpcbind being updated to rpcbind-0.2.3-14.rc2.fc24
With this update, which was documented in the update,d  a reboot or 
restart of NFS is needed to get the ports registered... 

This is a one time thing.... My apologies if it caused any problem.


Note You need to log in before you can comment on or make changes to this bug.