nfs install fails manual mounting remote share

dohpaz · 05-03-2007, 11:29 PM

I have installed Slackware using NFS previously but now I can't. The nfs server machine which I used successfully before, has the following config files:

/etc/exports:

Code:

/mnt/cdrom 192.168.1.0/24(ro,no_subtree_check)

/etc/hosts.allow:

Code:

portmap: 192.168.1.0/24
rquotad: 192.168.1.1 , 192.168.1.2
mountd: 192.168.1.1 , 192.168.1.2

ps -A shows that nfsd,portmap,statd,quotas, and lockd are running

running exportfs command reveals:

Code:

/mnt/cdrom    192.168.1.0/24

I am booting nfs client from slackware 11 bare.i,install.1,install.2 I then
load pcmcia.dsk and network.dsk which gets my 3com nic up and running. I can
then run:

Code:

ifconfig eth0 192.168.1.2 up

and ping my router and the nfs server succesfully.

I then run /sbin/rpc.portmap then mkdir /mount
mount 192.168.1.101:/mnt/cdrom /mount fails with the following error:

Code:

mount: RPC: Program not registered

A google search revealed that this could be due to rpc.portmap not running but ps -A shows that it is...:

Code:

ps -A |grep rpc
 2125 ?        00:00:00 rpc.portmap
 2134 ?        00:00:00 rpc.statd
 2137 ?        00:00:00 rpc.rquotad
 2140 ?        00:00:00 rpciod/0
 2150 ?        00:00:00 rpc.mountd

also the command rpcinfo -p on the server shows:

Code:

rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp    617  status
    100024    1   tcp    620  status
    100011    1   udp    619  rquotad
    100011    2   udp    619  rquotad
    100011    1   tcp    622  rquotad
    100011    2   tcp    622  rquotad
    100021    1   udp   1025  nlockmgr
    100021    3   udp   1025  nlockmgr
    100021    4   udp   1025  nlockmgr
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   tcp   4451  nlockmgr
    100021    3   tcp   4451  nlockmgr
    100021    4   tcp   4451  nlockmgr
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100005    1   udp    630  mountd
    100005    1   tcp    633  mountd
    100005    2   udp    630  mountd
    100005    2   tcp    633  mountd
    100005    3   udp    630  mountd
    100005    3   tcp    633  mountd

How can I further troubleshoot this?
/var/log/messages didn't have any usefull info.

I use shorewall firewall but I have disabled it with chmod -x /etc/rc.d/rc.firewall.

dohpaz · 05-03-2007, 11:32 PM

I just checked /var/log/messages on the client and found the following:

Code:

auth.err portmap[692]: Cannot bind udp: address already in use

hollywoodb · 05-03-2007, 11:38 PM

I'm not sure on that UDP error, but a couple things:

IF we're talking NFSv4,
then /etc/exports on the server should contain "fsid=0" or simliar in the options.
hosts.allow on the server should reference nfsd, and nfsd should be running, i.e.: nfsd: 192.168.1.
on the client, there should be some type of nfs service that runs not only the rpc.* that you show, but rpc.idmapd as well.

IF we're not talking NFSv4
you shouldn't be running rpc.* from the commandline, there should be an initscript or service that handles these and their PID files.

Hope this helps, I really have very little experience pre-NFSv4

dohpaz · 05-04-2007, 12:00 PM

In the nfs howto under the troubleshooting section
http://nfs.sourceforge.net/nfs-howto/ar01s07.html

It indicates that the error I receive means that the client does not detect NFS running on the server.

It says to check the server with rpcinfo -p which i did(see above)
and also to run rpcinfo -p from the client. Well the laptop client
booted from bare.i does not have that command so I copied it onto a floppy and when I run it I get:

Code:

rpcinfo -p

Program  Vers   Proto    Port
100000     2      udp       111
100000     2      tcp       111

and

192.168.0.102 is the ip of nfs server)

Code:

rpcinfo -p 192.168.0.102

No remote programs registered

The troubleshooting section says to check your hosts.allow and exports files which I did and then decided to change 192.168.0.0/24 to the ip of the client. Bingo that did it.