Cannot run vessel after fresh install
Closed this issue · 9 comments
Hello,
I installed Vessel and am trying to run it but got some issues:
I installed brew install npm and npm install grunt-cli.
Thanks for your help.
Arnaud
Hmm that is odd. Is the app modified in any way?
You shouldn't need npm or grunt-cli to run Vessel, only to build it.
The error looks like Vessel can't either spawn a new process or read/write a file.
No I did not modify it: Just downloaded and installed it. Yes, that's what
I inferred too but I thought this was because it could not find some other
tools, hence my installing npm and grunt-cli.
Don't know where to look...
Le 26 août 2014 01:39, "Gavin M. Roy" notifications@github.com a écrit :
Hmm that is odd. Is the app modified in any way?
You shouldn't need npm or grunt-cli to run Vessel, only to build it.
The error looks like Vessel can't either spawn a new process or read/write
a file.—
Reply to this email directly or view it on GitHub
#2 (comment).
Any chance that it does not have permission to write to the /Users/arnaud/projects/vessel directory?
If you run it via terminal, we may get a better idea of what's going on. Assuming it's in /Applications (or replace /Applications with the root path to the app), in terminal try:
/Applications/Vessel.app/Contents/MacOS/VesselAnd it will spit out logging info in the terminal. That might get things a bit farther.
Here is the log I got before it starts hanging...:
Already up-to-date.
From https://github.com/awvessel/manifest
* branch master -> FETCH_HEAD
null
[26432:0827/174516:INFO:CONSOLE(218)] "Waiting on 1 promises", source: ./coffee/listeners/config.coffee (218)
[26432:0827/174517:INFO:CONSOLE(220)] "Promises complete", source: ./coffee/listeners/config.coffee (220)
[26432:0827/174517:INFO:CONSOLE(18)] "Vagrant Listener: Performing status", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174517:INFO:CONSOLE(18)] "Vagrant Listener: Status received", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174517:INFO:CONSOLE(18)] "Vagrant Listener: Performing ssh-config", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174517:INFO:CONSOLE(18)] "Vagrant Listener: Fetching uptime", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174517:INFO:CONSOLE(18)] "Vagrant Listener: SSH config received", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174517:INFO:CONSOLE(26)] "Vagrant Listener: Checking if box is outdated", source: ./coffee/utils/logger.coffee (26)
[26432:0827/174517:INFO:CONSOLE(18)] "Vagrant Listener: Outdated status received", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174524:INFO:CONSOLE(143)] "Path ensured", source: ./coffee/listeners/build.coffee (143)
[26432:0827/174524:INFO:CONSOLE(116)] "Waiting on 0 promises", source: ./coffee/listeners/build.coffee (116)
[26432:0827/174524:INFO:CONSOLE(118)] "Promises complete", source: ./coffee/listeners/build.coffee (118)
[26432:0827/174524:INFO:CONSOLE(50)] "Cloned", source: ./coffee/listeners/build.coffee (50)
[26432:0827/174528:INFO:CONSOLE(26)] "[config validatePassword]: stderr", source: ./coffee/utils/logger.coffee (26)
[26432:0827/174528:INFO:CONSOLE(60)] "Fetching new etcd discovery URL", source: ./coffee/listeners/build.coffee (60)
[26432:0827/174529:INFO:CONSOLE(18)] "[config] Got etcd discovery URL of https://discovery.etcd.io/7e9e106d053f3fb1409d6b5d311a57fd", source: ./coffee/utils/logger.coffee (18)
[26432:0827/174529:INFO:CONSOLE(62)] "Received URL: https://discovery.etcd.io/7e9e106d053f3fb1409d6b5d311a57fd", source: ./coffee/listeners/build.coffee (62)
[26432:0827/174529:INFO:CONSOLE(125)] "Generating cloud-config: https://discovery.etcd.io/7e9e106d053f3fb1409d6b5d311a57fd", source: ./coffee/listeners/build.coffee (125)
[26432:0827/174529:INFO:CONSOLE(128)] "Heard back from generate: true", source: ./coffee/listeners/build.coffee (128)
[26432:0827/174529:INFO:CONSOLE(65)] "Cloud config generated", source: ./coffee/listeners/build.coffee (65)
[26432:0827/174529:INFO:CONSOLE(18)] "Vagrant Listener: Performing up with virtualbox", source: ./coffee/utils/logger.coffee (18)
_sudo_true null
What version of vagrant?
vagrant --version
Did you get the same error running interactively before it hangs?
oh oh
$ vagrant --version
-bash: vagrant: command not found
Arnaud Bailly
FoldLabs Associate: http://foldlabs.com
On Wed, Aug 27, 2014 at 6:01 PM, Gavin M. Roy notifications@github.com
wrote:
What version of vagrant?
vagrant --version
Did you get the same error running interactively before it hangs?
—
Reply to this email directly or view it on GitHub
#2 (comment).
Looks like vagrant was not installed :-(
Apologies for the noise: My laptop has been stolen and I just started reinstalling it...
No worries, I need to make some sort of pre-flight check for that stuff when launching the app!
I can confirm that it works much better when vagrant is correctly installed :-) !