davidread
commented
10 years ago ==> default: err: /Stage[main]/Dgu_ckan/File[/vagrant/src/ckan/ckan.ini]/ensure: change from absent to link failed: Could not set 'link on ensure: Protocol error - /var/ckan/ckan.ini or /vagrant/src/ckan/ckan.ini at /etc/puppet/modules/dgu_ckan/manifests/init.pp:219
This first error message is being unable to make a symbolic link to ckan.ini and it appears to be due to a problem with Virtualbox running on Windows. There is discussion here: http://stackoverflow.com/questions/24200333/symbolic-links-and-synced-folders-in-vagrant and here: https://www.virtualbox.org/ticket/10085#comment:12 . You could try running the Windows prompt as Administrator. But I think you would be better off with a host running Linux or OSX.
==> default: err: /Stage[main]/Dgu_ckan/Service[jetty]/ensure: change from stopped to running failed: Could not start Service[jetty]: Execution of '/etc/init.d/jetty start' returned 127: at /etc/puppet/modules/dgu_ckan/manifests/init.pp:473
The next error is not due to the first error. It says the Java Jetty container won't start. I can't find anything about error 127. Maybe it's a Windows thing again - I don't have much guess.
==> default: notice: /Stage[main]/Dgu_ckan/Exec[npm_deps_shared]/returns: npm ERR! { [Error: EPERM, open '/src/shared_dguk_assets/node_modules/grunt-contrib-less/node_modules/less/node_modules/request/node_modules/form-data/node_modules/combined-stream/node_modules/delayed-stream/test/integration/t ==> default: notice: /Stage[main]/Dgu_ckan/Exec[npm_deps_shared]/returns: npm ERR! Please try running this command again as root/Administrator. ==> default: err: /Stage[main]/Dgu_ckan/Exec[npm_deps_shared]/returns: change from notrun to 0 failed: sudo npm install returned 50 instead of one of [0] at /etc/puppet/modules/dgu_ckan/manifests/init.pp:597
Again this doesn't rely on the previous failed steps. It's a permissions problem again, and might be to do with the symbolic link thing.
I'm sorry I can't help more. I've included the output I get here: https://gist.github.com/davidread/11fafa9d5716766dd053
Tried installing dgu-vagrant-puppet togo branch yesterday, choosing the 1st option, i.e. to install on a Vagrant VM. But looks like "vagrant up" failed at some point in provisioning. I am able to do "vagrant ssh" and look around in the machine, but it probably should have created a CKAN database in postgresql, but there is no such thing. There are numerous errors in the "vagrant up" output below, perhaps you can shed some light on how to cure this: