The FreeBSD Diary |
(TM) | Providing practical examples since 1998If you buy from Amazon USA, please support us by using this link. |
NFS Portmap: RPC: Program not registered
27 June 2000
|
Over the past 9 months or so, this problem has been a recurring issue.
It would go away only to return at a later date. It was getting to be very
annoying. The crunch came this morning when I opened the XEON
box in order to disconnect a noisy fan on a video card. Don't worry, the card
actually has lots of ventilation already. It has an exchaust fan right beside it
(less than 4mm from the heatsink on the card. When I restarted the box, which acts both as an NFS server and an NFS client, the boot process was paused with the following message:
I also found the following messages in
I mentioned this on IRC, and Unfurl suggested it was an Here's what I had in
Here's what I changed it to:
|
The original problem
27 June 2000
|
Today after I rebooted two boxes, I found that one couldn't remount some
NFS partitions which resided on the other box. During the boot process, the
following message was displayed (it is split into two lines here for readability):Mounting NFS file systemsNFS Portmap: RPC: Program not registered This was on the client box. The server box seemed fine. I pressed control-C to allow the box to continue booting. Then I tried to mount the partitions manually: mount /www/unixathome.org/adsl NFS Portmap: RPC: Program not registered Following some advice, I did the following (but before you do that, see also the next section for more information):
The above process worked. The mount succeeded. Life goes on. |
More information
15 July 2000
|
Each time I reboot the NFS server, I find that the clients can't access
it. In the logs on the client, I find this:nfs server mynfsserver:/path/to/stuff: not responding So on the server I do this: killall -term nfsd nfsd -u -t -n 4 Soon afterwards, I find messages like this in the client: nfs server mynfsserver:/path/to/stuff: is alive again I also noticed that one of my mounts doesn't mount properly. And that mountd was not running on the server. So I started it manually by issuing the command: mountd Then, on the client, I manually mounted the missing volumes. e.g.: # mount -v ducky:/nfs/path /path/to/local/mount/point ducky:/nfs/path on /path/to/local/mount/point (nfs) |