While trying to setup NFS on an OVM 3.2 configuration on OEL 5.9, I followed the documentation to the letter but when time came to start the NFS daemon I kept getting the error above.
[root@ovm /]# service nfs start Starting NFS services: [ OK ] Starting NFS quotas: Cannot register service: RPC: Unable to receive; errno = Connection refused rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp). [FAILED] Starting NFS daemon: [FAILED]
After a little googling, it turns out that RPCBind may not be running.
[root@ovm /]# rpcinfo -p rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
Perhaps I needed to update my NFS Utility packages?
[root@ovm /]# yum install nfs-utils Loaded plugins: rhnplugin, security This system is not registered with ULN. You can use up2date --register to register. ULN support will be disabled. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package nfs-utils.x86_64 1:1.0.9-70.el5 set to be updated --> Processing Dependency: initscripts >= 8.45.43 for package: nfs-utils --> Running transaction check ---> Package initscripts.x86_64 0:8.45.44-3.0.1.el5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================= Updating: nfs-utils x86_64 1:1.0.9-70.el5 el5_latest 409 k Updating for dependencies: initscripts x86_64 8.45.44-3.0.1.el5 el5_latest 1.6 M Transaction Summary ============================================================================================================================================================= Install 0 Package(s) Upgrade 2 Package(s) Total download size: 2.0 M Is this ok [y/N]: y Downloading Packages: (1/2): nfs-utils-1.0.9-70.el5.x86_64.rpm | 409 kB 00:00 (2/2): initscripts-8.45.44-3.0.1.el5.x86_64.rpm | 1.6 MB 00:01 ------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 598 kB/s | 2.0 MB 00:03 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : initscripts 1/4 warning: /etc/sysctl.conf created as /etc/sysctl.conf.rpmnew Updating : nfs-utils 2/4 Cleanup : nfs-utils 3/4 Cleanup : initscripts 4/4 Updated: nfs-utils.x86_64 1:1.0.9-70.el5 Dependency Updated: initscripts.x86_64 0:8.45.44-3.0.1.el5 Complete!
Then I tried the RPC info command again, but no luck!
[root@ovm /]# rpcinfo -p rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
Portmap? Oh, that would explain a lot since NFS apparently requires port mapper service to run.
[root@ovm /]# chkconfig portmap on [root@ovm yum.repos.d]# service portmap start
Try RPC info again. Aha, that did it!
[root@ovm yum.repos.d]# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper
Finally, restart the NFS Service and set it to autostart.
[root@ovm /]# service nfs start Starting NFS services: [ OK ] Starting NFS quotas: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ] [root@ovm /]# chkconfig nfs on
Hope this was helpful!
Cheers!
Maaz Anjum's Blog 
I ran into the same issue for my rhel6 box. I followed your instructions. “portmap” service was not available in my service. Instead Rhel6 has rpcbind service. Once I started rpbcbind service{“service rpcbind start”], I was able to start the nfs service.
Thanks for such a detailed instruction.
Kripa,
I am glad the instructions were helpful and thank you for sharing your fix on RHEL6!
Cheers.
Maaz
Thanks Maaz –
I ran into this same issue setting up Oracle VM Manager/Servers in virtualbox. I was following the documentation here: http://www.oracle.com/technetwork/server-storage/vm/ovm3-demo-vbox-1680215.pdf
Steve
Hi Steve,
I was working through the same document. Thanks for the mention on twitter 🙂
Cheers,
Maaz
Yey! For CentOS 6.5 the service you start/enable before nfs is called “rpcbind”.
Joe,
Thanks for sharing your experience on CentOS!
Cheers,
Maaz
It’s hard to find your articles in google. I found it on 18 spot,
you should build quality backlinks , it will help you to increase traffic.
I know how to help you, just type in google – k2 seo tricks
Can confirm your fix worked on RHEL 5.10. It’s true that RHEL 6 has rpcbind instead. Thanks for the post!
Hi Jim,
I haven’t tried it on RHEL 5.10, but I’d be curious to know whether the solution is the same or different.
Glad it helped you in any case 🙂
Cheers,
Maaz
RHEL 5.10 was identical. I Googled the error and saw your post. I checked portmap and saw it was off, started it and nfs fired right up. Rebooting would have fixed it since in my case portmap was set to “on” in checkconfig. I did a brief RCA and found that an installer script I had been running killed nfs processes as part of its logic. The script failed for an unrelated reason then exited without sending the init.d startup commands. All is well and work is flowing, thanks again.
perfect
Your Article helped me too. Thanks!
Glad it helped PK!
Hi,
When iam restarting the nfs service it showing me
Starting NFS quotas: Cannot register service: RPC: Unable to receive; errno = Connection refused
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
[FAILED]
Starting NFS mountd: [FAILED]
Starting NFS daemon: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
rpc.nfsd: unable to set any sockets for nfsd
===========================================
Even though ifollowed above step’s the portmap can’t restart even please can you help on this.
Regard’s,
Mohan.K
Mohan, what is your OS? Do you have iptables enabled?
You just saved my day!! THANKS!! 🙂
Cheers!
thanks a lot for solution..same issue.. resolved
Thanks for the post
Super clutch. Thanks.
Thank you so much…The solution worked right for me