Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

New public folder not picking up #61

Closed
dkouvdis opened this Issue Sep 24, 2013 · 18 comments

Comments

Projects
None yet
5 participants

Hi

I have around 10 folders in public folder and all works fine.

Now when I need to create a new one, it wouldn't work. It is showing other site instead?
I have create new json file, added site domain address in /etc/hosts file. Create new folder in public folder

This had affected me since I updated your repo. Am I missing something?

Was not aware of this change
config.vm.network :private_network, ip: "192.168.33.10"

Sorry

@dkouvdis dkouvdis closed this Sep 24, 2013

dkouvdis commented Nov 9, 2013

Hi.

Now I can no longer add new sites. Created new json in data_bags and added folder in the public folder. It is not picking up. I followed your instructions exactly.

So I did some research, did vagrant ssh.
In the /etc/apache2/sites-available - I am seeing no new files created there
In the /etc/apache2/sites-enabled - I am seeing no new files created there
In the /etc/hosts/ - I am seeing no new domain address been added to 127.0.0.1

What could be happening?

I have to manually create new files and restarting the apache to make it work.

Yes, I have done vagrant reload, halt. Tried everything before doing the manual step

@dkouvdis dkouvdis reopened this Nov 9, 2013

@ghost

ghost commented Nov 10, 2013

I am having the same issue as @dkouvdis please help..

Owner

r8 commented Nov 11, 2013

Can you clarify your vagrant/virtualbox versions and your operating system?

OSX 10.9
Virtualbox 4.3
Vagrant 1.3.5

Although I had the same problem with previous osx, version. My only solution to solve it was to backup all my db and vagrant destroy, and then build it again in order to pick up the new files.

Let say I have three sites like this below
angular.dev
local.dev
project1.dev

When I create a new one called project2.dev, I am only seeing the first one alphabetically which is angular.dev

@ghost

ghost commented Nov 12, 2013

I have the same specification as @dkouvdis
OSx 10.9
Vbox 4.3.2
Vagrant 1.3.5

and latest r8 Lamp

I have two projects
local.dev
test.dev

test.dev is pulling the files from local.dev and not from test.dev

my vim /etc/hosts are as follows
and data_bags as follows

screenshot 2013-11-12 11 34 14

screenshot 2013-11-12 11 34 54

annoying :(

Hi there, I'm facing the same problem in two machines where I run this vagrant lamp stack.
VirtualBox 4.2.18 r88780
Vagrant 1.3.5
Windows 7
Create the json file, the folder under public and halt/up (tried reload also). If there's something else I need to do to or inform please let me know.

esteluk commented Nov 18, 2013

Same. This also wasn't working for me about three/four weeks ago when I tried previously.

Owner

r8 commented Nov 18, 2013

@dkouvdis I think I'm beginning to understand what the problem is.

Am I right assuming that you're doing just vagrant reload, not vagrant reload --provision, as latest Vagrant actually requires?

Hi, @r8

Thanks for the reply, I am not aware of this command line. You are correct, this could be the solution.

Will test it tonight and will respond.

Maybe updating the docs about this would be great for others.

Cheers.

Owner

r8 commented Nov 18, 2013

I know that from Vagrant changelog:

vagrant up will now only run provisioning by default the first time it is run. Subsequent reload or up will need to explicitly specify the --provision flag to provision. [GH-1776]

https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md#130-september-5-2013

I can't find anything about this behavior in Vagrant docs though, so maybe I actually need to mention it in my docs.

Interesting changelog description.

I found the docs, dont think its detailed though.
http://docs.vagrantup.com/v2/cli/provision.html

Cheers

Hi r8 you nailed it thank you.

@ghost

ghost commented Nov 21, 2013

This is still not working for me on my OSx please provide a proper documentation on fixing this no clue why provision does not work. I get this error now

Recipe Compile Error in /tmp/vagrant-chef-1/chef-solo-1/cookbooks/vagrant_main/recipes/default.rb

NoMethodError

undefined method `[]' for nil:NilClass

Cookbook Trace:

/tmp/vagrant-chef-1/chef-solo-1/cookbooks/build-essential/recipes/debian.rb:30:in from_file' /tmp/vagrant-chef-1/chef-solo-1/cookbooks/build-essential/recipes/default.rb:21:infrom_file'
/tmp/vagrant-chef-1/chef-solo-1/cookbooks/vagrant_main/recipes/default.rb:2:in `from_file'

Relevant File Content:

/tmp/vagrant-chef-1/chef-solo-1/cookbooks/build-essential/recipes/debian.rb:

23: command "apt-get update"
24: action :nothing
25: # tip: to suppress this running every time, just use the apt cookbook
26: not_if do
27: ::File.exists?('/var/lib/apt/periodic/update-success-stamp') &&
28: ::File.mtime('/var/lib/apt/periodic/update-success-stamp') > Time.now - 86400*2
29: end
30>> end.run_action(:run) if node['build_essential']['compiletime']
31:
32: %w{
33: autoconf
34: binutils-doc
35: bison
36: build-essential
37: flex
38: }.each do |pkg|
39:

[2013-11-21T12:51:51+00:00] INFO: Forking chef instance to converge...
[2013-11-21T12:51:52+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

@ghost

ghost commented Nov 21, 2013

I am forced to destroy my vagrant and vagrant up again to make it read a new folder.. grrr

Owner

r8 commented Nov 21, 2013

@serieseight Well, you're obviously having different problem then others here.

I'll try to reproduce it

@ghost

ghost commented Nov 21, 2013

Hi, Iv fixed it all i removed virtual box, vagrant and cleaned out all files to do with VM and reinstalled it all and its all good now..
2 hours later! :)

vagrant reload --provision worked. Closing this

@dkouvdis dkouvdis closed this Nov 24, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment