VVV installer halts if grunt is nor installed

[jnystromdesign]

When starting up vvv for the first time with vagrant up it will halt if grunt is not installed.
After the message
==> default: /tmp/vagrant-shell: line 358: grunt: command not found
it will output
==> default: Installing Grunt CLI
which will go on forever. By installing grunt cli manually this can be avoided.

Expected Behavior

Grunt cli should be installed if it's not already installed or it should ask the user to install grunt cli manually.

Current Behavior

Sais it is installing grunt cli (which it doesn't seem to complete)

Possible Solution

Install grunt cli manually and run vagrant up again.

[ktmn]

Happened to me too. First time stalled at installing Grunt, so I did VBoxManage controlvm vvv poweroff
to turn the machine off and ran vagrant up --provision again and then it worked.

[mpmumau]

Just by way of confirmation, I can vouch that this bug happens with the current, fresh-off-the-repo commit.

[daveshaw]

Seeing this as well, but in my case manually installing grunt-cli doesn't fix the problem. I'm stuck.

[mklasen]

Running vagrant halt and vagrant up --provision after running into this issue fixes the problem.

[mpmumau]

@mklasen Not for me; I tried that and many other things after much Googling, to no avail.

[LC43]

did the same as @mklasen and on the second run it completed provision. only catchmail seems to have failed, but its not critical.

[kraftner]

So I thought I've hit that issue as well but as it turned out it just took forever until the provision continued. I still don't know why that is, but just as a hint for others that this maybe is fixable by patience™.

[jonathan-dejong]

I noticed my mailcatcher stopped working as well. So I did a vagrant destroy and on up this now also occurs for me. And even when successful after a loooong time mailcatcher does not work :/

[kraftner]

@jonathan-dejong I think the mailcatcher thing could be another issue - see #1235

[jonathan-dejong]

@kraftner thank you! Was looking for something like that but couldn't find anything (my googlefu was not strong enough). The fix in that thread did solve my issue (with mailcatcher).

[jerturowetz]

I can report same issue, I'm hanging on exactly the same line on a a fresh Windows 10 install (Oracle VirtualBox 5.1.24, Vagrant 1.97, VVV 2.0.0).

EDIT: As @kraftner mentioned, it was just a super long wait for the grunt install to complete (this would have been anywhere from 15 to 30 minutes). Still seems like something fishy is going on but I can report that the install completed eventually.

[spuddick]

I can vouch as well that it was just a very long wait. I found this thread by searching for issues related to hanging on "Installing Grunt CLI". As I was reading, I saw movement in my command line window. It was about a 15 - 30 min wait for me too.

[nylen]

#1246 should fix this.

Still seems like something fishy is going on

Confirmed. The fishiness is a Node.js post-install script failing to download a binary, then node-gyp going into an infinite loop until it uses all available memory. Towards the end of this process you'll get a memory-related error if you attempt to vagrant ssh.

[cj-andrew]

I can confirm that this was a really long wait for me as well, using VVV2.

vagrant up seemed to stall at Installing Grunt CLI... After waiting for about 25-30 minutes, it moved through and completed successfully on its own. In the recent past, I had exited with a Ctrl-Break, and tried a vagrant halt followed by vagrant up --provision. That helped move past the stall.

This time round, however, I just waited and it eventually completed.

@nylen makes an interesting observation about the Node.js post-install script failing at some point in the process.

[ghost]

For the record, I wont open a new bug for this.

Had the same problem using latest master ( Oct 12, 2017) on two different install (at home and work) and other undecipherable errors (The SSH command responded with a non-zero exit status. ).

I had to rerun provision multiple times to get it to pass.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.