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.
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/nfs-serverconfig.html
Section Number and Name:
8.7. NFS Server Configuration
Donald Sarratt wrote:
The section suggests setting LOCKD_TCPPORT and LOCKD_UDPPORT in /etc/sysconfig/nfs to specify the ports used by the nlockmgr service.
This doesn't seem to work for me, as mentioned in /etc/sysconfig/nfs itself I had to set the parameters in /etc/modprobe.d/lockd.conf instead. Should the documentation be updated to reflect this?
Hi Steve,
Could you please have a look at section 8.7. NFS Server Configuration and let me know what we should change based on the customer's feedback?
Thank you very much.
(In reply to Milan Navratil from comment #1)
> Hi Steve,
>
> Could you please have a look at section 8.7. NFS Server Configuration and
> let me know what we should change based on the customer's feedback?
>
> Thank you very much.
Yeap that has been changed when we moved to the upstream systemd services.
/etc/sysconfig/nfs now states:
#
#
# To set lockd kernel module parameters please see
# /etc/modprobe.d/lockd.conf
#
and /etc/modprobe.d/lockd.conf
#
# Set the NFS lock manager grace period. n is measured in seconds.
#options lockd nlm_grace_period=90
#
# Set the TCP port that the NFS lock manager should use.
# port must be a valid TCP port value (1-65535).
#options lockd nlm_tcpport
#
# Set the UDP port that the NFS lock manager should use.
# port must be a valid UDP port value (1-65535).
#options lockd nlm_udpport
#
# Set the maximum number of outstanding connections
#options lockd nlm_max_connections=1024
#
# Set the default time value for the NFS lock manager
# in seconds. Default is 10 secs (min 3 max 20)
#options lockd nlm_timeout=10
#
# Choose whether to record the caller_name or IP address
# this peer in the local rpc.statd's database.
#options lockd nsm_use_hostnames=0