Rpc error program not registered

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I’m trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs — /majid nfs — yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to… (1 Reply)

Discussion started by: Hiroshi

2. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared,
By the way I did the searches, since i haven’t found that someone wrote a script like this in the past, I’m sure it will serve more people.

The scenario as follow:
An NFS Client with Daily CRON , running bash script… (4 Replies)

Discussion started by: Brian.t

3. Solaris

nfs mount: RPC: Rpcbind failure — RPC: Timed out

Fails to mount the server (10.125.224.22) during installation of a software on client, throwing the below error:

nfs mount: 10.125.224.22: : RPC: Rpcbind failure — RPC: Timed out
nfs mount: retrying: /cdrom

This happened after complete shutdown of the lab. The server came up fine but most… (1 Reply)

Discussion started by: frintocf

4. Red Hat

Not able to mount NFS share on client side

When i tried to mount the nfs i see this error message
mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount
mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied

and the /etc/exports file in the host side looks like this

/remote/proj1 … (12 Replies)

Discussion started by: srinathk

5. AIX

can not mount from aix client to linux nfs server

Hi,

I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error:

# mount 128.127.11.121:/aix /to_be_del
mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper
failure — RPC: 1832-008 Timed out
mount: retrying… (1 Reply)

Discussion started by: victorcheung

6. UNIX for Advanced & Expert Users

Unusual NFS mount problem on only ONE client: Red Hat WS Rel 3

This is an unusual situation where I have an NFS server currently serving out MULTIPLE clients over several variants of Linux and UNIX successfully (world permissions) except for a SINGLE client. Even the other Linux (SuSE) clients in the same room are mounting successfully with defaults without… (6 Replies)

Discussion started by: neelpert1

7. Shell Programming and Scripting

NFS client Mount script after boot

Hi,

I have 12 AIX P series servers. One has the NFS DB2data and the others are client mounts. NFS is not in /etc/filesystem because if NFS DB2data not up the client takes 7+ minutes to give up on nfsmnt and boot up.
I’d like to check that nfs is up, then do the client mount all from a startup… (0 Replies)

Discussion started by: sv2xs

8. UNIX for Dummies Questions & Answers

can not get netapp to mount RPC Not registered error

getting «NFS mount: netapp : RPC: Program not registered» error

searched the site but none of the fixes from previous threads are helping (2 Replies)

Discussion started by: calamine

9. UNIX for Advanced & Expert Users

clnttcp_create: RPC program not registered

s/o=SCO 5.05 openserver

hi, i have a problem with a mount between 2 servers

i can see the mounted files, but i can�t open it if the file is a *.dbf,

if i try to a «dbf» file with fox for unix the error is (the system has reached the maximum number of blocks)

mount -f NFS… (1 Reply)

Discussion started by: jav_v

10. UNIX for Dummies Questions & Answers

«rpc program not registered»??

Hello all,

When I shut down my X86/Solaris 8, I get the following
messages on the console:

«rpc program not registered «……

What is mean?why?May someone can tell me

Thanks in advance. (1 Reply)

Discussion started by: Lee

• 
• Forum
• The Ubuntu Forum Community
• Ubuntu Specialised Support
• Ubuntu Servers, Cloud and Juju
• Server Platforms
• [ubuntu] NFS setup problem (RPC not registered)

1. NFS setup problem (RPC not registered)
   

   Hello,

   I’ve followed several guides and am trying to get NFS working on my local network.

   For starters, I think I should be able to NFS mount a drive on the server (192.168.1.65) TO the server. From there I’ll work with another client (currently 192.168.1.80)

   Code:

   $cat /etc/exports
   /media 192.168.1.0/24(rw,no_subtree_check)
   
   
   $cat /etc/hosts.deny
   portmap mountd nfsd statd lockd rquotad : ALL
   
   
   $cat /etc/hosts.allow
   ALL : 192.168.1.65/255.255.255.0, 192.168.1.80/255.255.255.0

   ran

   Code:

   $sudo exportfs -ra
   $sudo /etc/init.d/nfs-kernel-server restart
   $sudo /etc/init.d/portmap restart
   
   
   $sudo mount 192.168.1.65:/media blah
   mount.nfs: mount to NFS server '192.168.1.65:/media' failed: RPC Error: Program not registered

   from the client:

   Code:

   $sudo mount 192.168.1.65:/media blah
   mount.nfs: mount to NFS server '192.168.1.65:/media' failed: RPC Error: Program not registered

   <tears hair out>

   The guides I’ve read seem simple, so I must be missing something easy. Can’t figure it out, so I’m looking for help after googling for 2 hours. Thanks

   ---

2. Re: NFS setup problem (RPC not registered)
   

   do you see NFS if you query with rpcinfo -p

   ---

3. Re: NFS setup problem (RPC not registered)
   

   Maybe try in /etc/hosts.allow:

   Code:

   ALL:192.168.1.65
   ALL:192.168.1.80

   ---

4. Re: NFS setup problem (RPC not registered)
   

   If you use UFW firewall make sure that you’r clients have the permission to connect on server on all ports.

   ---

5. Re: NFS setup problem (RPC not registered)
   

   Code:

   sudo apt-get update
   sudo apt-get install portmap

   ---

6. Re: NFS setup problem (RPC not registered)
   

   Oh yes, after editing the exports file, have you:

   Code:

   sudo exportfs -a
   sudo /etc/init.d/nfs-kernel-server restart
   sudo /etc/init.d/portmap restart

   ?

   ---

7. Re: NFS setup problem (RPC not registered)
   

   Originally Posted by jgarner
   

   do you see NFS if you query with rpcinfo -p

   yes

   Originally Posted by Jive Turkey
   

   Maybe try in /etc/hosts.allow:

   Code:

   ALL:192.168.1.65
   ALL:192.168.1.80

   no difference

   Originally Posted by ene_dene
   

   If you use UFW firewall make sure that you’r clients have the permission to connect on server on all ports.

   don’t know what UFW is, probably not (?) using it

   Originally Posted by KiLaHuRtZ
   

   Code:

   sudo apt-get update
   sudo apt-get install portmap

   up to date

   Originally Posted by ene_dene
   

   Oh yes, after editing the exports file, have you:

   Code:

   sudo exportfs -a
   sudo /etc/init.d/nfs-kernel-server restart
   sudo /etc/init.d/portmap restart

   ?

   yes

   Now I see:

   Code:

   $ sudo mount 192.168.1.65:/media blah -v
   mount: no type was given - I'll assume nfs because of the colon
   mount.nfs: timeout set for Sat May  1 22:57:09 2010
   mount.nfs: text-based options: 'addr=192.168.1.65'
   mount.nfs: mount(2): Input/output error
   mount.nfs: mount system call failed

   but if I tail dmesg, I see:

   Code:

   [11534.140022] rpcbind: server 192.168.1.65 not responding, timed out

   which is very different from before. Now running from the client machine (192.168.1.80)

   Code:

   $ sudo mount 192.168.1.65:/media tmp/ -v
   mount: no type was given - I'll assume nfs because of the colon
   mount: wrong fs type, bad option, bad superblock on 192.168.1.65:/media,
          missing codepage or helper program, or other error
          (for several filesystems (e.g. nfs, cifs) you might
          need a /sbin/mount.<type> helper program)
          In some cases useful info is found in syslog - try
          dmesg | tail  or so

   this just seems like a b0rked mount, though

   ---

8. Re: NFS setup problem (RPC not registered)
   

   I don’t know where the problem is, but here is how I would do it.
   Assumptions:
   server address: 192.168.1.65
   client address: 192.168.1.80

   On a server I’d install portmap, nfs-kernel-server.
   Edited the /etc/exports file and put:

   Code:

   /media	192.168.0.2(rw,sync,no_subtree_check)

   then exportfs -a as you have done, restart portmap and nfs-kernel-server as you have done.
   Now on server you need to check if your UFW firewall is running (check this first, before you did anything, maybe this is the problem). You do this by:
   If the output is:
   Than you can, either disable the firewall (sudo ufw disable), which I wouldn’t do, or you can allow all traffic from local network to server by:

   Code:

   sudo ufw allow from 192.168.1.0/24

   To me, it’s easier with firewall anyway, than with host.allow, deny. If you use firewall you don’t need to put anything in host.allow, deny.

   Now, you don’t have to mount anything on server if you just want to share /media folder.

   On client, you have to have installed nfs-client. Then you just mount the drive:

   Code:

   sudo mount -t nfs 192.168.1.80:/media /folder_of_your_choice

   Of course, that folder needs to exist on client, and it probably needs to be empty.

   Btw, I have it configured in shown way, and it worked with Ubuntu server 9.10 and now works with Ubuntu server 10.04.

   ---

9. Re: NFS setup problem (RPC not registered)
   

   I appreciate the clear responses, and it seems that this should be no problem from the descriptions.

   ufw ISN’T running

   Code:

   $ sudo ufw status
   Status: inactive

   after running (on the client):

   Code:

   $ sudo mount 192.168.1.65:/media blah -v
   mount: no type was given - I'll assume nfs because of the colon
   mount.nfs: timeout set for Sun May  2 11:44:24 2010
   mount.nfs: text-based options: 'addr=192.168.1.65'
   mount.nfs: mount(2): Input/output error
   mount.nfs: mount system call failed

   from the server I see this:

   Code:

   tail dmesg
   [57386.570805] nfsd: last server has exited, flushing export cache
   [57387.795916] svc: failed to register lockdv1 RPC service (errno 97).
   [57387.797685] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
   [57387.797712] NFSD: starting 90-second grace period

   I also note that it doesn’t matter what I choose for the SOURCE directory to mount
   192.168.1.65:/home
   gives the same output as
   192.168.1.65:/media

   fyi:

   Code:

   $ sudo exportfs -rva
   exporting 192.168.0.2:/media

   maybe I’ll upgrade to 10.04, wipe if off the server and start over cleanly. Seems like it must be something silly

   ---

10. Re: NFS setup problem (RPC not registered)
    

    I’m sorry, but I don’t know where the problem is. Perhaps someone with more experience with NFS errors could be of better help.

    I hope upgrading will change something.

    ---