[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work

Srikanth 1973101 at bugs.launchpad.net
Wed Nov 13 05:11:05 UTC 2024


I have to use nfs version 3 in org for bitbucket datacenter

I have followed bellow steps.

1)NFS Server Configuration Updates Edited /etc/default/nfs-kernel-server
to disable NFS versions 2 and 4 and set a fixed port for mountd:

RPCMOUNTDOPTS="--manage-gids --port 9024" 
RPCNFSDOPTS="-N 4 -N 2"


2)Configured /etc/default/nfs-common to set fixed ports for statd and
lockd:

NEED_STATD=yes
STATDOPTS="--port 9028 --outgoing-port 9029" LOCKD_OPTS="-p 9027 -o 9026"


3)Updated /etc/modprobe.d/lockd.conf to set specific TCP and UDP ports
for lockd:

options lockd nlm_tcpport=9027 options lockd nlm_udpport=9028



4)Applied configurations and restarted services:

sudo systemctl restart nfs-kernel-server rpcbind 
sudo systemctl daemon-reload


5)Observations from rpcinfo -p Output: After applying the above configurations, the output of rpcinfo -p showed the following:

program vers proto port service
100005 1 udp 40661 mountd
100005 1 tcp 45805 mountd
100005 2 udp 55256 mountd
100005 2 tcp 50431 mountd
100005 3 udp 34768 mountd
100005 3 tcp 47275 mountd



6)Despite setting RPCMOUNTDOPTS="--port 9024" in /etc/default/nfs-kernel-server, mountd continued to use random ports (e.g., 40661, 45805). This suggests the configuration may not have applied correctly

The mounting error (mount.nfs: Connection timed out) may stem from the
mountd service binding to random ports instead of the specified port
(9024). This causes firewall and security group configurations to
mismatch, resulting in a timeout during the mount attempt.


Do I need to modify any other files in in order to make my nfs server to
work on nfs3 version with static ports. In /etc.nfs.conf file if I give
static port for mountd, lockd, statd then will I able to make my nfs
server to work on only nfsversion3

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1973101

Title:
  After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work

Status in nfs-utils package in Ubuntu:
  Opinion

Bug description:
  I upgraded from 20.04 to 22.04 a server which has NFS clients that are
  version 2 (SunOS 4.1.4), version 3 (Redhat 6.2) and version 4.2 (other
  modern Linux systems).

  After upgrading the version 2 and version 3 clients no longer can
  mount the file systems.

  A check with rpcinfo -p showed version 2 no longer being advertised, I
  checked the conf and found the update had disabled it, I re-enabled
  it.

  Version 3 was still advertised, but the mount still fails, and after
  re-enabling version 2, the mount still fails.

  I am also not at all appreciative of the unauthorized changes that the
  upgrade made to my exports file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nfs-kernel-server 1:2.6.1-1ubuntu1
  Uname: Linux 5.17.6 x86_64
  .etc.request-key.d.id_resolver.conf: create	id_resolver	*	*	/usr/sbin/nfsidmap -t 600 %k %d
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Wed May 11 18:44:54 2022
  NFSMounts:
   
  NFSv4Mounts:
   /bu    204.122.16.128:/mail.bu nfs4   rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=204.122.16.222,local_lock=none,addr=204.122.16.128
   /misc  204.122.16.12:/misc     nfs4   rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=204.122.16.222,local_lock=none,addr=204.122.16.12
   /home  204.122.16.12:/home     nfs4   rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=204.122.16.222,local_lock=none,addr=204.122.16.12
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nfs-utils
  UpgradeStatus: Upgraded to jammy on 2022-05-10 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions




More information about the foundations-bugs mailing list