Closed berpcor closed 8 years ago
Hi @berpcor
Can you please run the command again like this:
vagrant up --debug &> vagrant.log
and then put the contents of vagrant.log in a gist?
Hey @berpcor
Unfortunately I don't have access to those installation scripts. I removed some of the comments and the plugins from your Vagrantfile - can you tell me if the issue persists with this Vagrantfile:
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.hostname = hostname
config.vm.network :private_network, ip: server_ip
config.vm.network :forwarded_port, guest: 80, host: 8000
config.vm.network :forwarded_port, guest: 9200, host: 9200
config.ssh.forward_agent = true
config.vm.synced_folder ".", "/vagrant", disabled: true
config.vm.synced_folder "projects", "/var/www", create:true,
id: "core",
:nfs => true,
:mount_options => ['nolock,vers=3,udp,noatime,actimeo=2']
config.vm.provider :virtualbox do |vb|
vb.name = hostname
vb.customize ["modifyvm", :id, "--cpus", server_cpus]
vb.customize ["modifyvm", :id, "--memory", server_memory]
vb.customize ["guestproperty", "set", :id, "/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 10000]
end
config.vm.provision "shell", path: "#{github_url}/scripts/base.sh", args: [github_url, server_swap, server_timezone]
config.vm.provision "shell", path: "#{github_url}/scripts/base_box_optimizations.sh", privileged: true
config.vm.provision "shell", path: "#{github_url}/scripts/php.sh", args: [php_timezone, hhvm, php_version]
config.vm.provision "shell", path: "#{github_url}/scripts/vim.sh", args: github_url
config.vm.provision "shell", path: "#{github_url}/scripts/apache.sh", args: [server_ip, public_folder, hostname, github_url]
config.vm.provision "shell", path: "#{github_url}/scripts/mysql.sh", args: [mysql_root_password, mysql_version, mysql_enable_remote]
config.vm.provision "shell", path: "#{github_url}/scripts/memcached.sh"
config.vm.provision "shell", path: "#{github_url}/scripts/redis.sh"
config.vm.provision "shell", path: "#{github_url}/scripts/composer.sh", privileged: false, args: [github_pat, composer_packages.join(" ")]
config.vm.provision "shell", path: "#{github_url}/scripts/git-ftp.sh", privileged: false
end
This vagrantfile doesn't work as github_url variable not set, for example. Should I create a new vagrantfile in a new directory with the content you provided?
Hi @berpcor
Sorry - you still need all the variables at the top (same as your original Vagrantfile). I just didn't post them there.
I created a new folder c:\www3, put there vagrantfile you provided. Executed vagrant up
first time I had freeze on mounting NFS shared folder. I pressed ctr+c, then manually stopped VM in Virtualbox. Started again vagrant up, now I am waiting for provisioning...
Nope, the same problem... ((
Hi @berpcor
What port(s) are you trying to access and how?
80 I guess... http://192.168.56.56.xip.io - like it worked before... Besides, now I have 17 VirtualBox Host-Only Network adapters )
Hi @berpcor
I'm not familiar with xip.io - what is that? Did you destroy the old Vagrant machines? Im not sure why you have so many host-only adapters.
http://xip.io/ I won't describe better ) Just several sentences.
I am checking settings in Virtualbox GUI. The last VM has no shared folders.
Hi @berpcor
Can you access the machine by IP address directly (no xip.io)? The last VM won't have shared folders (they are explicitly disabled, and if you put it in a subfolder, "projects" won't exist either).
http://192.168.56.56 Can't get access too...
Why I decided to use gulp?.. Main rule: don't touch if it works - was broken...
config.vm.network :private_network, ip: "192.168.56.56"
config.vm.network :forwarded_port, guest: 80, host: 8080, auto_correct: true
config.vm.network :forwarded_port, guest: 9200, host: 9200
I have access to my guest on url localhost:8080, but I can't open IP-address.
Exactly. Every time I reload vagrant it creates a new host-only Network.
Hi @berpcor
I just tried, and I'm unable to reproduce this issue on my machine. Just to make sure, your "host" (local laptop) is ubuntu 14.04 and the guest (vm you're trying to run) is windows 7? What box are you using?
1-st question: yes and yes. config.vm.box = "ubuntu/trusty64"
Again. localhost:8080 - working localhost:9200 (Elasticsearch) - working. Can't open IP address.
config.vm.network :private_network, ip: "169.254.213.188" - my IP now. Vagrant created host-only network with IP of 169.254.55.176. Is it normal?
From inside of the guest I can ping 169.254.213.188.
If I set IP equals to 192.168.56.X Host-only Network adapter should get 192.168.56.1 Why in my case it is not true?
I moved forward a little bit. When I start Vagrant, as I said, it should take my IP then search appropriate network adapter (the same network), if I haven't got it, vagrant should create it (IP equals to mine, but the last octet is 1). In my case each time I reloaded Vagrant, it created a new network adapter BUT not in the subnet in which my IP exists. I deleted all adapters, manually edited settings of the very first adapter (IP: 192.168.56.1, mask 255.255.255.0, IP of my guest machine was 192.168.56.56) then chosen it in GUI of Virtualbox settings for VM and everything works. Now I am trying to reproduce behaviour of Vagrant...
Vagrant is installed (latest version), Virtualbox (4.3.36, downgraded from 5) too. I'll try to delete all of virtual adapters and when I do vagrant up Vagrant should create adapter with necessary settings. I want to see what will happen.
It looks like this - https://github.com/mitchellh/vagrant/issues/1014 - is my problem.
Hi @berpcor
I'm having a very difficult time following the issue you're describing. It seems your original reported issue has changed.
Can you do the following:
Vagrant.configure(2) do |config|
config.vm.box = "hashicorp/precise64"
config.vm.network "private_network", ip: "33.33.33.10"
config.vm.provision "shell", inline: "sudo apt-get -yqq install apache2"
end
This is a vanilla Vagrantfile that installs apache 2. You should see a message like "it works" on the default page.
Hey there,
I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks! 😄
Everything worked excelent. Had a problem with long names of files in shared folder created by npm. (I needed to install gulp). Installed the latest version of virtualbox (Vagrant version was 1.7.x). After that vagrant up stopped working (Virtualbox's error - E_FAIL (0x80004005) Failed to create the host-only adapter). Then I reinstalled Virtualbox - didn't help. Then I deleted virtualbox at all. For some reasons all of my network adapters were deleted too (ethernet and wireless) - there were deleted drivers. I deleted them from the list of hardware, updated my configuration and reinstalled drivers. Then I installed Virtualbox 5 (latest for now). Vagrant up now is working (it looks like that), but when I type in some of my sites in address bar, I can't visit it - timeout. Upd.: I watched logs There was
I installed https://github.com/dotless-de/vagrant-vbguest Additions updated, but I still can't enter my site via browser.
Vagrant version
Installed Version: 1.8.1 Latest Version: 1.8.1
Host operating system
"Ubuntu 14.04.3 LTS"
Guest operating system
Windows 7
Vagrantfile
Debug output
https://gist.github.com/berpcor/9f475bd8b0823d45d690 Upd.: https://gist.github.com/berpcor/d04b5bf6e36a51c5ad72 There was a big amount information in console but only this is stored in file.
Expected behavior
After vagrant up I should be able to visit my project ia adress bar. But I can't.