Closed csauer-djed closed 11 years ago
I'm assuming it's an issue with either vagrant or vagrant-salt, but I don't know what I don't know in this case.
I re-did the creation of the venv by hand and made sure to follow the salt scripts to the letter and I was able to get the example page served up properly.
So the only issue why vagrant/vagrant-salt/salt could not auto-create the venv.
I found one thing which could be causing this, but I can't know for sure. If you want to help me debug it, you should set salt.run_highstate
to false
in the Vagrantfile and then manually run the following after clean vagrant up
:
sudo salt-call state.highstate
If you get an error in your output, let me know. For now, I will close this issue.
It's actually an issue with Salt and has been fixed for the next release.
I installed the versions above, cloned the repo, and ran vagrant up. I got the "501 Bad Gateway", even after waiting a bit. The log from the install showed the contents:
you get the same error if you "vagrant ssh" and then run "sudo salt-call state.highstate"
/home/vagrant does not contain a /env/ directory for venv which causes uwsgi to keep trying to start and fail.
once logged into the VM, I created the venv by hand and ran the pip commands on it and uwsgi seemed to be happy but still wasn't getting the expected results (but I think we need to worry about one step at a time)