Vvv: vagrant up halt on cloning into '/srv/www/phpcs'

[jimboobrien]

Expected Behavior

Expected the vagrant up to finish or error out and continue.

Current Behavior

Vagrant up halts on "Cloning into '/srv/www/phpcs'" and does not error or continue.
I think this happens because I already created some phpcs stuff myself on my ubuntu machine.
Also, when doing ctrl + c in terminal the graceful cleanup fails as well.

Your Environment

• VVV version: 2.0.0
• Vagrant version: 1.8.5
• VM Provider name: VirtualBox
• VM Provider version: 5.0.32
• Operating System and version: ubuntu 16.04

[jimboobrien]

After killing the vagrant up and doing vagrant up and vagrant provision it did complete and load the wordpress-develop site now. But, it took two attempts to get the vagrant provision to go through. Had to wipe everything and re-clone the repo to try again.

[LoreleiAurora]

Do you have a copy of the provision log? If so can you put it in a gist
and link it here?

On Thu, 20 Apr 2017, 4:18 am Jimobrien, [e-mail] wrote:

After killing the vagrant up and doing vagrant up and vagrant provision it
did complete and load the wordpress-develop site now. But, it took two
attempts to get the vagrant provision to go through. Had to wipe everything
and re-clone the repo to try again.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1179#issuecomment-295564029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADtkKaJqFODc-YLc8L32iY4AOMtyve0fks5rxs5tgaJpZM4NCfIS
.

[jimboobrien]

There are a lot of errors in my php7.0_errors.log in the log directory, but I did not see a provision error log inside the log directory. I believe the php7 errors are from a site I imported once I got it to get past the phpcs error somehow, generated the default and develop directories, set the hostsfile, and finally load in the browser.

Where should I look for the provision log file?

• Jim

[LoreleiAurora]

The log is what comes up on the screen when you type vagrant up

[Spone]

Same issue here, not clear what happened. Do you know an way to save the log from Windows PowerShell to a file? (I run Vagrant on Windows).

[LoreleiAurora]

@Spone Ctrl + C then Ctrl + V

[Spone]

My log is here: https://gist.github.com/Spone/73de53a06eaf163534d69af7876907a2 (I only have the last 3000 lines)

EDIT: actually after waiting a long time, the provisioning continued until the end. I think the first time was probably a network glitch...

[jimboobrien]

My issue just hung on the line that says installing php-cs when doing the first vagrant up. I don't have the log for you, but I can tell you why I think it had a problem.

I had manually installed php-cs for PhpStorm before trying out vvv 2.0. Because of this I feel the first vagrant up hung because it saw I had already created the php-cs folder in /var folder with custom profiles for WordPress with a custom ruleset.

If the vagrant up could just check for folder and skip if found then it would avoid this hangup.

• Jim

[tomjn]

I'm closing this as the way PHPCS is provisioned has completely changed and the git clone in question no longer exists

[neilgee]

I just had this happen to me on a new clone of VVV2...

==> default: Restart services...
==> default:  * Restarting nginx nginx
==> default:    ...done.
==> default: Restarting memcached:
==> default: memcached.
==> default: stop: Unknown instance:
==> default: mailcatcher start/running, process 9743
==> default: php7.0-fpm stop/waiting
==> default: php7.0-fpm start/running, process 9932
==> default: Setup MySQL configuration file links...
==> default:  * Copied /srv/config/mysql-config/my.cnf               to /etc/mysql/my.cnf
==> default:  * Copied /srv/config/mysql-config/root-my.cnf          to /home/vagrant/.my.cnf
==> default: service mysql restart
==> default:  * Stopping MariaDB database server mysqld
==> default:    ...done.
==> default:  * Starting MariaDB database server mysqld
==> default:    ...done.
==> default:  * Checking for corrupt, not cleanly closed and upgrade needing tables.
==> default: No custom MySQL scripting found in database/init-custom.sql, skipping...
==> default: Initial MySQL prep...
==> default: Start MariaDB Database Import
==> default: No custom databases to import
==> default: Network connection detected...
==> default:
==> default: Installing/updating wp-cli and debugging tools
==> default: Downloading wp-cli, see http://wp-cli.org
==> default: Downloading PHP_CodeSniffer (phpcs), see https://github.com/squizlabs/PHP_CodeSniffer
==> default: Cloning into '/srv/www/phpcs'...
^C==> default: Waiting for cleanup before exiting...
^C==> default: Exiting immediately, without cleanup!
neilg@[~/provision-vvv]:(master) vagrant up

Seems ok on the vagrant up

[tomjn]

@neilgee is that 2.0 master? or 2.1 develop? Your output contains "Downloading PHP_CodeSniffer" but that was removed in https://github.com/Varying-Vagrant-Vagrants/VVV/commit/e85e31801947293aa91c9a62204427716ce0d528 6 months ago.

If you can reproduce using the latest develop branch, I'll reopen, otherwise reproduction in the master branch isn't relevant as 2.1 already fixes it

[neilgee]

Ok that was 2 will try out develop 2.1

[lock[bot]]

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.