LinuxQuestions.org
Review your favorite Linux distribution.
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 09-25-2015, 09:52 PM   #1
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Rep: Reputation: 36
NFS issues in -current?


I recently upgraded my laptop to Slackware64-current. I have multiple NFS shares that I used to be able to mount when I was running 14.1.
I have rc.rpc and rc.nfsd set to executable, but when I try to restart rc.rpc it takes 3-4 minutes to return to the prompt and returns an exit code of 1.
My /etc/fstab:
Code:
192.168.1.103:/home/izzle121/.common /home/izzle121/.common nfs defaults 0 0
My NFS server's /usr/sbin/exportfs:
Code:
/home/izzle121/.common
          192.168.1.0/24
In an effort to figure out what was wrong, I did remove the aaa_elflibs from /etc/slackpkg/blacklist and subsequently ran slackpkg install-new && slackpkg upgrade-all && slackpkg clean-system.
Before I did that, /sbin/rpc.statd wouldn't actually start with an exit code of 130, but since I made the change and rebooted, it will start and run but it won't let me mount the share.
I can also use the -o nolock option to bypass statd, but that isn't optimal for me.
 
Old 09-26-2015, 01:45 PM   #2
Rinndalir
Member
 
Registered: Sep 2015
Posts: 733

Rep: Reputation: Disabled
You restart nfsd on the server? What do server logs say?
 
Old 09-26-2015, 03:11 PM   #3
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
I had not tried that, but all of my other machines running 14.1-stable are able to mount the shares.
 
Old 09-26-2015, 04:01 PM   #4
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by Rinndalir View Post
You restart nfsd on the server? What do server logs say?
Just as I thought, restarting nfs server side accomplished nothing.
I only get a successful mount message when I use the -o nolock,ro options from the -current machine
I can mount/remount all my shares from the 14.1 machines without problems.
 
Old 09-26-2015, 08:25 PM   #5
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Ireland
Distribution: Slackware, Crux, NetBSD
Posts: 1,448

Rep: Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905
Quote:
Originally Posted by slacker1337 View Post
Just as I thought, restarting nfs server side accomplished nothing.
I only get a successful mount message when I use the -o nolock,ro options from the -current machine
I can mount/remount all my shares from the 14.1 machines without problems.
Do you mount the NFS shares over TCP or UDP?
 
Old 09-26-2015, 08:41 PM   #6
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by gezley View Post
Do you mount the NFS shares over TCP or UDP?
Feeling like a newb, but whichever is default.
 
Old 10-01-2015, 09:00 PM   #7
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
gezley,
Here is some output I collected by running "nstat -npl | grep rpc"
Desktop where NFS is operating normally:
Code:
tcp        0      0 0.0.0.0:43936           0.0.0.0:*               LISTEN      803/rpc.statd       
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      799/rpc.portmap     
tcp        0      0 0.0.0.0:601             0.0.0.0:*               LISTEN      845/rpc.rquotad     
tcp        0      0 0.0.0.0:54622           0.0.0.0:*               LISTEN      862/rpc.mountd      
udp        0      0 0.0.0.0:45828           0.0.0.0:*                           803/rpc.statd       
udp        0      0 0.0.0.0:39992           0.0.0.0:*                           862/rpc.mountd      
udp        0      0 0.0.0.0:111             0.0.0.0:*                           799/rpc.portmap     
udp        0      0 127.0.0.1:979           0.0.0.0:*                           803/rpc.statd       
udp        0      0 0.0.0.0:1022            0.0.0.0:*                           845/rpc.rquotad
Laptop which is having issues starting rpc.statd (after a fresh restart of rc.rpc):
Code:
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      592/rpc.portmap     
udp        0      0 0.0.0.0:111             0.0.0.0:*                           592/rpc.portmap
I did note this in /var/log/messages:
Code:
Oct  1 20:56:15 alain rpc.statd[599]: Version 1.3.1 starting
Oct  1 20:56:15 alain sm-notify[600]: Version 1.3.1 starting
Oct  1 20:56:15 alain sm-notify[600]: Already notifying clients; Exiting!
 
Old 10-02-2015, 06:34 AM   #8
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Ireland
Distribution: Slackware, Crux, NetBSD
Posts: 1,448

Rep: Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905
Quote:
Originally Posted by slacker1337 View Post
gezley,
Here is some output I collected by running "nstat -npl | grep rpc"
It's hard to know what's wrong. Is the NFS server running Slackware? There was an update to nfs-utils on -current earlier this year. Perhaps there is a mismatch with NFS on an older Slackware?

Do you have iptables running on the server, perhaps allowing only a limited range within the DHCP scope? The fact that it works when nolock is specified suggests not but it doesn't hurt to clear these things up first.
 
Old 10-02-2015, 07:05 AM   #9
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by gezley View Post
It's hard to know what's wrong. Is the NFS server running Slackware? There was an update to nfs-utils on -current earlier this year. Perhaps there is a mismatch with NFS on an older Slackware?

