-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.0
-
None
What were you trying to do that didn't work?
Since we changing to use `nfsdctl` to start the NFS server, setting "tcp=n" in /etc/nfs.conf starts to get some wired output:
[root@dell-per660-17 ~]# rpm -q nfs-utils nfs-utils-2.8.2-0.el10.x86_64 [root@dell-per660-17 ~]# echo -e "[nfsd]\ntcp=n" > /etc/nfs.conf [root@dell-per660-17 ~]# cat /etc/nfs.conf [nfsd] tcp=n [root@dell-per660-17 ~]# systemctl restart nfs-server [root@dell-per660-17 ~]# rpcinfo -p | grep -w nfs 100003 3 udp 2049 nfs 100003 3 tcp 2049 nfs <<<< 100003 4 tcp 2049 nfs <<<<
By default it's like:
[root@dell-per660-17 ~]# echo > /etc/nfs.conf [root@dell-per660-17 ~]# systemctl restart nfs-server [root@dell-per660-17 ~]# rpcinfo -p | grep -w nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs
Disable tcp and enable udp will be like:
[root@dell-per660-17 ~]# echo -e "[nfsd]\ntcp=n\nudp=y" > /etc/nfs.conf [root@dell-per660-17 ~]# cat /etc/nfs.conf [nfsd] tcp=n udp=y [root@dell-per660-17 ~]# systemctl restart nfs-server [root@dell-per660-17 ~]# rpcinfo -p | grep -w nfs 100003 3 udp 2049 nfs
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
Steps to reproduce
Expected results
Previously starting nfs-server with "tcp=n" will be failed like:
rpc.nfsd[11653]: rpc.nfsd: version 4 requires the TCP protocol systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE
Actual results
- relates to
-
-
- Closed
-
