Nfs failed in joomlatools box

73 views
Skip to first unread message

Yves Dangel

unread,
May 31, 2016, 12:56:36 PM5/31/16
to Joomlatools Developers
Hi everybody,

I needed to reinstall my system on new ssd/motherboad but I have some problems with vagrant joolabox on my new debian 8.2 host. (all was working before)
Mismatch of virtualbox guest addon was solved when updating vagrant to 1.8 and virtualbox to 5.0 but a nfs problem remains.

With vagrant ssh, I was able to install a test site with
sudo joomla site:create test   (without sudo the command didn't complete)

but I cannot modifiy source files on my host because ~/Dev/jbox/www folder is empty.


yves@yd:~/Dev/jbox$ vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'joomlatools/box' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
   
default: Adapter 2: hostonly
==> default: Forwarding ports...
   
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
   
default: SSH address: 127.0.0.1:2222
   
default: SSH username: vagrant
   
default: SSH auth method: private key
   
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for yves:
nfs-kernel-server.service - LSB: Kernel NFS server support
   
Loaded: loaded (/etc/init.d/nfs-kernel-server)
   
Active: active (exited) since sam. 2016-05-28 10:12:27 CEST; 3 days ago
==> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount
-o 'vers=3,udp' 33.33.33.1:'/home/yves/Dev/jbox/www' /var/www

Stdout from the command:



Stderr from the command:

stdin
: is not a tty
mount
.nfs: requested NFS version or transport protocol is not supported



nfs-kernel-server is installed on host and nfs module is loaded on both client and host.
IP Adress 33.33.33.1 is pingable from client.
I cannot see anything in client log about this problem.

What does I need to check to solve that ?

Thanks for your help

Peter Raeves

unread,
Jun 1, 2016, 6:05:37 AM6/1/16
to Joomlatools Developers
Hello,

I suppose you checked already your firewall settings...
If not, please do so.
Did you try emptying your /etc/exports folder and restart your nfs-kernel-server.service after that.
This seems to work is some cases.
I see you are working in your home directory. Is is encrypted by any chance? This could also cause this type of error.
If so, you could move your working directory out of your home directory.

Good luck,
Peter

Op dinsdag 31 mei 2016 18:56:36 UTC+2 schreef Yves Dangel:

Yves Dangel

unread,
Jun 1, 2016, 12:09:40 PM6/1/16
to Joomlatools Developers
Hello Peter,

I have no firewall and ping can success from host to client and from client to host.
i have no encrypted home directory so it doesn't seem to be the problem.
No luck.

I will try again to google same issue but as far as I searched, i didn't find a solution.
A lot of issues on Mac...

Thanks for your help.


Yves Dangel

unread,
Jun 1, 2016, 12:47:28 PM6/1/16
to Joomlatools Developers

More info :


sudo mount -v
-o 'vers=3,udp' 33.33.33.1:'/home/yves/Dev/jbox/www' /var/www

gives

mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Wed Jun  1 14:32:03 2016
mount.nfs: trying text-based options 'vers=3,udp,addr=33.33.33.1'
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

and

sudo rpcinfo -p

   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  35789  status
    100024    1   tcp  45724  status


Steven Rombauts

unread,
Jun 1, 2016, 2:40:19 PM6/1/16
to Joomlatools Developers
Hello Yves,

It seems that NFS server isn't running at all based on the output you posted from the rpcinfo -p command. If you were to look for the keyword nfs only you should get the following result:

{20:29}[5.5.32]~/:master ✓ rpcinfo -p | grep nfs 
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs

If you run  ps -aef | grep nfs  you should see the nfs daemon in the output (/sbin/nfsd or similar).

Does it work if you start it manually? I 'm not 100% sure about the correct command for your system, but something along these lines should do it: /etc/init.d/nfs-kernel-server start

If it works then it means the service fails to start properly at boot time (for example wrong startup ordering). 

Good luck,
Steven

--

---
You received this message because you are subscribed to the Google Groups "Joomlatools Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomlatools-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yves Dangel

unread,
Jun 1, 2016, 7:10:58 PM6/1/16
to Joomlatools Developers, ste...@kotuha.be
Hello Steve,

service nfs-kernel-server status

nfs
-kernel-server.service - LSB: Kernel NFS server support
   
Loaded: loaded (/etc/init.d/nfs-kernel-server)
   
Active: active (exited) since mer. 2016-06-01 16:16:24 CEST; 8h ago
 
Process: 26071 ExecStop=/etc/init.d/nfs-kernel-server stop (code=exited, status=0/SUCCESS)
 
Process: 26079 ExecStart=/etc/init.d/nfs-kernel-server start (code=exited, status=0/SUCCESS)

juin
01 16:16:24 yd nfs-kernel-server[26079]: Not starting NFS kernel daemon: no exports. ... (warning).

but /etc/exports was not empty !!

I just typed


service nfs-kernel-server start
service nfs
-kernel-server status
nfs-kernel-server.service - LSB: Kernel NFS server support
   
Loaded: loaded (/etc/init.d/nfs-kernel-server)

   
Active: active (running) since jeu. 2016-06-02 00:34:40 CEST; 2s ago
 
Process: 2453 ExecStop=/etc/init.d/nfs-kernel-server stop (code=exited, status=0/SUCCESS)
 
Process: 2461 ExecStart=/etc/init.d/nfs-kernel-server start (code=exited, status=0/SUCCESS)
   
CGroup: /system.slice/nfs-kernel-server.service
           
└─2489 /usr/sbin/rpc.mountd --manage-gids

juin
02 00:34:40 yd nfs-kernel-server[2461]: Exporting directories for NFS kernel daemon....
juin
02 00:34:40 yd rpc.mountd[2489]: Version 1.2.8 starting
juin
02 00:34:40 yd nfs-kernel-server[2461]: Starting NFS kernel daemon: nfsd mountd.


 and it works.

I will watch after my next reboot if this happens again ...

Thanks a lot.

Reply all
Reply to author
Forward
0 new messages