-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-9.6, rhel-10.0
-
nfs-utils-2.8.3-1.el10
-
No
-
Low
-
TestCaseProvided
-
rhel-fs-net
-
None
-
False
-
False
-
-
None
-
None
-
Pass
-
Automated
-
Unspecified
-
Unspecified
-
Unspecified
-
-
All
-
None
What were you trying to do that didn't work?
In my test logs always find the rpc.statd warning
Jun 14 13:56:51 rhel-10-upk rpc.statd[13137]: Failed to register (statd, 1, udp): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk rpc.statd[13137]: Failed to register (statd, 1, tcp): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk rpc.statd[13137]: Failed to register (statd, 1, udp6): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk rpc.statd[13137]: Failed to register (statd, 1, tcp6): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk rpc.statd[13137]: failed to create RPC listeners, exiting Jun 14 13:56:51 rhel-10-upk systemd[1]: rpc-statd.service: Control process exited, code=exited, status=1/FAILURE Jun 14 13:56:51 rhel-10-upk systemd[1]: rpc-statd.service: Failed with result 'exit-code'. Jun 14 13:56:51 rhel-10-upk systemd[1]: Failed to start rpc-statd.service - NFS status monitor for NFSv2/3 locking..
And it happens if trying to restart nfs-server when rpcbind/rpcbind.socket stopped.
P.s. After checking the rpc-statd systemd script IMO we should "Requires" rpcbind.service in coordination with the "After" sentence.
[root@rhel-10-upk ~]# systemctl cat rpc-statd | grep rpcbind Requires=nss-lookup.target rpcbind.socket After=network-online.target nss-lookup.target rpcbind.service [root@rhel-10-upk ~]#
What is the impact of this issue to you?
We have to restart the rpc-statd once again
Please provide the package NVR for which the bug is seen:
Both current rhel10 (nfs-utils-2.8.3-0.el10) and rhel9 (nfs-utils-2.5.4-37.el9) have this issue
How reproducible is this bug?:
Reliable
Steps to reproduce
[root@rhel ~]# for i in `seq 10`; do systemctl reset-failed; systemctl stop rpcbind rpcbind.socket ; systemctl restart nfs-server ; systemctl status rpc-statd; done
Expected results
Staring nfs-server should bring rpc-statd active also
Actual results
[root@rhel-10-upk ~]# rpm -q nfs-utils nfs-utils-2.8.3-0.el10.x86_64 [root@rhel-10-upk ~]# systemctl restart nfs-server [root@rhel-10-upk ~]# systemctl stop rpcbind rpcbind.socket [root@rhel-10-upk ~]# systemctl restart nfs-server [root@rhel-10-upk ~]# systemctl status rpc-statd × rpc-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; static) Active: failed (Result: exit-code) since Sat 2025-06-14 13:56:51 UTC; 9s ago Duration: 23.729s Invocation: 6aa708e890e64c609c1aa4dd299bb479 Docs: man:rpc.statd(8) Process: 13136 ExecStart=/usr/sbin/rpc.statd (code=exited, status=1/FAILURE) Mem peak: 1.5M CPU: 8msJun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: Version 2.8.3 starting Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: Flags: TI-RPC Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: Failed to register (statd, 1, udp): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: Failed to register (statd, 1, tcp): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: Failed to register (statd, 1, udp6): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: Failed to register (statd, 1, tcp6): svc_reg() err: RPC: Success Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net rpc.statd[13137]: failed to create RPC listeners, exiting Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net systemd[1]: rpc-statd.service: Control process exited, code=exited, status=1/FAILURE Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net systemd[1]: rpc-statd.service: Failed with result 'exit-code'. Jun 14 13:56:51 rhel-10-upk.lab.kissvm.net systemd[1]: Failed to start rpc-statd.service - NFS status monitor for NFSv2/3 locki> lines 1-20/20 (END)
- links to
-
RHBA-2025:154773
nfs-utils update
