plugout.net

Posted: **Mon Oct 14, 2013 6:13 pm**

After upgrading, I can no longer access my ns2 via nfs from my Raspberry pi.
I checked /etc/exports and everything looks fine.
Can someone confirm that nfs still works or how I can troubleshoot the matter further?

Posted: **Thu Oct 17, 2013 8:08 am**

Oh is that the problem i am having? I had also reinstalled Ubuntu and forgot to backup my fstab NAS mount setting and haven't been able to get it working since. I presumed my syntax was incorrect.

In the meantime i mounted with SFTP but i want to reconnect locally with NFS.

Posted: **Thu Oct 17, 2013 9:20 am**

Sorry nerg,

I overlooked your post (several posts in the same time)

Maybe there is a bug with the additional exports file. Seems that its contents is no longer included in the main exports file

Could you confirm me that you use only this options to set nfs access?

If yes, temporarily you can try to use the client Ip to do the same thing

Posted: **Thu Oct 17, 2013 12:12 pm**

After some more testing,there is no bug with the additional exports file :-D

So to find what happens
* Check if the nfs server is really running

Code: Select all: ps axf|grep usr/sbin|grep -E rpc\|port\|nfsd|grep -v grep

and its output must be

Code: Select all: 32059 ? S 0:00 \_ [nfsd] 902 ? Ss 0:00 /usr/sbin/portmap 32053 ? Ss 0:00 /usr/sbin/rpc.mountd 32055 ? Ss 0:00 /usr/sbin/rpc.statd

and in NFS menu you should see your selected NFS folders in the 'NFS server's export list' area

Posted: **Sun Nov 17, 2013 5:01 pm**

Thank you Jocko,

I got the following output:
983 ? Ss 0:00 /usr/sbin/portmap
1021 ? Ss 0:00 /usr/sbin/rpc.mountd
1023 ? Ss 0:00 /usr/sbin/rpc.statd

That's one line short. What am I missing?

Posted: **Mon Nov 18, 2013 4:53 pm**

Hi nerg

I made a mistake with the command. You should have a line with the daemon nsfd like this

19469 ? S 0:00 \_ [nfsd]

so read directly the output of the command

Code: Select all: ps axf

Previously, I pretty had the same issue and I apparently fixed it by removing some pid files (I am not sure because I don't succeed to reproduce the bug)

So stop the NFS server and post the output of

Code: Select all: ls -al /var/run/

Posted: **Tue Nov 19, 2013 4:48 pm**

Jocko wrote:So stop the NFS server and post the output of
Code: Select all
ls -al /var/run/

Ok, here's the output:

Code: Select all: lrwxrwxrwx 1 root root 18 2013-11-17 20:53 /var/run -> /rw_fs/tmp/var/run

Oh, and thanks for this wonderful project. Will donate shortly.

Posted: **Tue Nov 19, 2013 4:53 pm**

Hi nerg

Oups :dry you need to use the real path so do

Code: Select all: ls -al /rw_fs/tmp/var/run

Posted: **Wed Nov 20, 2013 6:01 pm**

Code: Select all: root@fvdwsl-base:/ # ls -al /rw_fs/tmp/var/run total 44 drwxrwxrwx 3 nobody nobody 4096 2013-11-19 19:17 . drwxr-xr-x 8 root root 4096 2013-11-19 21:16 .. -rw-r--r-- 1 root root 4 2013-11-19 19:17 dropbear.pid -rw------- 1 nobody root 85 2013-11-19 21:16 .htpasswd -rw-r--r-- 1 root root 4 2013-11-19 19:16 httpd.pid drwxr-xr-x 2 nobody nobody 4096 2013-11-19 19:17 lock -rw-r--r-- 1 root root 4 2013-11-19 21:16 noflushd.pid -rw------- 1 root root 382 2013-11-19 19:17 portmap_mapping -rw-r--r-- 1 root root 4 2013-11-19 19:17 rpc.statd.pid -rw------- 1 root root 4 2013-11-19 19:17 sm-notify.pid -rw-r--r-- 1 root root 384 2013-11-20 19:50 utmp

Posted: **Wed Nov 20, 2013 6:29 pm**

Hi nerg,

we will try to stop manually nfs server and remove its pid files.

So in putty do

Code: Select all: /usr/bin/killall -9 nfsd /usr/bin/killall -9 rpc.statd /usr/bin/killall -9 rpc.mountd unlink /var/run/rpc.statd.pid (it should no longer exist and so you can get a warning) unlinck /var/run/sm-notify.pid

and then try to restart the nfs server

plugout.net

no nfs access after upgrade v14 -> v15

no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15

Re: no nfs access after upgrade v14 -> v15