Have you ever seen this in your logs:
10:55:18 [server] nfslock: rpc.statd startup failed
If you have, you might want to check and make sure that you have portmap running
[server][root][~]# service portmap status portmap is stopped
Oppps. Portmap is not running. Let’s check and see if portmap is configured to start at boot?
[server][root][~]# chkconfig --list portmap portmap 0:off 1:off 2:off 3:off 4:off 5:off 6:off
And if it’s not (as is our case), configure it to start at boot:
[server][root][~]# chkconfig portmap on
Ahhhhh, thats more like it. This is how it should look:
[server][root][~]# chkconfig --list portmap portmap 0:off 1:off 2:on 3:on 4:on 5:on 6:off
And crank it up
[server][root][~]# service portmap start Starting portmap: [ OK ]
Now you can make sure it is running
[server][root][~]# service portmap status portmap (pid 15384) is running...
If security is a concern, would you want to start up portmap, turn off rpc.statd, or take steps to secure portmap?
Since portmap keeps a list of what services are running on which ports, connecting machines can use this list.
Of interest: http://tldp.org/HOWTO/NFS-HOWTO/security.html (section 6.1 talks specifically about the portmapper.
Wayne
18 Feb 10 at 8:10 am