My first attempt to connect resulted in this message:
# mount fred:/usr/ports/distfiles /mnt
NFS Portmap: RPC: Port mapper failure - RPC: Timed out
I cleared out my firewall rules on the NFS server and tried again. Note: the NFS
server is a test box and the firewall rules were not necessary. Don't just clear out
your firewall rules unless you are aware of the implications of doing so.
My next attempt resulted in this:
# mount fred:/usr/ports/distfiles /mnt
nfs: can't access /usr/ports/distfiles: Permission denied
I checked my logs and found this:
mountd[42593]: mount request denied from 192.168.0.10 for
/nzmirror/ports/distfiles
Ahhh, yes, I remember now. This box actually has a lot of symlinks on it
because it contains three disks. Look at this:
# ls -ld /usr/ports
lrwxr-xr-x 1 root wheel 16 Dec 24 20:21 /usr/ports -> /nzmirror/ports/
As you can see, the actual physical pathname is something different from what I was
supplying in the exports file. And if you check man exports, you'll see
that symbolic links are not permitted. The following is from the third paragraph
under DESCRIPTION:
The pathnames must not have any symbolic links in them and
should not have any "." or ".." components.
Well, that explains that. So I changed /etc/exports on the server to
contain this:
/nzmirror/ports/distfiles 192.168.0.10
Remember that after making changes to /etc/exports, you should hup mountd:
killall -hup mountd
On the client, I tried that mount again:
mount fred:/nzmirror/ports/distfiles /mnt
The next problem I encountered was a permissions issue:
[root@ducky:/mnt] # mkdir temp
mkdir: temp: Permission denied
I tried many things to resolve this. Eventually it went away. I have no
idea why. Sorry.
6 May 2000
I've just experience a situationwhich may explain the above problem which just "went
away". When I was writing Tranferring
websites/users from one box to another I had this in my exports on the server:
/usr/home/www 192.168.0.78
But this was how I was trying to mount it on the client:
# mount -v ducky:/usr/local/www /mnt
nfs: can't access /usr/local/www: Permission denied
The problem is the pathname. Note that the exports contains "home" but
the mount contains "local". Trying to mount a non-existant export will
give you a plain simple error like that. Be sure to check the basics such as that.
4 October 2000
I was rebooting a NFS client when I spotted this message on the console:
nfs: bad MNT RPC: RPC: Timed out
This message repeated several times. I checked the NFS server:
# showmount -e
RPC: Timed out
showmount: can't do exports rpc
So I restarted mountd and tried again:
# killall -term mountd
# mountd
# showmount -e
Exports list on localhost:
/usr/home/www/ 10.0.0.1
/usr/home/justine 10.0.0.1
/usr/home/eimi 10.0.0.1
/usr/home/chrissy 10.0.0.1
But these messages kept repeating on the client:
nfs: bad MNT RPC: RPC: Timed out
I pressed CONTROL-C on the client's console. The client then completed the boot
process. But no NFS volumes were mounted.
So I mounted them manually, one at a time. I have no idea what caused this error.
If you do, please add your comments.
5 October 2000
I figured it out. It was a problem on the server. After another reboot
of the client, I found that the volumes were again not mounted. So I mounted them by
hand. But I found one volume which could not be mounted. I had forgotten that
this client mounted NFS volumes from two different servers. I went to the other NFS
server, I killed mountd and nfsd and then restarted them.
Then the volumes mounted properly on the client.
18 June 2004
Today I encounted this error for the first time. I was compiling a
kernel on my fast box and while I was waiting
I set up the slow box. I did this:
$ mount polo:/usr/src /usr/src
polo:/usr/src: RPCPROG_MNT: RPC: Authentication error; why = Client credential too weak
That confused me. I checked /var/log/messageson the NFS server:
mountd[95]: mount request from 10.0.0.20 from unprivileged port
Ahhh! I wasn't root when I tried to mount! I su'd to root, and all was well.
|
