VVV: failed to open vendor/perftools/php-profiler/autoload.php on a fresh provision

Are you using the latest stable or develop branch version of VVV?

Yes (develop)

Is it a new VVV or an existing VVV that used to work?

Existing, worked but now broken

Whats the problem?

@tomjn asked in the vvv slack that I create a bug report for this:

After following the steps at https://varyingvagrantvagrants.org/docs/en-US/troubleshooting/ Starting from Fresh (in between vagrant destroy and vagrant box update; I installed newer versions of the virtualbox and virtualbox extension pack);

I was receiving the following errors in the terminal as I was reprovisioning and whenever I went to any of my local sites; the same errors would appear in my browser.

Warning: require_once(vendor/perftools/php-profiler/autoload.php): failed to open stream: No such file or directory in /srv/www/default/php-profiler/config.php on line 3

Fatal error: require_once(): Failed opening required 'vendor/perftools/php-profiler/autoload.php' (include_path='.:/usr/share/php') in /srv/www/default/php-profiler/config.php on li

Note: I have not isolated it enough to reproduce its specific cause.

After commenting out out the mongodb and tideways entriesin my config.yaml ; I also renamed utilities to extensions; I no longer had the issue.

below is the log file from ; named provisioner-site-anameofmysite log/provisioners/2022.04.04_18-54-43 https://gist.github.com/skorasaurus/bc6bfaf69b3f83ac6614830c26141333

How do we reproduce it?

No response

VVV Status screen

\ V\ V\ V / v3.9.0 Path:"/home/myusername/vvv"
 \_/\_/\_/  git::develop(5742364)

Platform: linux shell:/bin/bash systemd  vagrant-goodhosts vagrant-vbguest CaseSensitiveFS shared_db_folder_disabled
Vagrant: v2.2.18, virtualbox: v6.1.32

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Which Operating System are you using?

Linux

Which provider are you using?

VirtualBox

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 22 (15 by maintainers)

Most upvoted comments

closing this as it hasn’t seen updates in a year and newer versions are out, feel free to reopen if the exact same issue happens again.

I’m not sure if this is resolved but the ideal situation is that the only way to reproduce this is using stable or older

The git repo is in provision/extensions/core if you want to do it manually

On Tue, 5 Apr 2022 at 16:25, Will Skora @.***> wrote:

You can modify config.yml to pull in that branch as a separate source,

Sorry, could you explain a bit more what I need to specifically modify in config.yml to pull in this PR https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/pull/99>

— Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2590#issuecomment-1088863581, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZ3FIJQC565K42AVS4DVDRLMRANCNFSM5SQZVVAQ . You are receiving this because you were mentioned.Message ID: @.***>

Also www/default/php-profiler