LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-15-2006, 09:42 AM   #1
SaintsOfTheDiamond
Member
 
Registered: Jan 2006
Location: Lexington, KY
Distribution: Arch and a little Slack
Posts: 139

Rep: Reputation: 15
NFS client ..


I've read all the NFS threads that have been popping up lately and none of them seem to help me resolve my current "issues". I tried following this tutorial here at LQ and the documentation on the NFS page and I'm still having problems. I got the server end working no problem with a basic installation from the Slack 10.2 discs I made a few weeks back. This is what I get on the server box with rpcinfo -p
Code:
    program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100011    1   udp    665  rquotad
    100011    2   udp    665  rquotad
    100011    1   tcp    668  rquotad
    100011    2   tcp    668  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp   1026  nlockmgr
    100021    3   udp   1026  nlockmgr
    100021    4   udp   1026  nlockmgr
    100005    1   udp    677  mountd
    100005    1   tcp    680  mountd
    100005    2   udp    677  mountd
    100005    2   tcp    680  mountd
    100005    3   udp    677  mountd
    100005    3   tcp    680  mountd
    100024    1   udp    683  status
    100024    1   tcp    686  status
Which should be good to go no? On my main box that I'm using as the client (I'm only sending files from my main box to the server box since its my webserver experiment so there is no server running on this end) I get:
Code:
    program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
I installed Slack on both boxes from the same discs and the only thing I didn't install on my main box (the one that's not working) was the Apache stuff. Doing an slocate on --> nfsd, lockd, statd, mountd, and rquotad returns nothing.
 
Old 03-15-2006, 04:44 PM   #2
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
What are the "issues"?
Did you export any directories on the server?
Did you mount it from the client?
Any error-messages? In the system-logs...?
slocate only works if you ran "updatedb" - and it would only give the location of the file - it doesn't say anything about if a service is running or not - but portmap running on the client would be enough.
 
Old 03-15-2006, 08:06 PM   #3
SaintsOfTheDiamond
Member
 
Registered: Jan 2006
Location: Lexington, KY
Distribution: Arch and a little Slack
Posts: 139