Do you have iptables running on the server, perhaps allowing only a limited range within the DHCP scope? The fact that it works when nolock is specified suggests not but it doesn't hurt to clear these things up first.
Yes, the NFS server is running Slackware64-14.1. The mismatch concern came to my mind as well, but if that's the case, it will force me to upgrade everything to 14.? at the same time.
I do not have iptables running (I know, but I'm still learning).

I'm not intimately familiar with what exactly each rpc process does, but according to the rc.rpc script, the -nolock option is for cases where statd either doesn't work or you are OK with mounting the shares read-only. Please correct me if I'm wrong.
 
Old 10-02-2015, 09:06 AM   #10
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Ireland
Distribution: Slackware, Crux, NetBSD
Posts: 1,448

Rep: Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905
Quote:
Originally Posted by slacker1337 View Post
My NFS server's /usr/sbin/exportfs:
Code:
/home/izzle121/.common
          192.168.1.0/24
I've just noticed this path - /usr/sbin/exportfs. I assume it's just a typo? You export your shares in /etc/exports .

Might be worth looking at the Slackware docs page just to make sure you have everything right. I haven't done it too often but whenever I have set up NFS on Slackware it's been straightforward with these instructions.

Another thing to check is the kernel config on both server and current:
Code:
grep NFS /boot/config > ~/server-nfs   # do this on server
grep NFS /boot/config > ~/current-nfs  # do this on current
diff server-nfs current-nfs            # now copy both files to current directory and diff
 
Old 10-02-2015, 09:14 AM   #11
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
The /usr/sbin/exportfs was just a way for me to show what is being exported by the server. I do have /etc/exports setup (and usable by every other machine on my network, with exception to the -current build).

I will check the kernel configs when I get home, thanks for the additional guidance!
 
Old 10-02-2015, 11:32 AM   #12
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Ireland
Distribution: Slackware, Crux, NetBSD
Posts: 1,448

Rep: Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905Reputation: 905
Quote:
Originally Posted by slacker1337 View Post
The /usr/sbin/exportfs was just a way for me to show what is being exported by the server.
Sorry, I was on autopilot there!
Quote:
I do have /etc/exports setup (and usable by every other machine on my network, with exception to the -current build).
Yes I do bear that in mind. A couple more things to consider:
a) what happens if you comment out the NFS mount in fstab and mount it manually? If it works, perhaps the network is coming up too late for the fstab entry.
b) If you set up a temporary NFS share on the -current machine can the 14.1 clients connect to it without this trouble?
 
Old 10-03-2015, 09:53 PM   #13
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by gezley View Post
a) what happens if you comment out the NFS mount in fstab and mount it manually? If it works, perhaps the network is coming up too late for the fstab entry.
b) If you set up a temporary NFS share on the -current machine can the 14.1 clients connect to it without this trouble?
A) I have attempted to mount manually with no result and very little feedback from the system.
Code:
sudo mount -v -t nfs eddie:/home/izzle121/.common /home/izzle121/.common/
mount.nfs: timeout set for Sat Oct  3 21:45:58 2015
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

sudo mount -v -t nfs -o nolock,ro eddie:/home/jared/.common /home/jared/.common/
mount.nfs: timeout set for Sat Oct  3 21:49:39 2015
mount.nfs: trying text-based options 'nolock,addr=192.168.1.103'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.103 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.103 prog 100005 vers 3 prot UDP port 34619
eddie:/home/jared/.common on /home/jared/.common type nfs (ro,nolock)
Now the state of the -current machine:
Code:
ps axc|grep rpc.statd
No feedback, statd only runs briefly after restarting rc.rpc, then dies. I've attempted to run "/usr/sbin/rpc.statd -d" manually and seen no success/failure feedback

When I export a file from the -current machine and attempt to mount it from a 14.1 machine:
Code:
sudo mount -v -t nfs alain:/export /mnt/tmp
Password: 
mount.nfs: timeout set for Sat Oct  3 21:52:30 2015
mount.nfs: trying text-based options 'addr=192.168.1.107'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered

mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered

mount.nfs: requested NFS version or transport protocol is not supported
 
Old 10-03-2015, 09:54 PM   #14
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Original Poster
Rep: Reputation: 36
I was thinking it might be a problem with nfs-utils, so I attempted to rollback to version 1.2.8 with the same result. I'm suspicious now that some dependency is broken on my system, but I'm unsure what exactly the dependencies for nfs-utils would be, or how to find it.
 
  


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
X11 forwarding and nfs mounting in -current iiv Slackware 3 11-22-2007 02:39 PM
nfs and portmap of 5/17 broken -current TNWestTex Slackware 1 05-21-2007 06:06 PM
NFS issues noir911 Linux - Software 3 09-12-2006 06:33 AM
nfs issues cwwilson721 Slackware 4 05-12-2006 03:29 AM
Slack current NFS install lancest Slackware 2 11-26-2002 06:47 AM

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

All times are GMT -5. The time now is 12:38 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