shedd / duckpan-vagrant

Vagrant + Chef virtual development environment for DuckDuckGo (http://duckduckhack.com)
Apache License 2.0
5 stars 5 forks source link

"vagrant up" not working #15

Closed jagtalon closed 9 years ago

jagtalon commented 10 years ago

I'm getting this error when I first ran vagrant up. Not quite sure what the problem is. I'm using OS X 10.9.1

screen shot 2014-02-09 at 3 36 56 pm

shedd commented 10 years ago

Hi Jag, thanks for the issue report.

If you run vagrant provision again after seeing this error, does Chef complete the provisioning successfully then?

jagtalon commented 10 years ago

@shedd I will try that--thanks. Does it work for you or maybe this only on the Mac?

quanganhdo commented 10 years ago

If I remembered correctly, I need to run this in vagrant ssh to force the install script to succeed:

cpanm Module::Path --force
shedd commented 10 years ago

I tested this again today. I didn't see the specific problem reported - I did see another installation error when the script attempted to install the DuckPAN package (there was a connection issue in downloading the final duckpan package the first time around).

In general, I've found that running vagrant provision again after any failures allows the script to resolve the problem.

I'll think about ways to make the installation script more reliable. In general, I'd like to move away from the current Chef recipe to Ansible, maybe as a part of that, this could be revamped. Open to any other ideas, too!

shedd commented 9 years ago

@jagtalon do you know if you're still having this issue? Some improvements have been made recently to the dependencies, which might fix the issue. Going to close this for now...