-
-
Notifications
You must be signed in to change notification settings - Fork 56
Errors during vagrant up #36
Comments
Can you try to Otherwise, once the machine goes up and has the error, you can still ssh in via |
Thank for your reply jgable. Log provided belong to vagrant halt and vagrant up :( npm ERR! install Couldn't read dependencies npm ERR! System Linux 3.2.0-58-generic In Ghost folder there are only npm log files: seems clone ghost repository fails but I don't know why... |
For what it's worth, I'm experiencing identical errors on two different physical machines. |
@rucka, @lourinaldi This sounds like Ghost is not properly mounted into the virtual machine. Please make sure that you have cloned the Ghost repository alongside Ghost-Vagrant. Your directory structure should look like the following:
Please also make sure that NFS works properly on your machines. |
@halfdan you were right, I had unpacked https://ghost.org/zip/ghost-0.4.1.zip rather than cloning the repo. Fixed that. But I still get "grunt init" errors during provisioning. |
@lourinaldi Can you post the errors here? |
@halfdan I wiped everything and re-cloned the two repos fresh. On running vagrant up, I get the following (only pasting relevant section). Then going to http://local.tryghost.org/ yields "502 Bad Gateway" from nginx.
|
Those are mostly notices. You receive the 502 Bad Gateway because you didn't start Ghost. You need to @lourinaldi Can you try and update the guest additions? (https://github.com/TryGhost/Ghost-Vagrant#updating-virtual-box-guest-additions). Do a |
Hi there, I just tried setting up the Vagrant box and got a similar error:
So it failed at installing grunt-cli (probably just because it's the first package listed). I logged into the box and went to
So I checked out the path where it tries to install the modules:
The directory is owned by some admin user and we run I have no clue why it fails upon provisioning though - that should be run as root, right? |
@kamilkowalski what version of vagrant and virtual box are you working with? |
@halfdan I finally got it to work after reading @kamilkowalski's comment. And that was only after disabling the new MySQL provisioning in the puppet init file, which was also failing. |
@lourinaldi Oh - did you get any errors from the MySQL provisioning? I just added MySQL recently and tried to test it as best as I could. |
@jgable Just tested at work on VirtualBox 4.3.4 and Vagrant 1.4.3 - same error. Back home I have VirtualBox 4.3.6 and Vagrant 1.4.2 I believe. I noticed in README.md that there's no '>=' next to Vagrant's version - does that mean that it has to be exactly the 1.2.2 version? Anyway, when I logged in to the box here at work and tried running
So I switched to a http:// registry, and then I got the same as yesterday. Running Regardless of the error, I think the nvm directory and its subdirectories should be owned by vagrant since it resides in /home/vagrant - Ghost is run by the vagrant user as well. I don't know how to change the permissions in Puppet manifests though, I don't know that much about it. |
@kamilkowalski Just so you know, yesterday my builds on Travis-CI were failing also due to SELF_SIGNED_CERT_IN_CHAIN errors. I believe the issue was caused by NPM if I had to guess. My builds are all passing today and I changed nothing. |
This looks like a couple of things, the permissions issues, and our old version of NPM was having the Have a fix inbound 🚀 |
@jgable good news! 👍 I was having SSL issues previously not only with npm but also with Ruby Gems. In those cases I usually changed the repository address to HTTP since I thought it's a connectivity problem, good to know it's just a bug. |
Just to add a source regarding the SSL issues: http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more |
I have had a horrible time trying to use this. When puppet fails at the mysql step you are left in a horrible half installed state. How about using a pre-built image instead of using puppet to install dependencies? |
@davidblurton It would be a lot more helpful if you posted actual error messages here. Using a pre-built image wouldn't work, as we will also add PostgreSQL. |
Sorry, was getting stress out by it earlier. Here is the complete log for a fresh clone:
|
Did you run git submodule init and git submodule update —recursive? -- On 9 Mar 2014 at 18:24:51, David Blurton (notifications@github.com) wrote: Sorry, was getting stress out by it earlier. Here is the complete log for a fresh clone: Bringing machine 'default' up with 'virtualbox' provider... Progress: 90% Guest Additions Version: 4.1.12 — |
Aha - that solves the mysql problem - thanks. Then I follow the instructions in your bad gateway comment above and get the following errors:
|
Ok, figured out the problem. Looks like I've been hitting this npm bug because I'd already installed some of the dependencies in my source folder. I also had to build sqlite3 from source because it had been built on my mac by grunt init which meant the binary didn't work inside vagrant. I guess I should've run The solution was to delete the node_modules directory and then |
@davidblurton Thanks, removing |
Hi All,
I installed virtual box (4.2.2), vagrant and ghost-vagrant as read me documentation on my ; also i upgraded virtual box guest addition.
After vagrant up command 'git submodule update' error occur (my logs following):
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Running any VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
GuestAdditions 4.2.22 running --- OK.
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] -- /tmp/vagrant-puppet/manifests
[default] -- /tmp/vagrant-puppet/modules-0
[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
[default] Mounting NFS shared folders...
[default] Running provisioner: puppet...
Running Puppet with base.pp...
warning: Could not retrieve fact fqdn
err: /Stage[main]/Ghost/Exec[git submodule update]/returns: change from notrun to 0 failed: git submodule update --init returned 128 instead of one of [0] at /tmp/vagrant-puppet/modules-0/ghost/manifests/init.pp:62
notice: /Stage[main]/Nvm/Exec[set-node-version]/returns: executed successfully
err: /Stage[main]/Ghost/Exec[npm-install-packages]/returns: change from notrun to 0 failed: npm install returned 34 instead of one of [0] at /tmp/vagrant-puppet/modules-0/ghost/manifests/init.pp:56
notice: /Stage[main]/Ghost/Exec[grunt init]: Dependency Exec[npm-install-packages] has failures: true
warning: /Stage[main]/Ghost/Exec[grunt init]: Skipping because of failed dependencies
notice: /Stage[main]/Upstart/Service[app]/ensure: ensure changed 'stopped' to 'running'
notice: Finished catalog run in 1.36 seconds
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
cd /tmp/vagrant-puppet/manifests && puppet apply --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' base.pp --detailed-exitcodes || [ $? -eq 2 ]
Can you help me?
Thanks
Regards
Gianluca
The text was updated successfully, but these errors were encountered: