I'm having trouble setting up NFS between two Suse 9.0 boxes. One is set up as the server and one is set up as the client. When I use Yast runlevel editor:details (expert mode) to start the nfs client I get this error message: /etc/init.d/nfs start returned 1 (unspecified error): Importing Net File System (NFS)mount: RPC: Program not registered ..failed I checked man rpc but: rpc register rpchandle proc Export proc as an RPC callable proc using the server handle rpchandle. Only registered procs can be called by RPC clients. Doesn't help me much. How do I register nfs with rpc? Or is it the other way round? Shouldn't the script that starts nfs in the runlevel editor take care of this? When you start nfs clients using Yast doesn't it just work? Thanks, Jerome
Jerome Lyles
I'm having trouble setting up NFS between two Suse 9.0 boxes. One is set up as the server and one is set up as the client. When I use Yast runlevel editor:details (expert mode) to start the nfs client I get this error message:
/etc/init.d/nfs start returned 1 (unspecified error):
Importing Net File System (NFS)mount: RPC: Program not registered ..failed
It means mountd is not registered by portmapper on the NFS server. IMHO the portmap process must run both on the NFS client and the server. The following is from SUSE 8.2: # /usr/sbin/rpcinfo -p server program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 100021 1 udp 32769 nlockmgr 100021 3 udp 32769 nlockmgr 100021 4 udp 32769 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100005 1 udp 32770 mountd 100005 1 tcp 32769 mountd 100005 2 udp 32770 mountd 100005 2 tcp 32769 mountd 100005 3 udp 32770 mountd 100005 3 tcp 32769 mountd # /usr/sbin/rpcinfo -p client program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 32768 nlockmgr 100021 3 udp 32768 nlockmgr 100021 4 udp 32768 nlockmgr
When you start nfs clients using Yast doesn't it just work?
Yes and no. For instance a firewall may block the ports. -- A.M.
On Friday 06 February 2004 02:52 am, Alexandr Malusek wrote:
Jerome Lyles
writes: I'm having trouble setting up NFS between two Suse 9.0 boxes. One is set up as the server and one is set up as the client. When I use Yast runlevel editor:details (expert mode) to start the nfs client I get this error message:
/etc/init.d/nfs start returned 1 (unspecified error):
Importing Net File System (NFS)mount: RPC: Program not registered ..failed
It means mountd is not registered by portmapper on the NFS server.
IMHO the portmap process must run both on the NFS client and the server. The following is from SUSE 8.2:
# /usr/sbin/rpcinfo -p server
On machine A and B the srvers are running but: # /usr/sbin/rpcinfo -p server rpcinfo: server is unknown host # /usr/sbin/rpcinfo -p client rpcinfo: client is unknown host On machine A nfsserver is running but nfslock is not loaded (Yast says there is potential for conflict if nfs server and nfs-utils are both loaded. Is this true?). On B nfsserver and nfslock are running. The rcportmap status is: running on both machines. Thanks, Jerome
Jerome Lyles
On machine A and B the srvers are running but:
# /usr/sbin/rpcinfo -p server rpcinfo: server is unknown host
The word "server" stands for the hostname of your NFS server. If its name is "A" than use # /usr/sbin/rpcinfo -p A The same for the client.
On machine A nfsserver is running but nfslock is not loaded (Yast says there is potential for conflict if nfs server and nfs-utils are both loaded.
Note that two implementations of the NFS server are available in SUSE 9.0: the userspace and the kernel implementation. The nfs-server*.rpm is the userspace implementation, I suggest you don't use it.
On B nfsserver and nfslock are running. The rcportmap status is: running on both machines.
Don't concentrate on these things, just do what the Adminguide says to do and check the visibility of the NFS services via the "rpcinfo" command. -- A.M.
On Friday 06 February 2004 09:04 am, Jerome Lyles wrote:
On Friday 06 February 2004 02:52 am, Alexandr Malusek wrote:
Jerome Lyles
writes: I'm having trouble setting up NFS between two Suse 9.0 boxes. One is set up as the server and one is set up as the client. When I use Yast runlevel editor:details (expert mode) to start the nfs client I get this error message:
/etc/init.d/nfs start returned 1 (unspecified error):
Importing Net File System (NFS)mount: RPC: Program not registered ..failed
It means mountd is not registered by portmapper on the NFS server.
mountd isn't registering with portmapper and I don't know why. On machine A and B the servers are running but: # /usr/sbin/rpcinfo -p 'server' No remote programs registered. # /usr/sbin/rpcinfo -p 'client' No remote programs registered. /etc/init.d/nfs start Importing Net File System (NFS)mount: RPC: Program not registered
IMHO the portmap process must run both on the NFS client and the server.
The rcportmap status is: running on both machines. OK-the portmapper is running. The servers are running on both machines. But the nfs client cannot find the server because it is not registered. Why not?? "Normally" it would/should be registered with the portmapper and the server running,right? Are there commands to use to find out why 'No remote programs registered' is true (I assume this means the server)? Just in case the problem is here: etc/exports: /home/myhome/ 192.168.0.*(rw,root_squash,sync) etc/host.allow: portmap: 192.168.0.* lockd: 192.168.0.* rquotad: 192.168.0.* mountd: 192.168.0.* statd: 192.168.0.* /etc/hosts.deny: http-rman : ALL EXCEPT LOCAL portmap:ALL lockd:ALL mountd:ALL rquotad:ALL statd:ALL Thanks, Jerome
Jerome Lyles
On machine A and B the servers are running but:
# /usr/sbin/rpcinfo -p 'server' No remote programs registered.
If portmapper is not visible then NFS will not work. You have to get it working first. Run "rpcinfo" on the NFS server: /usr/sbin/rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper The portmapper should be listed (portmap doesn't use access control rules on the localhost). I think the problem is that you use an approach which only experts can use: severely restrict access first and then start the service. An easier approach (highly recommended for beginners) is to start the service first and then gradually restrict the access.
etc/host.allow:
portmap: 192.168.0.*
I don't see this syntax in the "man 5 hosts_access". It doesn't mean it cannot work. Anyway, try portmap: 192.168.0. or portmap 192.168.0.0/255.255.255.0 -- A.M.
On Saturday 07 February 2004 01:53 am, Alexandr Malusek wrote:
Jerome Lyles
writes: On machine A and B the servers are running but:
# /usr/sbin/rpcinfo -p 'server' No remote programs registered.
If portmapper is not visible then NFS will not work. You have to get it working first. Run "rpcinfo" on the NFS server:
I think the problem is that you use an approach which only experts can use: severely restrict access first and then start the service. An easier approach (highly recommended for beginners) is to start the service first and then gradually restrict the access.
This is true. I commented out the restrictions I added in /etc/hosts.deny. Now portmapper is visable to NFS. Thank you very much. It happens that portmap:ALL only allowed localhost access:-). Now I think the only obstacle left is this: # /etc/init.d/nfs start Importing Net File System (NFS)mount: linux:/home/adriel failed, reason given by server: Permission denied failed So I only have a permission problem left I think. Anyone have a solution?
etc/host.allow: portmap: 192.168.0.*
I don't see this syntax in the "man 5 hosts_access". It doesn't mean it cannot work. Anyway, try
portmap: 192.168.0. or portmap 192.168.0.0/255.255.255.0 A.M.
I changed to 192.168.0. in hosts.allow on one of my boxes.
Just a silly question. Can you ping each machine from each other? Yes I can.
Also another gotcha is in /etc/exports file make sure you include a netmask with the ip address. For example this is an entry in my /etc/exports
/home 10.212.32.0/24(rw,sync) 10.212.33.0/24(rw,sync) I changed /etc/exports to: /home/myhome/ 192.168.0.0/24(rw,root_squash,sync) Thanks, Jerome
On Sat, 7 Feb 2004 21:11, Jerome Lyles wrote:
The rcportmap status is: running on both machines.
Just a silly question. Can you ping each machine from each other? I have not totally been across this thread but from the few things that I have seen mentioned it appears that there may be a problem with the network connection between the two computers. Also another gotcha is in /etc/exports file make sure you include a netmask with the ip address. For example this is an entry in my /etc/exports /home 10.212.32.0/24(rw,sync) 10.212.33.0/24(rw,sync) -- Regards, Graham Smith ---------------------------------------------------------
On Saturday 07 February 2004 06:22 am, Graham Smith wrote:
On Sat, 7 Feb 2004 21:11, Jerome Lyles wrote:
The rcportmap status is: running on both machines.
I think the problem is that you use an approach which only experts can use: severely restrict access first and then start the service. An easier approach (highly recommended for beginners) is to start the service first and then gradually restrict the access.
This is the first part of the solution:
Also another gotcha is in /etc/exports file make sure you include a netmask with the ip address. For example this is an entry in my /etc/exports
/home 10.212.32.0/24(rw,sync) 10.212.33.0/24(rw,sync) -- Regards, Graham Smith --------------------------------------------------------- This is the second part of the solution:
When I used a netmask on my /etc/exports entry: /home/myhome 192.168.0.0/24(rw,root-squash,sync) and ran exportfs -ra, the client connected to the server. Thank you all for your help. Jerome
On Friday 06 February 2004 08:24 am, Jerome Lyles wrote:
I'm having trouble setting up NFS between two Suse 9.0 boxes. One is set up as the server and one is set up as the client. When I use Yast runlevel editor:details (expert mode) to start the nfs client I get this error message:
/etc/init.d/nfs start returned 1 (unspecified error):
Importing Net File System (NFS)mount: RPC: Program not registered ..failed
I checked man rpc but:
rpc register rpchandle proc Export proc as an RPC callable proc using the server handle rpchandle. Only registered procs can be called by RPC clients.
Doesn't help me much. How do I register nfs with rpc?
You don't - you simply make sure that the rpc daemon is running. It's called portmap, so rcportmap status will tell you if it's running (on the server and the client. You might possibly have to install it, although it should be a dependency of nfs and nfsserver HTH Dylan
Or is it the other way round? Shouldn't the script that starts nfs in the runlevel editor take care of this? When you start nfs clients using Yast doesn't it just work? Thanks, Jerome
-- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin
participants (4)
-
Alexandr Malusek
-
Dylan
-
Graham Smith
-
Jerome Lyles