Closed andreagrillo closed 6 years ago
Can you delete your copy of PHPMyAdmin, git pull
and reprovision? If it doesn't work, please put the full provisioner log in a gist and link to it from here so I can look through and check things
As an aside, you can use any MySQL client in place of PHPMyAdmin
Hi there,
after git pull
I tried to make a vagrant up --provision
but I receive this error:
`This Vagrant environment has specified that it requires the Vagrant version to satisfy the following version requirements:
= 2.1.0
You are running Vagrant 2.0.4, which does not satisfy these requirements. Please change your Vagrant version or update the Vagrantfile to allow this Vagrant version. However, be warned that if the Vagrantfile has specified another version, it probably has good reason to do so, and changing that may cause the environment to not function properly. `
but you tell me to don't use vvv with Vagrant version 2.1.0, right ?
With the v2.2.1 release, we fixed the vagrant trigger issue and Vagrant 2.1 is needed now, so upgrade and uninstall vagrant triggers
ok, Done! Working fine now, but PHPMyAdmin doesn't works...403 Forbidden, too. Any idea ?
Does completely deleting PHPMyAdmin and reprovisioning correct the issue?
no, I have deleted PHPMyAdmin, update vagrant and vvv to latest one and make a provisioning. Nothing, doesn't works.
I make a box update, too
Looking into this as well, as I am experiencing the same issue.
I think something with provisioning going awry.
Here is the snippet where I think something is going wrong:
default: Installing/Updating PHPMyAdmin
default: rm:
default: cannot remove ‘/srv/www/default/database-admin/vendor/codacy/coverage/.git/objects/pack/pack-3818f69fa7bd64ef22c94c0bf630c18333cd5da9.idx’
default: : Operation not permitted
default: rm:
default: cannot remove ‘/srv/www/default/database-admin/vendor/codacy/coverage/.git/objects/pack/pack-3818f69fa7bd64ef22c94c0bf630c18333cd5da9.pack’
default: : Operation not permitted
default: Do not run Composer as root/super user! See https://getcomposer.org/root for details
default: Installing phpmyadmin/phpmyadmin (4.8.1)
default:
default: [InvalidArgumentException]
default: Project directory ./ is not empty.
I have to take a break, as I need to dig through the provision code and or my box to see why it isn't emptying before trying to install.
Also, if you ssh into the box, you'll notice /srv/www/default/database-admin has no index.php file or anything to load via nginx, so I don't believe it's a permission error.
Hi there,
I'm waiting to find a final solution for this issue. However, like a temporary fix I have add this tool https://dev.mysql.com/downloads/file/?id=474210 and I have configure it with this guide: https://github.com/Varying-Vagrant-Vagrants/VVV/wiki/Connecting-to-MySQL-MariaDB
This solution working fine for me.
I have tried (for Windows 10) HeidiSQL but doesn't works fine for me. MySql Workbench working very well in my case.
I hope this temporary solution working for @ACatThatPrograms, too.
About PHPMyAdmin, any other idea @tomjn ?
Thanks for your time. AG
I'm at a conference until Monday and my capacity to look into this is significantly diminished. Now that the with around you did is actually a superior solution to phpmyadmin, which is included for convenience rather than as a defacto tool On Fri, 15 Jun 2018 at 12:27, Andrea Grillo notifications@github.com wrote:
Hi there,
I'm waiting to find a final solution for this issue. However, like a temporary fix I have add this tool https://dev.mysql.com/downloads/file/?id=474210 and I have configure it with this guide: https://github.com/Varying-Vagrant-Vagrants/VVV/wiki/Connecting-to-MySQL-MariaDB
This solution working fine for me.
I have tried (for Windows 10) HeidiSQL but doesn't works fine for me. MySql Workbench working very well in my case.
I hope this temporary solution working for @ACatThatPrograms https://github.com/ACatThatPrograms, too.
About PHPMyAdmin, any other idea @tomjn https://github.com/tomjn ?
Thanks for your time. AG
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1547#issuecomment-397580433, or mute the thread https://github.com/notifications/unsubscribe-auth/AADl5z4RaQH1CSYKqX8wYygSbZ2oSr4qks5t84wfgaJpZM4UlsJ7 .
Additionally I cannot offer any further suggestions without a full provision log, I don't have enough information to debug remotely On Fri, 15 Jun 2018 at 15:17, Tom Nowell contact@tomjn.com wrote:
I'm at a conference until Monday and my capacity to look into this is significantly diminished. Now that the with around you did is actually a superior solution to phpmyadmin, which is included for convenience rather than as a defacto tool On Fri, 15 Jun 2018 at 12:27, Andrea Grillo notifications@github.com wrote:
Hi there,
I'm waiting to find a final solution for this issue. However, like a temporary fix I have add this tool https://dev.mysql.com/downloads/file/?id=474210 and I have configure it with this guide: https://github.com/Varying-Vagrant-Vagrants/VVV/wiki/Connecting-to-MySQL-MariaDB
This solution working fine for me.
I have tried (for Windows 10) HeidiSQL but doesn't works fine for me. MySql Workbench working very well in my case.
I hope this temporary solution working for @ACatThatPrograms https://github.com/ACatThatPrograms, too.
About PHPMyAdmin, any other idea @tomjn https://github.com/tomjn ?
Thanks for your time. AG
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1547#issuecomment-397580433, or mute the thread https://github.com/notifications/unsubscribe-auth/AADl5z4RaQH1CSYKqX8wYygSbZ2oSr4qks5t84wfgaJpZM4UlsJ7 .
Hi @tomjn
don't worry. Reply when you have time....I haven't hurry on this issue. I'll make a provision log for you. I'll post it to you ASAP. Thanks for your time AG
Got mine fixed, I'll add below.
To continue my findings, at least on my end. I believe it has to do with the .idx and .pack files left behind by composer. The provisioner abandons install with the directory still containing files when it is unable to delete them.
Once you post a provision log it should help verify we have the same issue.
I would imagine we have the same issue so follow below to verify:
cd /srv/www/default/database-admin
ls
Continue below if same issue:
Cleanup old install files:
cd /srv/www/default/database-admin
rm *
chmod -r 755 vendor
rm -rf vendor
Make sure files are removed with 'ls'. database-admin needs to be empty if not use 'rm' appropriately.
exit and reprovision with "vagrant reload --provision"
@tomjn
I'm actually not sure what causes this issue, I tried replicating it, but have failed to do so. I think it may have been after updating VVV, though I am not sure.
It is at your discretion if it's cause worthy to update vvv-utilities/phpmyadmin/provision.sh to force chmodding those files just in case prior to the rm or not.
Hopefully this helps anyone else that runs into this.
@andreagrillo
If this doesn't help, I'll still look at your log and see if anything jumps at me.
PHPMyAdmin was changed to use Composer, and a part of that is the removal and reinstallation of PHPMyAdmin via this route, as detecting a composer install vs composer install that needed updating vs pre-composer was still something we hadn't figured out.
As for chmod, that should be irrelevant, that folder is mounted by vagrant, and so it should always have the same owner and file permissions
I don't think it was a composer issue, or an issue with the existing code.
Currently no problems now even when provisioning, and have been unable to recreate this issue.
I updated from a very old version of VVV, so maybe that could have had something to do with it.
@ACatThatPrograms unfortunately doens't works on my case, this is my provision log:
Thanks for ALL
Additional thing: Now the database-admin folder is empty:
@andreagrillo
Just saw this, and I don't have a lot of time at the moment so just a few things so it's clear when I can sit down:
Did you remove those files yourself, or were they already gone?
If removed yourself, is that log from a provision pre or post removal?
Using your mysql client or command line can you verify you have a database called 'phpmyadmin' as you are getting an error related to it; Maybe you created it with your client?
Regardless, I would re provision now and post an updated log. You should have files in database-admin.
Out of curiosity what all files were in database-admin? Was there an index.php file?
Clearly not now, but after a re-provision verify that there are files inside database-admin including an index.php.
For me, this problem stemmed from an nginx error, my solution was realizing that there wasn't a file for nginx to read so it threw an error. If you had an index.php file your 403 error was stemming from something else.
Additionally:
ls -al /srv/www/default/database-admin
?ls -al /srv/www/default
?Additionally, the PHPMyAdmin provisioner always outputs:
echo "Installing/Updating PHPMyAdmin"
But that message is nowhere to be seen in your provisioner log:
default: Current branch master is up to date.
==> default: Running provisioner: utility-core-phpmyadmin (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180616-3264-l1g50e.sh
==> default: Running provisioner: utility-core-webgrind (shell)...
That is not what is meant to happen, at an absolute minimum you should have seen this:
default: Current branch master is up to date.
==> default: Running provisioner: utility-core-phpmyadmin (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180616-3264-l1g50e.sh
default: Installing/Updating PHPMyAdmin
==> default: Running provisioner: utility-core-webgrind (shell)...
vvv-custom.yml
to use a custom branch?Note that the dashboard will always show PHPMyAdmin as an option under tools, it does not check to see if PHPMyAdmin has been installed. So if you remove it from the utilities section and reprovision, the PHPMyAdmin button will still be there but nonfunctional
I'm having the same issue here. I can access wordpress admin and everything is fine but when I try to access phpmyadmin I get 403 Forbidden. The link I'm using is http://vvv.test/database-admin/ . What should I do?
@IacopoC do you have anything in your www/default/database-admin
folder? Additionally can you answer any of the questions I asked earlier in this issue? Right now we need more information to be able to debug this, I'm unable to reproduce this issue on my machine
In the database-admin folder I have 1 folder and 1 file. Vendor folder and config.inc file. I'll try to answer other question already posted.
in addition I still have the button of phpmyadmin in vvv.test dashboard, but the link goes to 403 error page.
Can you confirm that provision/resources/core/phpmyadmin/provision.sh
looks like this file:
https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/blob/master/phpmyadmin/provision.sh
@IacopoC appears to have the issue I had earlier, though I'm still unsure of how to replicate it.
If doing a provision gets anything like this in the provision log:
default: Installing/Updating PHPMyAdmin
default: rm:
default: cannot remove ‘/srv/www/default/database-admin/vendor/codacy/coverage/.git/objects/pack/pack-3818f69fa7bd64ef22c94c0bf630c18333cd5da9.idx’
default: : Operation not permitted
default: rm:
default: cannot remove ‘/srv/www/default/database-admin/vendor/codacy/coverage/.git/objects/pack/pack-3818f69fa7bd64ef22c94c0bf630c18333cd5da9.pack’
default: : Operation not permitted
default: Do not run Composer as root/super user! See https://getcomposer.org/root for details
default: Installing phpmyadmin/phpmyadmin (4.8.1)
default:
default: [InvalidArgumentException]
default: Project directory ./ is not empty.
Then he should just need to clear his folder and re-provision.
Composer leaves behind .idx files that can't be removed without chmodding sometimes from what I've gathered through googling.
One of the comments on this stack exchange mentions it briefly.
I don't know why this is though.
yes @tomjn it correspond.
@tomjn I haven't removed anything.
This is the log:
vagrant@vvv:~$ ls -al /srv/www/default/database-admin total 4 drwxrwxr-x 1 www-data vagrant 0 Jun 16 10:11 . drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:16 ..
and
vagrant@vvv:~$ ls -al /srv/www/default total 9 drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:16 . drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:14 .. drwxrwxr-x 1 www-data vagrant 0 Jun 14 07:16 dashboard drwxrwxr-x 1 www-data vagrant 0 Jun 16 10:11 database-admin -rwxrwxr-- 1 www-data vagrant 338 Jun 14 06:45 index.php drwxrwxr-x 1 www-data vagrant 0 Apr 12 2015 memcached-admin drwxrwxr-x 1 www-data vagrant 0 May 5 13:48 opcache-status drwxrwxr-x 1 www-data vagrant 0 May 5 09:57 phpinfo drwxrwxr-x 1 www-data vagrant 0 May 5 13:50 webgrind
About the platform configuration I haven't change anything. This is the content of my vvv.custom.yml file:
This file is a YAML formatted file. YAML indenting is done in spaces not
tabs, and whitespace is significant. If you don't stick to this, it will
fail on provision
#
IMPORTANT, if you change this file, you have to reprovision, no exceptions
vagrant reload --provision
#
These are your websites, and their names map on to the folders they're
located in. See the docs for how to define these, and what all the keys
and options are
sites:
The wordpress-default configuration provides a default installation of the
latest version of WordPress.
wordpress-default: repo: https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-default.git hosts:
local.wordpress.test
The wordpress-develop configuration is useful for contributing to WordPress.
wordpress-develop: repo: https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-develop.git hosts:
- src.wordpress-develop.test
build.wordpress-develop.test
support: repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git hosts:
support.test
stripe_connect: repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git hosts:
stripe_connect.test
free_support: repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git hosts:
free_support.test
The following commented out site configuration will create a standard WordPress
site in www/example-site/ available at http://my-example-site.dev.
Remember, whitespace is significant! Tabs and spaces mean different things
example-site:
repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
hosts:
- my-example-site.test
The following commented out site configuration will create a environment useful
for contributions to the WordPress meta team:
wordpress-meta-environment:
repo: https://github.com/WordPress/meta-environment.git
Utilities are system level items rather than sites, that install tools or packages
the core utilities install tools such as phpmyadmin
utilities: core:
- memcached-admin
- opcache-status
- phpmyadmin
- webgrind
I have uploaded the file here: vvv-custom.zip If you want to look inside it for any tests.
@ACatThatPrograms
Out of curiosity what all files were in database-admin? Was there an index.php file? Clearly not now, but after a re-provision verify that there are files inside database-admin including an index.php.
After vagrant up --provision
no index.php file. In this moment I haven't any files in databse-admin folder.
About the database I haven't a database called phpmyadmin, look here: http://prntscr.com/jxxb4x. I try to create it and make a provision again. I'll write again in a few minutes with the test results.
AG
I have created the phpmyadmin dtabase now and make a vagrant reload --provision, but doesn't works. This is the provision log:
andre@DESKTOP-BVPA8EU MINGW64 ~/vagrant-local (master)
$ vagrant reload --provision
__ __ __ __
\ V\ V\ V / Varying Vagrant Vagrants
\_/\_/\_/ v2.2.1-git::master
Docs: https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard: http://vvv.test
==> default: Running triggers before reload ...
==> default: Running trigger: VVV Pre-Reload...
default: Running: inline script
default: Performing Database Backups
default: Database free_support backed up...
default: Database phpmyadmin backed up...
default: Database stripe_connect backed up...
default: Database support backed up...
default: Database wordpress_default backed up...
default: Database wordpress_develop backed up...
==> default: [vagrant-hostsupdater] Removing hosts
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: A newer version of the box 'ubuntu/trusty64' for provider 'virtualbox' is
==> default: available! You currently have version '20180612.0.0'. The latest is version
==> default: '20180614.0.3'. Run `vagrant box update` to update.
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
[default] GuestAdditions 5.2.10 running --- OK.
==> default: Checking for guest additions in VM...
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] Writing the following entries to (C:/WINDOWS/system32/drivers/etc/hosts)
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv.dev # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv.local # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv.localhost # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 local.wordpress.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 local.wordpress.dev # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 src.wordpress-develop.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 build.wordpress-develop.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 src.wordpress-develop.dev # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 build.wordpress-develop.dev # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 support.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 stripe_connect.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] 192.168.50.4 free_support.test # VAGRANT: a3b78aca82d9da175e446e081787432a (default) / 24a378bd-43f1-49a9-808a-d08d9fa4e436
==> default: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /srv/www => C:/Users/andre/vagrant-local/www
default: /var/log => C:/Users/andre/vagrant-local/log
default: /vagrant => C:/Users/andre/vagrant-local
default: /srv/config => C:/Users/andre/vagrant-local/config
default: /srv/database => C:/Users/andre/vagrant-local/database
==> default: Running provisioner: fix-no-tty (shell)...
default: Running: inline script
==> default: Running provisioner: default (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-gh5i1c.sh
default: Network connection detected...
default: Bash profile setup and directories.
default: * Copied /srv/config/bash_profile to /home/vagrant/.bash_profile
default: * Copied /srv/config/bash_aliases to /home/vagrant/.bash_aliases
default: * Copied /srv/config/vimrc to /home/vagrant/.vimrc
default: * Copied /srv/config/subversion-servers to /home/vagrant/.subversion/servers
default: * Copied /srv/config/subversion-config to /home/vagrant/.subversion/config
default: Network connection detected...
default:
default: Main packages check and install.
default: Adding ppa:git-core/ppa repository
default: * php7.2-fpm 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-cli 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-common 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-dev 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php-pear 1:1.10.5+submodules+notgz-1+ubuntu14.04.1+deb.sury.org+1
default: * php-imagick 3.4.3-3+ubuntu14.04.1+deb.sury.org+1
default: * php-memcache 3.0.9~20160311.4991c2f-7+ubuntu14.04.1+deb.sury.org+1
default: * php-memcached 3.0.4+2.2.0-1+ubuntu14.04.1+deb.sury.org+1
default: * php-ssh2 1.1.2+0.13-1+ubuntu14.04.1+deb.sury.org+1
default: * php-xdebug 2.6.0+2.5.5-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-bcmath 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-curl 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-gd 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-mbstring 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-mysql 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-imap 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-json 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-soap 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-xml 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * php7.2-zip 7.2.6-1+ubuntu14.04.1+deb.sury.org+1
default: * nginx 1.13.12-1~trusty
default: * memcached 1.4.14-0ubuntu9.3
default: * mariadb-server 10.1.32+maria-1~trusty
default: * imagemagick 8:6.7.7.10-6ubuntu3.9
default: * subversion 1.8.8-1ubuntu3.3
default: * git 1:2.17.0-1~ppa0~ubuntu14.04.1
default: * zip 3.0-8
default: * unzip 6.0-9ubuntu1.5
default: * ngrep 1.45.ds2-12
default: * curl 7.35.0-1ubuntu2.15
default: * make 3.81-8.2ubuntu3
default: * vim 2:7.4.052-1ubuntu3.1
default: * colordiff 1.0.13-1
default: * postfix 2.11.0-1ubuntu1.2
default: * python-pip 1.5.4-1ubuntu4
default: * ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.12
default: * gettext 0.18.3.1-1ubuntu3
default: * graphviz 2.36.0-0ubuntu3.2
default: * dos2unix 6.0.4-1
default: * g++ 4:4.8.2-1ubuntu6
default: * nodejs 6.14.2-1nodesource1
default: * libsqlite3-dev 3.8.2-1ubuntu2.1
default: Linked custom apt sources
default: No apt packages to install.
default: php7.2-fpm stop/waiting
default: php7.2-fpm start/running, process 9178
default: php7.0-fpm stop/waiting
default: php7.0-fpm start/running, process 9195
default:
default: Updating nvm...
default: From https://github.com/creationix/nvm
default: 0cdc184..41dc421 master -> origin/master
default: error: The following untracked working tree files would be overwritten by checkout:
default: .dockerignore
default: .editorconfig
default: .gitattributes
default: .github/ISSUE_TEMPLATE.md
default: .gitignore
default: .mailmap
default: .npmrc
default: .travis.yml
default: CONTRIBUTING.md
default: Dockerfile
default: LICENSE.md
default: Makefile
default: README.md
default: ROADMAP.md
default: bash_completion
default: install.sh
default: nvm-exec
default: nvm.sh
default: package.json
default: test/common.sh
default: test/fast/Aliases/circular/nvm_resolve_alias
default: test/fast/Aliases/circular/nvm_resolve_local_alias
default: test/fast/Aliases/circular/setup
default: test/fast/Aliases/circular/teardown
default: test/fast/Aliases/lts/setup_dir
default: test/fast/Aliases/lts/teardown_dir
default: test/fast/Aliases/nvm_ensure_default_set
default: test/fast/Aliases/nvm_resolve_alias
default: test/fast/Aliases/nvm_resolve_local_alias
default: test/fast/Aliases/setup
default: test/fast/Aliases/teardown
default: test/fast/Listing paths/teardown
default: test/fast/Listing versions/Using a nonstandard IFS should not break
default: test/fast/Listing versions/teardown
default: test/fast/Sourcing nvm.sh should make the nvm command available.
default: test/fast/Sourcing nvm.sh should not modify parameters of caller
default: test/fast/Unit tests/iojs_version_has_solaris_binary
default: test/fast/Unit tests/mocks/iojs.org-dist-index.tab
default: test/fast/Unit tests/mocks/nodejs.org-dist-index.tab
default: test/fast/Unit tests/mocks/nvm ls-remote iojs.txt
default: test/fast/Unit tests/mocks/nvm ls-remote lts.txt
default: test/fast/Unit tests/mocks/nvm ls-remote node.txt
default: test/fast/Unit tests/mocks/nvm ls-remote.txt
default: test/fast/Unit tests/mocks/nvm_ls_remote LTS argon.txt
default: test/fast/Unit tests/mocks/nvm_ls_remote LTS.txt
default: test/fast/Unit tests/mocks/nvm_ls_remote stable.txt
default: test/fast/Unit tests/mocks/nvm_ls_remote.txt
default: test/fast/Unit tests/mocks/nvm_ls_remote_iojs.txt
default: test/fast/Unit tests/mocks/nvm_make_alias LTS alias calls.txt
default: test/fast/Unit tests/mocks/nvm_print_implicit_alias remote stable.txt
default: test/fast/Unit tests/node_version_has_solaris_binary
default: test/fast/Unit tests/nvm ls-remote
default: test/fast/Unit tests/nvm version-remote
default: test/fast/Unit tests/nvm_add_iojs_prefix
default: test/fast/Unit tests/nvm_alias
default: test/fast/Unit tests/nvm_alias_path
default: test/fast/Unit tests/nvm_change_path
default: test/fast/Unit tests/nvm_checksum
default: test/fast/Unit tests/nvm_clang_version
default: test/fast/Unit tests/nvm_command_info
default: test/fast/Unit tests/nvm_compare_checksum
default: test/fast/Unit tests/nvm_compute_checksum
default: test/fast/Unit tests/nvm_curl_libz_support
default: test/fast/Unit tests/nvm_curl_use_compression
default: test/fast/Unit tests/nvm_curl_version
default: test/fast/Unit tests/nvm_default_packages
default: test/fast/Unit tests/nvm_die_on_prefix
default: test/fast/Unit tests/nvm_ensure_default_set
default: test/fast/Unit tests/nvm_ensure_version_installed
default: test/fast/Unit tests/nvm_ensure_version_prefix
default: test/fast/Unit tests/nvm_find_up
default: test/fast/Unit tests/nvm_format_version
default: test/fast/Unit tests/nvm_get_arch
default: test/fast/Unit tests/nvm_get_checksum
default: test/fast/Unit tests/nvm_get_checksum_alg
default: test/fast/Unit tests/nvm_get_latest missing curl or wget
default: test/fast/Unit tests/nvm_get_minor_version
default: test/fast/Unit tests/nvm_get_mirror
default: test/fast/Unit tests/nvm_has
default: test/fast/Unit tests/nvm_has_non_aliased
default: test/fast/Unit tests/nvm_has_solaris_binary
default: test/fast/Unit tests/nvm_has_system_iojs
default: test/fast/Unit tests/nvm_has_system_node
default: test/fast/Unit tests/nvm_install_latest_npm
default: test/fast/Unit tests/nvm_iojs_prefix
default: test/fast/Unit tests/nvm_is_alias
default: test/fast/Unit tests/nvm_is_iojs_version
default: test/fast/Unit tests/nvm_is_merged_node_version
default: test/fast/Unit tests/nvm_is_natural_num
default: test/fast/Unit tests/nvm_is_valid_version
default: test/fast/Unit tests/nvm_ls_current
default: test/fast/Unit tests/nvm_ls_remote
default: test/fast/Unit tests/nvm_ls_remote LTS aliases
default: test/fast/Unit tests/nvm_ls_remote_iojs
default: test/fast/Unit tests/nvm_make_alias
default: test/fast/Unit tests/nvm_node_prefix
default: test/fast/Unit tests/nvm_num_version_groups
default: test/fast/Unit tests/nvm_print_alias_path
default: test/fast/Unit tests/nvm_print_default_alias
default: test/fast/Unit tests/nvm_print_implicit_alias errors
default: test/fast/Unit tests/nvm_print_implicit_alias success
default: test/fast/Unit tests/nvm_print_npm_version
default: test/fast/Unit tests/nvm_remote_version
default: test/fast/Unit tests/nvm_remote_versions
default: test/fast/Unit tests/nvm_strip_iojs_prefix
default: test
default: error: The following untracked working tree files would be removed by checkout:
default: test/fast/Unit tests/nvm_install_no_progress_bar
default: test/fast/nvm should remove the last trailing slash in $NVM_DIR
default: Please move or remove them before you switch branches.
default: Aborting
default: Installing/updating npm...
default: /usr/bin/npm -> /usr/lib/node_modules/npm/bin/npm-cli.js
default: /usr/bin/npx -> /usr/lib/node_modules/npm/bin/npx-cli.js
default: + npm@6.1.0
default: updated 1 package in 25.667s
default: Installing/updating npm-check-updates...
default: /usr/bin/npm-check-updates -> /usr/lib/node_modules/npm-check-updates/bin/npm-check-updates
default: /usr/bin/ncu -> /usr/lib/node_modules/npm-check-updates/bin/ncu
default: + npm-check-updates@2.14.2
default: updated 2 packages in 18.861s
default: ack-grep already installed
default: Updating Composer...
default: You are already using composer version 1.6.5 (stable channel).
default: Changed current directory to /usr/local/src/composer
default: ./composer.json has been updated
default: Changed current directory to /usr/local/src/composer
default: Changed current directory to /usr/local/src/composer
default: Loading composer repositories with package information
default: Updating dependencies (including require-dev)
default: Nothing to install or update
default: Generating autoload files
default: Updating Grunt CLI
default: Adding graphviz symlink for Webgrind...
default: Installing Shyaml for bash provisioning..
default: Requirement already satisfied (use --upgrade to upgrade): shyaml in /usr/local/lib/python2.7/dist-packages
default: Cleaning up...
default: Setup configuration files...
default: * Copied /srv/config/init/vvv-start.conf to /etc/init/vvv-start.conf
default: sending incremental file list
default: deleting vvv-auto-wordpress-develop-provision-2b2bf03d9cfabafc0746df486a1377ae.conf
default: deleting vvv-auto-wordpress-default-provision-43ccb1d415c7a942e55797dff3e109bd.conf
default: deleting vvv-auto-support-provision-fd9dc2b2694ef8cd9db815e4ff5b25ef.conf
default: deleting vvv-auto-stripe_connect-provision-be6056806176a38405edd4bdd644f8c0.conf
default: deleting vvv-auto-free_support-provision-0d4dd633b9dbf8b48eed8255aea330d3.conf
default: default.conf
default: local-nginx-example.conf-sample
default: sent 1.85K bytes received 426 bytes 4.56K bytes/sec
default: total size is 3.89K speedup is 1.71
default: * Copied /srv/config/nginx-config/nginx.conf to /etc/nginx/nginx.conf
default: * Copied /srv/config/nginx-config/nginx-wp-common.conf to /etc/nginx/nginx-wp-common.conf
default: * Rsync'd /srv/config/nginx-config/sites/ to /etc/nginx/custom-sites
default: * RVM 1.29.3
default: * Mailcatcher 0.6.5
default: * Mailcatcher upstart already configured.
default: * Mailcatcher php7 fpm already configured.
default: * Copied /srv/config/php-config/php7.2-fpm.conf to /etc/php/7.2/fpm/php-fpm.conf
default: * Copied /srv/config/php-config/php7.2-www.conf to /etc/php/7.2/fpm/pool.d/www.conf
default: * Copied /srv/config/php-config/php7.2-custom.ini to /etc/php/7.2/fpm/conf.d/php-custom.ini
default: * Copied /srv/config/php-config/opcache.ini to /etc/php/7.2/fpm/conf.d/opcache.ini
default: * Copied /srv/config/php-config/xdebug.ini to /etc/php/7.2/mods-available/xdebug.ini
default: * Copied /srv/config/memcached-config/memcached.conf to /etc/memcached.conf and /etc/memcached_default.conf
default: Restart services...
default: * Restarting nginx nginx
default: ...done.
default: Restarting memcached:
default: memcached_default.
default: mailcatcher stop/waiting
default: mailcatcher start/running, process 9678
default: php7.2-fpm stop/waiting
default: php7.2-fpm start/running, process 9857
default: php7.0-fpm stop/waiting
default: php7.0-fpm start/running, process 9874
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: * Skipped import of free_support - tables exist
default: mysql -u root -proot phpmyadmin < phpmyadmin.sql
default: * Import of phpmyadmin successful
default: * Skipped import of stripe_connect - tables exist
default: * Skipped import of support - tables exist
default: * Skipped import of wordpress_default - tables exist
default: * Skipped import of wordpress_develop - tables exist
default: Databases imported
default: Network connection detected...
default:
default: Installing/updating wp-cli and debugging tools
default: Updating wp-cli...
default: Downloading from https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli-nightly.phar...
default: md5 hash verified: 6aa506babbbc021f2fc5af6c93db5e9a
default: New version works. Proceeding to replace.
default: Success: Updated WP-CLI to the latest nightly release.
default: Install/Update PHP_CodeSniffer (phpcs), see https://github.com/squizlabs/PHP_CodeSniffer
default: Install/Update WordPress-Coding-Standards, sniffs for PHP_CodeSniffer, see https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards
default: Loading composer repositories with package information
default:
default: Reading composer.json of automattic/vipwpcs (0.1.0)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (0.2.0)
default:
default: Reading composer.json of automattic/vipwpcs (0.2.1)
default:
default: Reading composer.json of automattic/vipwpcs (0.2.2)
default:
default: Reading composer.json of automattic/vipwpcs (0.2.3)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (Sections-and-severity)
default:
default: Reading composer.json of automattic/vipwpcs (add-create-function-sniff)
default:
default: Reading composer.json of automattic/vipwpcs (add-create-function-sniff-2)
default:
default: Reading composer.json of automattic/vipwpcs (add-dynamic-calls-sniff)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (add-filters-always-return-sniff)
default:
default: Reading composer.json of automattic/vipwpcs (add-js-restricted-functions.php)
default:
default: Reading composer.json of automattic/vipwpcs (add-merge-conflict-sniff.php)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (add-zoninator-sniff)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (fix-114-allow-unused-caught-exceptions)
default:
default: Reading composer.json of automattic/vipwpcs (fix-25/flag-robotstxt-action)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (master)
default:
default:
default:
default: Reading composer.json of automattic/vipwpcs (vip-go)
default:
default: Reading composer.json of automattic/vipwpcs (wpcs_vip_migration)
default:
default:
default:
default: Updating dependencies (including require-dev)
default: Package operations: 0 installs, 1 update, 0 removals
default: - Updating automattic/vipwpcs dev-master (3c29738 => 2160641):
default: Checking out 216064113f
default: Writing lock file
default: Using config file: /srv/www/phpcs/CodeSniffer.conf
default:
default: Config value "installed_paths" updated successfully; old value was "./CodeSniffer/Standards/WordPress/,./CodeSniffer/Standards/VIP-Coding-Standards/,./CodeSniffer/Standards/PHPCompatibility/"
default: Using config file: /srv/www/phpcs/CodeSniffer.conf
default:
default: Config value "default_standard" updated successfully; old value was "WordPress-Core"
default: The installed coding standards are MySource, PEAR, PSR1, PSR12, PSR2, Squiz, Zend, WordPress, WordPress-Core, WordPress-Docs, WordPress-Extra, WordPress-VIP, WordPress-VIP-Go, WordPressVIPMinimum and PHPCompatibility
default: Network connection detected...
default:
default:
default: Cleaning the virtual machine's /etc/hosts file...
default: -----------------------------
default: Provisioning complete in 336 seconds
default: For further setup instructions, visit http://vvv.test
==> default: Running provisioner: dashboard (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-7ayuzr.sh
default: Updating dashboard...
==> default: Running provisioner: utility-source-core (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-19pp5rm.sh
default: Updating core resources...
==> default: Running provisioner: utility-core-memcached-admin (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-ve74n9.sh
default: phpMemcachedAdmin already installed.
==> default: Running provisioner: utility-core-opcache-status (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-1p2ilzx.sh
default: Updating Opcache Status
default: From https://github.com/rlerdorf/opcache-status
default: * branch master -> FETCH_HEAD
default: Already up to date.
default: Current branch master is up to date.
==> default: Running provisioner: utility-core-phpmyadmin (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-f95xa3.sh
==> default: Running provisioner: utility-core-webgrind (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-11d5vxf.sh
default: Updating webgrind...
default: From https://github.com/jokkedk/webgrind
default: * branch master -> FETCH_HEAD
default: Already up to date.
default: Current branch master is up to date.
==> default: Running provisioner: site-wordpress-default (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-rtcvat.sh
default: Updating wordpress-default...
default: Creating database 'wordpress_default' (if it's not already there)
default: DB operations done.
default: Updating WordPress Stable...
default: Updating to version 5.0-alpha-43320 (en_US)...
default: Downloading update from https://wordpress.org/nightly-builds/wordpress-latest.zip...
default: Unpacking the update...
default: Cleaning up files...
default: File removed: wp-includes/random_compat/random_bytes_openssl.php
default: 1 files cleaned up.
default: Success: WordPress updated successfully.
default: Adding domains to the virtual machine's /etc/hosts file...
default: * Added local.wordpress.dev from /srv/www/wordpress-default/provision/vvv-hosts
default: * Added local.wordpress.test from /srv/www/wordpress-default/provision/vvv-hosts
default: * Added local.wordpress.test from /vagrant/vvv-custom.yml
default: * Restarting nginx nginx
default: ...done.
==> default: Running provisioner: site-wordpress-develop (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-125dl3z.sh
default: Updating wordpress-develop...
default: Creating database 'wordpress_develop' (if it's not already there)
default: DB operations done.
default: Updating WordPress develop...
default: Updating '.':
default: Skipped 'package-lock.json' -- Node remains in conflict
default: U src/js/_enqueues/lib/auth-check.js
default: U src/js/_enqueues/lib/emoji-loader.js
default: U src/js/_enqueues/wp/emoji.js
default: U src/wp-admin/includes/admin-filters.php
default: U src/wp-admin/includes/class-wp-community-events.php
default: U src/wp-admin/includes/file.php
default: U src/wp-admin/includes/misc.php
default: U src/wp-admin/includes/plugin.php
default: U src/wp-admin/includes/template.php
default: U src/wp-admin/privacy.php
default: U src/wp-includes/rest-api/fields/class-wp-rest-comment-meta-fields.php
default: U src/wp-includes/rest-api/fields/class-wp-rest-meta-fields.php
default: U src/wp-includes/rest-api/fields/class-wp-rest-post-meta-fields.php
default: U src/wp-includes/rest-api/fields/class-wp-rest-term-meta-fields.php
default: U src/wp-includes/rest-api/fields/class-wp-rest-user-meta-fields.php
default: U src/wp-includes/capabilities.php
default: U src/wp-includes/comment-template.php
default: U src/wp-includes/formatting.php
default: U src/wp-includes/general-template.php
default: U src/wp-includes/meta.php
default: U src/wp-includes/post.php
default: U src/wp-includes/taxonomy.php
default: U src/wp-includes/user.php
default: A tests/phpunit/data/languages/ja_JP.mo
default: A tests/phpunit/data/languages/ja_JP.po
default: U tests/phpunit/includes/bootstrap.php
default: U tests/phpunit/tests/admin/includesCommunityEvents.php
default: U tests/phpunit/tests/formatting/BlogInfo.php
default: U tests/phpunit/tests/formatting/Emoji.php
default: U tests/phpunit/tests/meta/registerMeta.php
default: U tests/phpunit/tests/post/meta.php
default: U tests/phpunit/tests/rest-api/rest-post-meta-fields.php
default: U tests/phpunit/tests/rest-api/rest-term-meta-fields.php
default: U tests/phpunit/tests/term/meta.php
default: U tests/phpunit/tests/comment.php
default: U tests/phpunit/tests/db.php
default: U tests/phpunit/tests/l10n.php
default: U tests/qunit/fixtures/wp-api-generated.js
default: U package.json
default:
default: Fetching external item into 'tests/phpunit/data/plugins/wordpress-importer':
default: Updated external to revision 1896913.
default: At revision 43378.
default: Summary of conflicts:
default: Skipped paths: 1
default: Updating npm packages...
default: Adding domains to the virtual machine's /etc/hosts file...
default: * Added src.wordpress-develop.test from /srv/www/wordpress-develop/provision/vvv-hosts
default: * Added build.wordpress-develop.test from /srv/www/wordpress-develop/provision/vvv-hosts
default: * Added src.wordpress-develop.dev from /srv/www/wordpress-develop/provision/vvv-hosts
default: * Added build.wordpress-develop.dev from /srv/www/wordpress-develop/provision/vvv-hosts
default: * Added src.wordpress-develop.test from /vagrant/vvv-custom.yml
default: * Added build.wordpress-develop.test from /vagrant/vvv-custom.yml
default: * Restarting nginx nginx
default: ...done.
==> default: Running provisioner: site-support (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-xionvg.sh
default: Updating support...
default: Creating database 'support' (if it's not already there)
default: DB operations done.
default: Updating WordPress Stable...
default: Success: WordPress is up to date.
default: Adding domains to the virtual machine's /etc/hosts file...
default: * Added support.test from /vagrant/vvv-custom.yml
default: * Restarting nginx nginx
default: ...done.
==> default: Running provisioner: site-stripe_connect (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-djzg6h.sh
default: Updating stripe_connect...
default: Creating database 'stripe_connect' (if it's not already there)
default: DB operations done.
default: Updating WordPress Stable...
default: Success: WordPress is up to date.
default: Adding domains to the virtual machine's /etc/hosts file...
default: * Added stripe_connect.test from /vagrant/vvv-custom.yml
default: * Restarting nginx nginx
default: ...done.
==> default: Running provisioner: site-free_support (shell)...
default: Running: C:/Users/andre/AppData/Local/Temp/vagrant-shell20180622-11684-uo7j0o.sh
default: Updating free_support...
default: Creating database 'free_support' (if it's not already there)
default: DB operations done.
default: Updating WordPress Stable...
default: Success: WordPress is up to date.
default: Adding domains to the virtual machine's /etc/hosts file...
default: * Added free_support.test from /vagrant/vvv-custom.yml
default: * Restarting nginx nginx
default: ...done.
==> default: Running provisioner: shell...
default: Running: inline script
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: Running provisioner: shell...
default: Running: inline script
default: * Restarting nginx nginx
default: ...done.
==> default: Running triggers after reload ...
==> default: Running trigger: VVV Post-Reload...
default: Running: inline script
but nothing changes:
vagrant@vvv:~$ ls -al /srv/www/default/database-admin
total 4
drwxrwxr-x 1 www-data vagrant 0 Jun 16 10:11 .
drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:16 ..
vagrant@vvv:~$ ls -al /srv/www/default
total 25
drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:16 .
drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:14 ..
drwxrwxr-x 1 www-data vagrant 4096 Jun 14 07:16 dashboard
drwxrwxr-x 1 www-data vagrant 0 Jun 16 10:11 database-admin
-rwxrwxr-- 1 www-data vagrant 338 Jun 14 06:45 index.php
drwxrwxr-x 1 www-data vagrant 4096 Apr 12 2015 memcached-admin
drwxrwxr-x 1 www-data vagrant 4096 May 5 13:48 opcache-status
drwxrwxr-x 1 www-data vagrant 0 May 5 09:57 phpinfo
drwxrwxr-x 1 www-data vagrant 4096 May 5 13:50 webgrind
Look here: http://prntscr.com/jxxmcf
AG
@ACatThatPrograms solution works for me.
Before, I upgraded Vagrant and VVV.
I think it is happening during updating, as it was after an update that I noticed a problem. I hadn't used PHPMyAdmin prior to updating though, so I'm not 100% sure if that is the root cause.
However if @marcelo2605 's issue started that way, it may be a starting point to recreating at least a version of the issues at hand. Thanks for your input, and I'm glad you got yours straightened out.
@andreagrillo 's problem, however, appears to be slightly different. His provisioner isn't running correctly according to his logs as was noted earlier in the thread and I'm not sure why that is. It just seems to skip over running the provisioner for phpmyadmin. I honestly can't remember if I experienced this issue at all prior to digging around before realizing the idx/git packages were causing my issue.
I think the best attempt at recreating at least one of these problems is to pull an old version and try it out to see if one of these, if any, is recreated through updating. I will try to when I have some time unless someone beats me to it.
So a TLDR:
Solutions:
composer update
insteadThis should be fixed in https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/commit/87ccdc350049bf7267a7d0344dc9caf5bb035dc4 which switched back to the older method but with PHPMyAdmin 4.8.1
This does mean that newer PHPMyAdmin releases will require somebody to manually update the file however. Reprovisioning should bring in the new version.
There's also the problem that existing users with older versions of PHPMyAdmin won't be updated as there's no mechanism for updating PHPMyAdmin now
Maybe for the update of VVV we can do a check based if the file RELEASE-DATE-4.8.1
exist inside the folder in case update to the latest that in our case is 4.8.1.
SO we can avoid the problem with old users.
Hi there,
I launch vv box update and then vagrant reload --provision....nothing works now. The provision stop during phpMyAdmin download and now nothing works. You find the provision log attached:
Any idea ? AG
I do not recommend running a box update, I also see you're still on the master
branch, fixes are pushed to the develop
branch not the master
branch, you will see no changes until 2.3
is released unless you switch branches.
As an aside, .log
files are an executable extension on MacOS, and can't be opened on mobile phones. I strongly recommend using a gist instead, or using a .txt
format instead
develop
branchhmmm looking at the log I see this:
default: Removing older phpMyAdmin install
default: Downloading phpMyAdmin 4.8.1
default: cp:
default: cannot stat ‘/vagrant/provision/resources/core/phpmyadmin/config.inc.php’
default: : No such file or directory
Which should not be possible as the file is present here:
https://github.com/Varying-Vagrant-Vagrants/vvv-utilities/tree/master/phpmyadmin
Did you delete the file or modify anything under the provision
folder? If the provision/resources/core
folder has local modifications of any kind that's a serious issue that needs resolving immediately. Delete the provision/resources/core
folder and reprovision to pull it down again
Hi @tomjn I switch vvv to develop branch and restore the phpmyadmin folder but nothing, 403 forbiden again.
This is the last log:
when you vagrant up, did u go to vvv.test and click on phpmyadmin on the right side.
i have the same thing that you are describing and my works fine. those files are the defaults.
@andreagrillo can you run vagrant ssh
, then run these commands 1 by 1 and post the output and confirm if the result is the same or fixed? If it fails, which command does it fail at?
sudo su
rm -rf /srv/www/default/database-admin/*
cd /srv/www/default
wget -q -O phpmyadmin.tar.gz "https://files.phpmyadmin.net/phpMyAdmin/4.8.1/phpMyAdmin-4.8.1-all-languages.tar.gz"
tar -xf phpmyadmin.tar.gz
mv phpMyAdmin-4.8.1-all-languages database-admin
rm phpmyadmin.tar.gz
cp "/vagrant/provision/resources/core/phpmyadmin/config.inc.php" "/srv/www/default/database-admin/"
By all accounts, this should work, as it's the same process that was used original but with a newer PHPMyAdmin.
Also at any point, did you run vagrant destroy
and reprovision? My only unconfirmed theory is that somehow there are files inside the VM in the locations of the mapped folders. I do not know how those would have gotten there, or how to test for them
@tomjn I have similar problem with 403 error
This is what I get after tar -xf phpmyadmin.tar.gz
root@vvv:/srv/www/default# tar -xf phpmyadmin.tar.gz
tar: phpMyAdmin-4.8.1-all-languages/vendor/bin/lint-query: Cannot create symlink to ‘../phpmyadmin/sql-parser/bin/lint-query’: Protocol error
tar: phpMyAdmin-4.8.1-all-languages/vendor/bin/highlight-query: Cannot create symlink to ‘../phpmyadmin/sql-parser/bin/highlight-query’: Protocol error
tar: Exiting with failure status due to previous errors
root@vvv:/srv/www/default#
hmm there shouldn't be any symlinks in that location
Hi @tomjn
Thanksssss! Working fine now. I only need to run two additional command:
cp -rf phpMyAdmin-4.8.1-all-languages/* .
rm -rf phpMyAdmin-4.8.1-all-languages/
because I see that no files inside database-admin folder.
However, without the last two commands, all working fine but you need to access to phpMyAdmin with this url:
http://vvv.test/database-admin/phpMyAdmin-4.8.1-all-languages/ instead of http://vvv.test/database-admin/
Thanks for all Tom :-)
@andreagrillo I've adjusted the provisioner to use the /tmp
folder, and use cp
, which should make it less sensitive to permissions etc
Can you test if this works for you? Move your existing folder somewhere else so you can restore it if things don't work, then reprovision
Likewise, @peterisj can you do the same?
For reference, you can run just the phpmyadmin provisioner with this command:
vagrant provision --provision-with="utility-source-core"
vagrant provision --provision-with="utility-core-phpmyadmin"
The first command updates the core utility, the second runs the phpmyadmin provisioner
This works
vagrant provision --provision-with="utility-source-core"
vagrant provision --provision-with="utility-core-phpmyadmin"
I get some symlink error, but now http://vvv.test/database-admin/ working correct
default: Running provisioner: utility-core-phpmyadmin (shell)...
default: Running: C:/Users/peteris/AppData/Local/Temp/vagrant-shell20180705- 14280-1n9dzv9.sh
default: Checking phpMyAdmin
default: Removing older phpMyAdmin install from /srv/www/default/database-ad min
default: Downloading phpMyAdmin 4.8.1
default: Extracting phpMyAdmin 4.8.1 into /tmp
default: Copying phpMyAdmin into place
default: cp:
default: cannot create symbolic link ‘/srv/www/default/database-admin/vendor/bin/highlight-query’
default: : Protocol error
default: cp:
default: cannot create symbolic link ‘/srv/www/default/database-admin/vendor/bin/lint-query’
default: : Protocol error
default: Cleaning up after phpMyAdmin
default: phpMyAdmin setup complete
Thank You!
@peterisj which file system is the host filesystem using?
@peterisj if you modify provision/resources/core/phpmyadmin/provision.sh
to this:
#!/usr/bin/env bash
DIR=`dirname $0`
echo "Checking phpMyAdmin"
# Download phpMyAdmin
if [[ ! -f /srv/www/default/database-admin/RELEASE-DATE-4.8.1 ]]; then
echo "Removing older phpMyAdmin install from /srv/www/default/database-admin"
rm -rf /srv/www/default/database-admin/*
echo "Downloading phpMyAdmin 4.8.1"
cd /tmp
wget -q -O phpmyadmin.tar.gz "https://files.phpmyadmin.net/phpMyAdmin/4.8.1/phpMyAdmin-4.8.1-all-languages.tar.gz"
echo "Extracting phpMyAdmin 4.8.1 into /tmp"
tar -xf phpmyadmin.tar.gz
echo "Copying phpMyAdmin into place"
mkdir -p /srv/www/default/database-admin
cp -rfL /tmp/phpMyAdmin-4.8.1-all-languages/* /srv/www/default/database-admin/
echo "Cleaning up after phpMyAdmin"
rm -rf /tmp/phpMyAdmin-4.8.1-all-languages
rm -f /tmp/phpmyadmin.tar.gz
echo "phpMyAdmin setup complete"
else
echo "PHPMyAdmin already installed."
fi
cp "${DIR}/config.inc.php" "/srv/www/default/database-admin/"
Then run vagrant provision --provision-with="utility-core-phpmyadmin"
, does that correct the symbolic link issue?
@tomjn Hi I have tried what you wrote before but I received this error:
default: fatal: unable to access 'https://github.com/Varying-Vagrant-Vagrants/vvv-utilities.git/': Could not resolve host: github.com
Easy bug, I have added a new site and after vagrant reload --provision I can't access to PHPMyAdmin, I receive a 403 Forbidden error page. Only This.
All other modules working fine, sites working fine....no other issue.
Any Idea ? Thanks for your time
AG