Original Poster
Rep: Reputation: 15
Hehe .. sorry .. guess I gave all the background and not my problem. I couldn't find any of the services daemons anywhere on my computer, so that's what I was using slocate for, and I do keep it updated by running updatedb at least once a day. I found the portmap daemon and the portmap service is running on the box on startup, I just can't find any of the other ones the NFS site says I need. When I try to mount the other computer with:
Code:
mount -t nfs 192.168.1.101:/var/www /mnt/oldSlacky
I get this:
Code:
mount: RPC: Authentication error; why = Failed (unspecified error)
/etc/export on the server box looks like this (192.168.1.100 is the IP of my main box -- the one that won't connect)
Code:
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.

/var/www             192.168.1.100(rw)

# End of Exports file
/etc/hosts.allow is:
Code:
portmap: 192.168.1.100

lockd: 192.168.1.100
rquotad: 192.168.1.100
mountd: 192.168.100
statd: 192.168.1.100
/etc/hosts.deny is:
Code:
portmap:ALL

lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL
Sorry for the mess of code, but I thought that'd help more than me trying to describe the problem. I guess what has me confused is that I installed Slack on both from the same CDs and I've actually pruned down the server box since it's just a webserver on a really old box and finding those daemons and starting those services was a piece of cake.
 
Old 03-15-2006, 09:55 PM   #4
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
Code:
iptables -F
on the client side/or server...
 
Old 03-15-2006, 11:11 PM   #5
SaintsOfTheDiamond
Member
 
Registered: Jan 2006
Location: Lexington, KY
Distribution: Arch and a little Slack
Posts: 139

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Mr_C
Code:
iptables -F
on the client side/or server...
Did it on both .. still nothing.
 
Old 03-15-2006, 11:52 PM   #6
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
/usr/doc/Linux-HOWTOs/NFS-HOWTO

So far it seems you have setup everything correctly. I had an access denied problem once with rpc and flushing the iptables solved it. In your case...hmmm I'm looking.
 
Old 03-16-2006, 12:00 AM   #7
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
HOLD THE PHONE!

your /etc/exports on your server should be
/var/www 192.168.1.101(rw)

Last edited by Mr_C; 03-16-2006 at 12:07 AM.
 
Old 03-16-2006, 03:01 AM   #8
SaintsOfTheDiamond
Member
 
Registered: Jan 2006
Location: Lexington, KY
Distribution: Arch and a little Slack
Posts: 139

Original Poster
Rep: Reputation: 15
According to the NFS link in my first post:

Quote:
An entry in /etc/exports will typically look like this:
Code:
directory machine1(option11,option12) machine2(option21,option22)
where directory [is] the directory that you want to share. It may be an entire volume though it need not be. If you share a directory, then all directories under it within the same file system will be shared as well.

machine1 and machine2 [are] client machines that will have access to the directory. The machines may be listed by their DNS address or their IP address (e.g., machine.company.com or 192.168.0.8). Using IP addresses is more reliable and more secure. If you need to use DNS addresses, and they do not seem to be resolving to the right machine, see Section 7.3.
And changing it to the IP of the server didn't fix it either. The only service that's running on the client is the portmap daemon. Is that really all I need to have running? The NFS page said there were 3 services I needed running in addition to portmap.
 
Old 03-16-2006, 01:10 PM   #9
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
hmm well the last time I set it up, portmap and nfs were the only related daemons I had running on the client side. So you probably need nfs

Ok yeah you're right about the ip in the /etc/exports <so how on earth did it work for me???>
 
Old 03-17-2006, 06:39 AM   #10
SaintsOfTheDiamond
Member
 
Registered: Jan 2006
Location: Lexington, KY
Distribution: Arch and a little Slack
Posts: 139

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Mr_C
hmm well the last time I set it up, portmap and nfs were the only related daemons I had running on the client side. So you probably need nfs
Where can I get that? I downloaded the latest nfs-utils tarball from the NFS site and after having to track down and intall three different dependencies I got the feeling I was doing something wrong. I still don't understand why it was so easy to get the server services running without any dependency or any of the other issues I'm having with the client.
 
Old 03-17-2006, 12:01 PM   #11
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
isn't that package like on the slackware cds?
 
Old 03-18-2006, 04:37 PM   #12
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
Code:
/share/1 192.168.1.254/22(rw,nohide,async)
Try allowing to your whole net instead of just one IP.
 
Old 03-19-2006, 12:29 PM   #13
SaintsOfTheDiamond
Member
 
Registered: Jan 2006
Location: Lexington, KY
Distribution: Arch and a little Slack
Posts: 139

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Shade
Code:
/share/1 192.168.1.254/22(rw,nohide,async)
Try allowing to your whole net instead of just one IP.
I tried that and it didn't work.

I just installed the nfs-utils from my Slack discs and I still get the same error message when I try to mount it on the client side. Here is the output of ps aux from the client logged in as root right after a reboot.
Code:
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  2.6  0.0    600   244 ?        S    12:11   0:04 init [3]  
root         2  0.0  0.0      0     0 ?        S    12:11   0:00 [keventd]
root         3  0.0  0.0      0     0 ?        SN   12:11   0:00 [ksoftirqd_CPU0]
root         4  0.0  0.0      0     0 ?        S    12:11   0:00 [kswapd]
root         5  0.0  0.0      0     0 ?        S    12:11   0:00 [bdflush]
root         6  0.0  0.0      0     0 ?        S    12:11   0:00 [kupdated]
root        10  0.0  0.0      0     0 ?        S<   12:11   0:00 [mdrecoveryd]
root        11  0.0  0.0      0     0 ?        S    12:11   0:00 [kreiserfsd]
root        66  0.0  0.0   1428   592 ?        Ss   12:11   0:00 /usr/sbin/syslogd
root        69  0.0  0.0   1384   452 ?        Ss   12:11   0:00 /usr/sbin/klogd -c 3 -x
root       179  0.0  0.0   1384   456 ?        S<s  12:11   0:00 udevd
root       244  0.0  0.0      0     0 ?        S    12:11   0:00 [knodemgrd_0]
root       345  0.0  0.0      0     0 ?        S    12:11   0:00 [khubd]
bin       3599  0.0  0.0   1596   608 ?        Ss   12:11   0:00 /sbin/rpc.portmap
root      3603  0.0  0.0   1552   712 ?        Ss   12:11   0:00 /usr/sbin/rpc.statd
root      3612  0.0  0.0   1412   508 ?        Ss   12:12   0:00 /usr/sbin/inetd
root      3616  0.0  0.1   3280  1476 ?        Ss   12:12   0:00 /usr/sbin/sshd
root      3627  0.0  0.0   1576   588 ?        S    12:12   0:00 /usr/sbin/crond -l10
root      3640  0.0  0.0   1424   516 ?        Ss   12:12   0:00 /usr/sbin/gpm -m /dev/mouse -t imps2
root      3642  0.1  0.1   2748  1696 tty1     Ss   12:12   0:00 -bash
root      3643  0.0  0.0   1376   480 tty2     Ss+  12:12   0:00 /sbin/agetty 38400 tty2 linux
root      3644  0.0  0.0   1376   480 tty3     Ss+  12:12   0:00 /sbin/agetty 38400 tty3 linux
root      3645  0.0  0.0   1376   480 tty4     Ss+  12:12   0:00 /sbin/agetty 38400 tty4 linux
root      3646  0.0  0.0   1376   480 tty5     Ss+  12:12   0:00 /sbin/agetty 38400 tty5 linux
root      3647  0.0  0.0   1376   480 tty6     Ss+  12:12   0:00 /sbin/agetty 38400 tty6 linux
root      3688  0.0  0.0   2568   892 tty1     R+   12:14   0:00 ps aux
rpc.lockd, rpc.statd, rpc.mountd, and rpc.portmap are all -rwxr-xrwx in the /usr/sbin directory so according to the NFS site I should be good to go, right?
 
Old 03-19-2006, 01:06 PM   #14
raypen
Member
 
Registered: Jun 2002
Location: Midwest
Distribution: Slackware
Posts: 365

Rep: Reputation: 30
Quote:
mount: RPC: Authentication error; why = Failed (unspecified error)
Have you tried:

Quote:
/var/www 192.168.1.100(sync,rw,no_root_squash)
with

Quote:
mount -t nfs 192.168.1.101:/var/www /mnt/oldSlacky
 
Old 03-19-2006, 06:52 PM   #15
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
No offence, just asking: how does no_root_squash (aka nobody) affect the ability to authenticate?

I'm a bit stumpted now...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
SUSE NFS client can't detect an NFS server RedBoot SUSE / openSUSE 4 01-20-2009 12:56 AM
NFS client = Linux, NFS server = Mac OS X Tiger --> Hell of a problem make Linux - Networking 9 03-10-2006 06:16 AM
nfs client on knoppix 3.9 - problem mounting nfs drive Rod Butcher Linux - Networking 1 09-21-2005 05:18 AM
SuSE 9.0 NFS client with RHL 7.3 NFS server ocjacob Linux - Networking 0 02-01-2005 02:01 PM
nfs client should it use tcp or udp to nfs serve rportmapper andersonas Linux - Networking 2 06-30-2004 01:05 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration