Closed harrisonfm closed 3 years ago
Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/
VVVJoin the VVV Slack Workspace
@harrisonfm can you update your log to include the entire log? Of both the failed provisionand of the failed vagrant up
. It's missing lots of information, we really do need the full entire output of the commands.
Also, I strongly recommend you switch away from the master
branch to either stable
or develop
. The develop
branch usually has fixes that haven't been merged to the stable branch yet, your issue may have been fixed months ago.
@tomjn , thanks for responding.
I just made sure that I pulled develop and got this same issue.
The vagrant provision
log is huge, 70mb: https://drive.google.com/file/d/1-aoh2kzwoWSkTbHax_20i2f_Y2vQcSSQ/view?usp=sharing
I don't have a log for vagrant up
, but it was failing on time sync with ntupdate until I manually installed it on the vm, afterwards I did not have problems with that step.
Google Docs
@harrisonfm can you give #2483 a test? Check out that branch and reprovision and see what difference it makes
@tomjn
I made the edits in your branch, tried to provision again and had the same result.
Here is a new log. https://drive.google.com/file/d/1F6IKHfl_vydTcaOCZ-mU-rTQ-oBLW4rf/view?usp=sharing
Google Docs
@harrisonfm can you confirm you have more than 1GB of free RAM when you run the vagrant command? It also looks like you've only sent over the contents of the main provisioner log, not the full output of the command as requested. This means any debug information the splash screen outputs is missing, and so is any of the output from vagrant itself or any of the single line provisioners that happen before the main provisioner
Also if you SSH into the VM and run php -a
, what is the output of echo ini_get('memory_limit');
?
@tomjn memory limit is 128M
Sorry, but I do not know how to get either item you're requesting. 1) What command will get me the available RAM, and are you talking about my machine or in the VM? 2) When I run provision, there's an enormous amount of output to screen in terminal. How can I better capture that for you?
@tomjn memory limit is 128M
It should be -1
, which is what I get, have you modified the PHP configs in the config
folder?
What command will get me the available RAM, and are you talking about my machine or in the VM?
On MacOS you can use activity manager
When I run provision, there's an enormous amount of output to screen in terminal. How can I better capture that for you?
copy paste, usually into a gist. Drag to select at the start of the output then scroll down and click on the end while holding shift, or just pipe it into a file
@tomjn Sorry, it is -1 as expected. I took the 128M from the phpinfo on the VVV dashboard.
Ram: VBoxHeadless is using 4GB
Here is the full terminal output. I tried using a gist but it crashes uploading. https://drive.google.com/file/d/1ScLD1AgIYyw_ZzGNIwcFLKIGdRXWjdPy/view?usp=sharing
Google Docs
how are you updating VVV to switch to that branch? The output says you're using v3.7.0-zip-no-vcs
, the usual git checkout modify/wpdoctor-xdebug
shouldn't have worked for you 🤔
I didn't switch branches, I just copied your edits to provision/core/wp-cli/provision.sh
and reprovisioned.
Reinstalled VVV entirely off stable and no longer having issues. Still don't have any idea on what caused the original issue, but thanks for your help @tomjn
A fix for the ntpupdate command was merged in 10 hours ago.
I would also note that the handful of people who had this were all on the stable
branch, unfortunately they did what you did before debugging of the issue could be completed. There are several PRs that could solve this currently in motion but nobody to test that it fixes the issue.
I'd recommend you use the develop
branch
What was The Command Used To Provision
vagrant provision
What Kind of VVV Provision Was This
This was a reprovision of an already working VVV then... This was an attempt to upgrade to a new version of VVV
Logs/What Broke
Update MacOS to Big Sur 11.4, Vagrant no longer works. I update VirtualBox, VVV, get
command ntpdate not found
errors on vagrant up.SSH into vagrant box, install ntpdate, vagrant up passes. Vagrant provision then fails.
vagrant provision
https://drive.google.com/file/d/1-aoh2kzwoWSkTbHax_20i2f_Y2vQcSSQ/view?usp=sharingYour Environment
Thanks for any help!