Cant find 'guest' file(s)

[wpoortman]

When I use the bash init_proces.sh, the command line returns a error which results in a invalid Vagrant installation process.

bash: /vagrant/scripts/guest/m-clear-cache: No such file or directory
This error comes up after 'Unlinking CE sample data'

Two weeks ago, it all worked perfectly on my local machine.

[paliarush]

Looks like Vagrant is unable to mount shared folders for some reason. Possibly you have broken NFS server configuration on your host (if your host is OSX or Linux).

Have you tried the following item from FAQ to get more info?

To debug any CLI script in current Vagrant project, set debug:vagrant_project option in config.yaml to 1

[Ramboz89]

Hello guys, I have got the same problem, I'm on macOs and I've just upgraded to Sierra, could it be the issue?

However on my personal laptop is working just fine.

[paliarush]

@Ramboz89 Can you please make sure that shared folders and NFS-shares were mounted (after vagrant ssh there should be project at the same path as on your host)? I'm on Yosemite and haven't encountered such issue.

[cgaubuchon]

Yup, having the same issue after upgrading to MacOS Sierra. Seems that any/all of my projects that use NFS-shares are no longer sharing the folders as expected. I enabled debug:vagrant_project and took a look but there isn't anything that seems to specifically point to this being the issue. Going to search around since this seems to be a Vagrant issue more than an issue with this specific repo.

[cgaubuchon]

Figured it out in my case. I opened the VirtualBox GUI client and noticed that there were two instances of "vagrant-magento" VMs running. Since I didn't have any critical data I stopped and removed them entirely and ran the init_process.sh script again and everything worked.

[rhssk]

I'm on Linux system and I'm getting bash: /vagrant/scripts/guest/m-clear-cache: No such file or directory error after Unlinking CE sample data as well. NFS is at default configuration. I can SSH in Vagrant box but there are no shared folders mounted.

Here's a debug dump:
https://gist.github.com/rhssk/f32fbf555cb65176029af609f51c7fb0

[paliarush]

@cgaubuchon Thanks for investigating that.

@rhssk I can see in logs that Vagrant failed to mount shared folders in your case. Looks like some incompatibility of Vagrant+VirtualBox+NFS+YourOS. If you cannot make NFS work, it is possible to set use_nfs option to 0, then you will basically have the same experience as guys whose host OS is Windows (which does not support NFS).

[rhssk]

@paliarush That's a shame, haven't had any issues when working with NFS alone. Any guess what causes the [Unknown source file] error? From the log it seems unrelated to NFS issues.

[paliarush]

@rhssk I can see in log the following:

==> magento2.vagrant243: Mounting NFS shared folders...
[2016-10-18 20:12:00]
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

Have you tried to create simple Vagrantfile which will mount NFS folders on your environment? Something like this should work (then just do vagrant up):

# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANT_API_VERSION = 2
Vagrant.configure(VAGRANT_API_VERSION) do |config|
    config.vm.box = "ubuntu/trusty64"

    config.vm.provider "virtualbox" do |vb|
        vb.memory = 2048
        vb.name = "magento2.ubuntu-14.04"
    end

    config.vm.synced_folder '.', '/var/www/test', type: "nfs", create: true

end

[rhssk]

That results in

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

set -e
mkdir -p /var/www/test
mount -o vers=3,udp 192.168.11.1:/home/user/test/var/www/test
if command -v /sbin/init && /sbin/init --version | grep upstart; then
  /sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=/var/www/test
fi

Stdout from the command:

Stderr from the command:

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

I'll have to troubleshoot this further, but at the moment it indeed seems unrelated to your work. Will post a solution to my problem if I find it.

[rhssk]

In my case ufw was the reason why nfs timed out.

[paliarush]

@rhssk Thanks for checking. I'll improve error reporting for the case when NFS cannot be mounted, to avoid any confusion in the future.