Date: Thu, 11 Dec 2003 22:06:49 +0900 From: Rob <nospam@users.sourceforge.net> To: freebsd-questions@freebsd.org Subject: NFS problem at boot-up: "nfsd: RPCPROG_NFS: RPC: Port mapperfailure - RPC: Unable to send" Message-ID: <3FD86BE9.1080904@users.sourceforge.net>
next in thread | raw e-mail | index | archive | help
Hi,
All my PCs are running up-to-date FreeBSD-stable.
I had set up an NFS server (800 MHz) and client (500 MHz),
which was all working fine. At boot-up it nfs-mounts two nfs file systems.
Today I replaced the client 500 MHz with a 2 GHz Pentium 4 PC.
Now the client gives the following during boot:
--------------------------------------------------------
[...]
Doing initial network setup: hostname.
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 147.47.254.184 netmask 0xffffff00 broadcast 147.47.254.255
inet6 fe80::2a0:b0ff:fe0e:3a95%rl0 prefixlen 64 tentative scopeid 0x1
ether 00:a0:b0:0e:3a:95
media: Ethernet 10baseT/UTP
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
add net default: gateway 147.47.254.1
Additional routing options: TCP keepalive=YES.
Routing daemons:.
Mounting NFS file systems:lahaye:/usr/ports: nfsd: RPCPROG_NFS: RPC: Port mapper
failure - RPC: Unable to send
.
Additional daemons: syslogd.
Doing additional network setup: ntpdate portmap.
Starting final network daemons: nfsiod NFS access cache time=2.
[...etc...]
--------------------------------------------------------
There is the "Mounting NFS file systems:" for a long while before the RPC message
comes. Strangely enough, the nfs file system is mounted at the end of the boot-up;
so why is there this RPC message and the long wait for nfs?
I have no clue what's going on here and have also no idea in what direction I should
go for solving this. Any hints?
Thanks,
Rob.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FD86BE9.1080904>