Mounting of network filesystem fails with message 'rpc.statd is not running but is required for remote locking'

Issue

• Network filesystem mounting fails with messages:

Job for rpc-statd.service failed because the control process exited with error code.
See "systemctl status rpc-statd.service" and "journalctl -xe" for details.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.

• Below messages are reported in the log file while starting rpcbind service on NFS-Client:

May  5 11:26:08 <hostname> systemd[1]: rpcbind.service: Main process exited, code=killed, status=11/SEGV
May  5 11:26:08 <hostname> systemd[1]: rpcbind.service: Failed with result 'signal'.
May  5 11:26:08 <hostname> kernel: traps: rpcbind[3296956] general protection fault ip:7ffff735fe18 sp:7fffffffeb00 error:0 in libc-2.28.so[7ffff7279000+1b9000]
May  5 11:26:08 <hostname> audisp-syslog[4760]: type=SERVICE_START msg=audit(1620185168.050:1113903): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpcbind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' UID="root" AUID="unset"
May  5 11:26:08 <hostname> audisp-syslog[4761]: type=SERVICE_START msg=audit(1620185168.050:1113903): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpcbind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' UID="root" AUID="unset"
May  5 11:26:08 <hostname> systemd[1]: rpcbind.service: Start request repeated too quickly.
May  5 11:26:08 <hostname> systemd[1]: rpcbind.service: Failed with result 'signal'.
May  5 11:26:08 <hostname> systemd[1]: rpcbind.socket: Failed with result 'service-start-limit-hit'.
May  5 11:26:09 <hostname> systemd[1]: Listening on RPCbind Server Activation Socket.
May  5 11:26:09 <hostname> systemd[1]: rpcbind.service: Start request repeated too quickly.
May  5 11:26:09 <hostname> systemd[1]: rpcbind.service: Failed with result 'signal'.
May  5 11:26:09 <hostname> systemd[1]: rpcbind.socket: Failed with result 'service-start-limit-hit'.
May  5 11:36:32 <hostname> kernel: [   34.720212] traps: rpcbind[5385] general protection fault ip:7ffff735fe18 sp:7fffffffeb00 error:0 in libc-2.28.so[7ffff7279000+1b9000]
May  5 11:36:32 <hostname> kernel: [   34.727294] traps: rpcbind[5393] general protection fault ip:7ffff735fe18 sp:7fffffffeb00 error:0 in libc-2.28.so[7ffff7279000+1b9000]
May  5 11:36:32 <hostname> kernel: [   34.733972] traps: rpcbind[5403] general protection fault ip:7ffff735fe18 sp:7fffffffeb00 error:0 in libc-2.28.so[7ffff7279000+1b9000]
May  5 11:36:32 <hostname> kernel: [   34.740412] traps: rpcbind[5415] general protection fault ip:7ffff735fe18 sp:7fffffffeb00 error:0 in libc-2.28.so[7ffff7279000+1b9000]
May  5 11:36:32 <hostname> kernel: [   34.746156] traps: rpcbind[5422] general protection fault ip:7ffff735fe18 sp:7fffffffeb00 error:0 in libc-2.28.so[7ffff7279000+1b9000]
May  5 11:36:21 <hostname> rpcbind[4762]: cannot create socket for udp6
May  5 11:36:21 <hostname> rpcbind[4762]: cannot create socket for tcp6