Ask Your Question
0

Problem starting up NFS server with Vagrant

asked 2014-02-03 06:38:56 -0500

ayjazz gravatar image

updated 2014-02-13 13:33:19 -0500

mether gravatar image

So I am trying to make my own edx server using these directions: https://github.com/edx/configuration/wiki/edX-Developer-Stack

Everything works up, until the 'vagrant up' section. NFS is needed to run the servers, so I end up getting this output:

[default] Configuring and enabling network interfaces...
[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for user: 
Redirecting to /bin/systemctl status  nfs-server.service
nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled)
   Active: failed (Result: exit-code) since Mon 2014-02-03 05:49:05 CST; 24min ago
  Process: 3552 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
  Process: 3549 ExecStartPre=/usr/libexec/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)

Redirecting to /bin/systemctl start  nfs-server.service
Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.
[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' 192.168.33.1:'/home/user/my-workspace/my-edx-workspace/edx-platform' /edx/app/edxapp/edx-platform

Stdout from the command:



Stderr from the command:

stdin: is not a tty
mount.nfs: Connection timed out

So I type in both systemctl status nfs-server.service and journalctl -xn to test them out. And this is the output respectively.

[user@localhost edx movies]$ systemctl status nfs-server.service
nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled)
   Active: failed (Result: exit-code) since Mon 2014-02-03 06:31:25 CST; 22s ago
  Process: 7577 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
  Process: 7574 ExecStartPre=/usr/libexec/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)

[user@localhost edx movies]$ journalctl -xn
-- Logs begin at Sun 2014-02-02 11:09:36 CST, end at Mon 2014-02-03 06:30:51 CST
Feb 03 06:12:44 localhost.localdomain gnome-session[1117]: Failed to open VDPAU 
Feb 03 06:12:44 localhost.localdomain gnome-session[1117]: Failed to open VDPAU 
Feb 03 06:13:12 localhost.localdomain gnome-session[1117]: Failed to open VDPAU 
Feb 03 06:18:59 localhost.localdomain gnome-session[1117]: No permission to use 
Feb 03 06:20:14 localhost.localdomain gnome-session[1117]: No permission to use 
Feb 03 06:20:44 localhost.localdomain gnome-session[1117]: No permission to use 
Feb 03 06:21:33 localhost.localdomain gnome-session[1117]: No permission to use 
Feb 03 06:27:56 localhost.localdomain gnome-session[1117]: (tracker-miner-fs:143
Feb 03 06:29:24 localhost.localdomain gnome-session[1117]: Failed to open VDPAU 
Feb 03 06:30:51 localhost.localdomain gnome-session[1117]: (firefox:2728): Gtk-C

So I went to this link, https://github.com/mitchellh/vagrant/issues/2447 and tried out this command.

sudo systemctl restart nfs-server

And this was the output

Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.

What is going on here? I'm out of ideas. I'm a Fedora newbie, so this output is ... (more)

edit retag flag offensive close merge delete

Comments

Do journalctl -u nfs -b instead; `journalctl -xn isn't showing anything related to nfs in that snippet.

randomuser gravatar imagerandomuser ( 2014-02-03 23:44:17 -0500 )edit

I did, and it had no output.

ayjazz gravatar imageayjazz ( 2014-02-04 01:06:43 -0500 )edit

Try starting it manually, verify your journalctl command, and check the logs again. It will at least show that you attempted to start nfs-server.service . You'll also want to look at ausearch -m avc -ts today for selinux denials and man nfs_selinux for the way to use NFS with SELinux.

randomuser gravatar imagerandomuser ( 2014-02-04 23:46:37 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
0

answered 2014-02-03 07:20:12 -0500

NickTux gravatar image

I don't know about NFS and vagrant, but I don't think that this failure has something to do with the environment. I would suggest to have a look inside /etc/exports (maybe a configuration is needed) and also inform the developer in github page.

edit flag offensive delete link more
0

answered 2015-07-03 09:51:20 -0500

NFS has to be running (started) on guest. There was in issue in Vagrant source code so that did not happened for Fedora guests. If you used Fedora guests, perhaps this was the issue. It's fixed in latest bug release:

sudo dnf update vagrant --enablerepo=updates-testing
edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2014-02-03 06:38:56 -0500

Seen: 3,402 times

Last updated: Jul 03 '15