Closed debabratakarfa closed 4 years ago
It looks like your computer couldn't connect to mirror.herrbischoff.com
:
Unable to connect to mirror.herrbischoff.com:https:
Double check that this site is up and reachable. If it persists, switch to a different network with a different ISP/routing, or, wait a bit and try again. Basically all the same things you'd do if google.com wouldn't load on your computer except it's the apt
command not Chrome/Firefox telling you
Hey @tomjn
Thanks, I check it is not working, mirror.herrbischoff.com
I hope it working from my network again.
Thanks
It's up for me, in the meantime, https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1993 might help with this once it's implemented, I'm unsure, give some of these alternative mirrors a test:
I have one VPN service and I connect to that, then try to run provisioning and it works.
But few issues,
default: Performing Database Backups
default: ERROR
default: 1524 (HY000)
default: : Plugin 'unix_socket' is not loaded
and
ERROR 1524 (HY000): Plugin 'unix_socket' is not loaded
default: ---------------------------------------------
default:
default: ! Site provisioner failed! Check the full log for more details
default:
default: ---------------------------------------------
default: * Warning: An nginx config was not found at .vvv/vvv-nginx.conf provision/vvv-nginx.conf or vvv-nginx.conf, searching 3 folders down, please be patient...
default: ! Warning: No nginx config was found, VVV will not know how to serve this site
default: * Adding domains to the virtual machine's /etc/hosts file...
default: * Adding hosts from the VVV config entry
default: - Added reelrollers.test from /vagrant/config.yml
default: * Reloading Nginx
default: ! reelrollers provisioning had some issues, check the log as the site may not function correctly, provisioning took 3 seconds
Sounds like problems caused by the failure of the main provisioner earlier, I recommend you to turn it off with a vagrant halt, then vagrant up --provision
On Wed, Mar 25, 2020 at 12:58 PM Debabrata Karfa notifications@github.com wrote:
I have one VPN service and I connect to that, then try to run provisioning and it works.
But few issues,
default: Performing Database Backups default: ERROR default: 1524 (HY000) default: : Plugin 'unix_socket' is not loaded
and
ERROR 1524 (HY000): Plugin 'unix_socket' is not loaded default: --------------------------------------------- default: default: ! Site provisioner failed! Check the full log for more details default: default: --------------------------------------------- default: Warning: An nginx config was not found at .vvv/vvv-nginx.conf provision/vvv-nginx.conf or vvv-nginx.conf, searching 3 folders down, please be patient... default: ! Warning: No nginx config was found, VVV will not know how to serve this site default: Adding domains to the virtual machine's /etc/hosts file... default: Adding hosts from the VVV config entry default: - Added reelrollers.test from /vagrant/config.yml default: Reloading Nginx default: ! reelrollers provisioning had some issues, check the log as the site may not function correctly, provisioning took 3 seconds
— 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/2092#issuecomment-603824159, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZ4GQEHL2MIJOVAWQBDRJH5XRANCNFSM4LTNGOQA .
I did
default: * Creating the `wordpress-one` database if it doesn't already exist, and granting the wp user access
default: ERROR
default: 1524 (HY000)
default: : Plugin 'unix_socket' is not loaded
default: ERROR
default: 1524 (HY000): Plugin 'unix_socket' is not loaded
default: ERROR
default: 1524 (HY000): Plugin 'unix_socket' is not loaded
default: * Error - Create `wordpress-one` database via init-custom.sql before attempting import
default: * Creating the `wordpress-two` database if it doesn't already exist, and granting the wp user access
default: ERROR
default: 1524 (HY000): Plugin 'unix_socket' is not loaded
default: ERROR
default: 1524 (HY000): Plugin 'unix_socket' is not loaded
default: ERROR
default: 1524 (HY000): Plugin 'unix_socket' is not loaded
default: * Error - Create `wordpress-two` database via init-custom.sql before attempting import
default: * Databases imported
default: * Testing network connection
Was this a fresh VM? Or an existing VM that suddenly encountered these issues?
The unix_socket
issue appears to be unrelated, this SO answer might have the solution https://stackoverflow.com/questions/37879448/mysql-fails-on-mysql-error-1524-hy000-plugin-auth-socket-is-not-loaded
Stack OverflowMy local environment is: fresh Ubuntu 16.04 with PHP 7 with installed MySQL 5.7 sudo apt-get install mysql-common mysql-server When I tried to login to MySQL (via CLI): mysql -u root -p I came
A not fresh one, it is an old one and running yesterday, add a new site and run provisioning.
@debabratakarfa the develop
branch got updated with more stringent networking checks, it'll check multiple domains now not just the launchpad PPA. There's also changes to the DB root password checks
Can you pull down the latest and do a vagrant reload --provision
?
I did, but got this error.
default: ! Main packages check and install failed, halting provision
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
I wish I not take this setup, now again I have to install a fresh VVV again.
@debabratakarfa can you post the full output? The part you quoted isn't the error message, it's the bit that comes after the error, I can't tell why it failed from what you've shared. Always include the full output, we can't help you if you don't include the full output
Wait, I am sharing more info with you.
First I run vagrant up --provision
then I got the above mention error.
Now I run vagrant reload --provision
and I am going the share log file with you.
First I run
vagrant up --provision
then I got the above mention error.
Log file
[38;5;2m * Beginning Main VVV Provisioner, if this is the first provision this may take a few minutes[0m
* Bash profile setup and directories.
* Setting ownership of files in /home/vagrant to vagrant
* Copying /srv/config/bash_profile to /home/vagrant/.bash_profile
* Copying /srv/config/bash_aliases to /home/vagrant/.bash_aliases
* Copying /srv/config/bash_aliases to /root/.bash_aliases
* Copying /srv/config/vimrc to /home/vagrant/.vimrc
* Copying /srv/config/subversion-servers to /home/vagrant/.subversion/servers
* Copying /srv/config/subversion-config to /home/vagrant/.subversion/config
* Copying /srv/config/ssh_known_hosts to /etc/ssh/ssh_known_hosts
* Copying /srv/config/sshd_config to /etc/ssh/sshd_config
* Reloading SSH Daemon
* Testing network connection to https://ppa.launchpad.net
[38;5;2m * Succesful Network connection to https://ppa.launchpad.net detected...[0m
* Testing network connection to https://mirror.herrbischoff.com
[38;5;2m * Succesful Network connection to https://mirror.herrbischoff.com detected...[0m
* Testing network connection to https://wordpress.org
[38;5;2m * Succesful Network connection to https://wordpress.org detected...[0m
* Testing network connection to https://github.com
[38;5;2m * Succesful Network connection to https://github.com detected...[0m
* Testing network connection to https://raw.githubusercontent.com
[38;5;2m * Succesful Network connection to https://raw.githubusercontent.com detected...[0m
* Testing network connection to https://getcomposer.org
[38;5;2m * Succesful Network connection to https://getcomposer.org detected...[0m
[38;5;2m * Network checks succeeded[0m
* Main packages check and install.
* git-core/ppa already present, skipping
* Setting up MySQL configuration file links...
* mysql group exists
* mysql user present and has uid 9001
uid=9001(mysql) gid=9001(mysql) groups=9001(mysql),115(vboxsf)
* Copying /srv/config/mysql-config/vvv-core.cnf to /etc/mysql/conf.d/vvv-core.cnf
* Copying custom apt sources
* Checking Apt Keys
* Running apt-get update...
Ign:1 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 InRelease
Hit:2 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 Release
Hit:3 https://deb.nodesource.com/node_10.x bionic InRelease
Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Hit:7 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:8 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Hit:9 http://ppa.launchpad.net/varying-vagrant-vagrants/php/ubuntu bionic InRelease
Hit:10 https://nginx.org/packages/mainline/ubuntu bionic InRelease
Get:13 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [909 kB]
Hit:11 https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease
Hit:12 https://mirror.wtnet.de/mariadb/repo/10.3/ubuntu bionic InRelease
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [313 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [42.8 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/restricted Translation-en [10.8 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1062 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [330 kB]
Fetched 2830 kB in 3s (922 kB/s)
Reading package lists...
* Installing apt-get packages...
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
* Installing apt-get packages returned a failure code, cleaning up apt caches then exiting
[38;5;9m ! Main packages check and install failed, halting provision[0m
Now I run
vagrant reload --provision
and I am going the share log file with you.
vagrant reload --provision
__ __ __ __
\ V\ V\ V / Varying Vagrant Vagrants
\_/\_/\_/ v3.3.0-git::develop
Platform: platform-darwin19.2.0 shell:/bin/zsh vagrant-hostsupdater shared_db_folder_disabled, VVV Path: "/Users/debabratakarfa/VVV"
Vagrant: v2.2.7, VirtualBox: v6.1.4r136177
Docs: https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard: http://vvv.test
==> default: Running action triggers before reload ...
==> default: Running trigger: VVV Pre-Reload...
default: Running: inline script
default: Performing Database Backups
default: Backing up Database test...
default: Database test backed up...
default: Backing up Database wordpress-one...
default: Database wordpress-one backed up...
default: Backing up Database wordpresstrunk...
default: Database wordpresstrunk backed up...
==> default: [vagrant-hostsupdater] Removing hosts
Password:
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'ubuntu/bionic64' version '20200218.0.0' is up to date...
==> 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: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 5.2.8_KernelUbuntu r120774
default: VirtualBox Version: 6.1
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] found entry for: 192.168.50.4 vvv
==> default: [vagrant-hostsupdater] found entry for: 192.168.50.4 vvv.test
==> default: [vagrant-hostsupdater] found entry for: 192.168.50.4 one.wordpress.test
==> default: [vagrant-hostsupdater] found entry for: 192.168.50.4 tideways.vvv.test
==> default: [vagrant-hostsupdater] found entry for: 192.168.50.4 xhgui.vvv.test
==> default: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> default: [vagrant-hostsupdater] 192.168.50.4 local.test.com # VAGRANT: e754386fd8fc673b5dd30566dab405e9 (default) / 0f024fe0-34f2-4f60-9635-9163f0e784bd
==> default: [vagrant-hostsupdater] 192.168.50.4 trunk.wordpress.test # VAGRANT: e754386fd8fc673b5dd30566dab405e9 (default) / 0f024fe0-34f2-4f60-9635-9163f0e784bd
==> 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 => /Users/debabratakarfa/VVV/www
default: /srv/config => /Users/debabratakarfa/VVV/config
default: /var/log/php => /Users/debabratakarfa/VVV/log/php
default: /srv/database => /Users/debabratakarfa/VVV/database/sql
default: /var/log/nginx => /Users/debabratakarfa/VVV/log/nginx
default: /srv/provision => /Users/debabratakarfa/VVV/provision
default: /srv/certificates => /Users/debabratakarfa/VVV/certificates
default: /var/log/memcached => /Users/debabratakarfa/VVV/log/memcached
default: /var/log/provisioners => /Users/debabratakarfa/VVV/log/provisioners
==> default: Running provisioner: file...
default: /Users/debabratakarfa/VVV/version => /home/vagrant/version
==> default: Running provisioner: default (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-7d4pma.sh
default: * Beginning Main VVV Provisioner, if this is the first provision this may take a few minutes
default: * Bash profile setup and directories.
default: * Setting ownership of files in /home/vagrant to vagrant
default: * Copying /srv/config/bash_profile to /home/vagrant/.bash_profile
default: * Copying /srv/config/bash_aliases to /home/vagrant/.bash_aliases
default: * Copying /srv/config/bash_aliases to /root/.bash_aliases
default: * Copying /srv/config/vimrc to /home/vagrant/.vimrc
default: * Copying /srv/config/subversion-servers to /home/vagrant/.subversion/servers
default: * Copying /srv/config/subversion-config to /home/vagrant/.subversion/config
default: * Copying /srv/config/ssh_known_hosts to /etc/ssh/ssh_known_hosts
default: * Copying /srv/config/sshd_config to /etc/ssh/sshd_config
default: * Reloading SSH Daemon
default: * Testing network connection to https://ppa.launchpad.net
default: * Succesful Network connection to https://ppa.launchpad.net detected...
default: * Testing network connection to https://mirror.herrbischoff.com
default: * Succesful Network connection to https://mirror.herrbischoff.com detected...
default: * Testing network connection to https://wordpress.org
default: * Succesful Network connection to https://wordpress.org detected...
default: * Testing network connection to https://github.com
default: * Succesful Network connection to https://github.com detected...
default: * Testing network connection to https://raw.githubusercontent.com
default: * Succesful Network connection to https://raw.githubusercontent.com detected...
default: * Testing network connection to https://getcomposer.org
default: * Succesful Network connection to https://getcomposer.org detected...
default: * Network checks succeeded
default:
default: * Main packages check and install.
default: * git-core/ppa already present, skipping
default:
default: * Setting up MySQL configuration file links...
default: * mysql group exists
default: * mysql user present and has uid 9001
default: uid=9001(mysql) gid=9001(mysql) groups=9001(mysql),115(vboxsf)
default: * Copying /srv/config/mysql-config/vvv-core.cnf to /etc/mysql/conf.d/vvv-core.cnf
default: * Copying custom apt sources
default: * Checking Apt Keys
default: * Running apt-get update...
default: Ign:1 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 InRelease
default: Hit:2 https://deb.nodesource.com/node_10.x bionic InRelease
default: Hit:3 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 Release
default: Hit:4 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
default: Hit:5 http://archive.ubuntu.com/ubuntu bionic InRelease
default: Hit:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
default: Hit:8 http://security.ubuntu.com/ubuntu bionic-security InRelease
default: Hit:9 http://ppa.launchpad.net/varying-vagrant-vagrants/php/ubuntu bionic InRelease
default: Hit:10 https://nginx.org/packages/mainline/ubuntu bionic InRelease
default: Hit:11 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
default: Hit:13 https://mirror.wtnet.de/mariadb/repo/10.3/ubuntu bionic InRelease
default: Hit:12 https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease
default: Reading package lists...
default: * Installing apt-get packages...
default: Reading package lists...
default: Building dependency tree...
default: Reading state information...
default: make is already the newest version (4.1-9.1ubuntu1).
default: unzip is already the newest version (6.0-21ubuntu1).
default: zip is already the newest version (3.0-11build1).
default: colordiff is already the newest version (1.0.18-1).
default: dos2unix is already the newest version (7.3.4-3).
default: graphviz is already the newest version (2.40.1-2).
default: ngrep is already the newest version (1.47+ds1-1).
default: subversion is already the newest version (1.9.7-4ubuntu1).
default: curl is already the newest version (7.58.0-2ubuntu3.8).
default: g++ is already the newest version (4:7.4.0-1ubuntu2.3).
default: gettext is already the newest version (0.19.8.1-6ubuntu0.3).
default: git is already the newest version (1:2.17.1-1ubuntu0.5).
default: imagemagick is already the newest version (8:6.9.7.4+dfsg-16ubuntu6.8).
default: memcached is already the newest version (1.5.6-0ubuntu1.2).
default: postfix is already the newest version (3.3.0-1ubuntu0.2).
default: software-properties-common is already the newest version (0.96.24.32.12).
default: vim is already the newest version (2:8.0.1453-1ubuntu1.3).
default: git-svn is already the newest version (1:2.17.1-1ubuntu0.5).
default: ntp is already the newest version (1:4.2.8p10+dfsg-5ubuntu7.1).
default: ntpdate is already the newest version (1:4.2.8p10+dfsg-5ubuntu7.1).
default: python-pip is already the newest version (9.0.1-2.3~ubuntu1.18.04.1).
default: nginx is already the newest version (1.17.9-1~bionic).
default: php-imagick is already the newest version (3.4.4-4+ubuntu18.04.1+deb.sury.org+1).
default: php-memcache is already the newest version (4.0.5.2+3.0.9~20170802.e702b5f9-1+ubuntu18.04.1+deb.sury.org+1).
default: php-memcached is already the newest version (3.1.4+2.2.0-1+ubuntu18.04.1+deb.sury.org+20191129).
default: php-pear is already the newest version (1:1.10.8+submodules+notgz-1+ubuntu18.04.1+deb.sury.org+1).
default: php-ssh2 is already the newest version (1.2+0.13-1+ubuntu18.04.1+deb.sury.org+1).
default: php-xdebug is already the newest version (2.9.3+2.8.1+2.5.5-1+ubuntu18.04.1+deb.sury.org+1).
default: php-yaml is already the newest version (2.0.4+1.3.2-1+ubuntu18.04.1+deb.sury.org+20191129).
default: php7.2-bcmath is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-cli is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-common is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-curl is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-dev is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-fpm is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-gd is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-imap is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-json is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-mbstring is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-mysql is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-soap is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-xml is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-zip is already the newest version (7.2.29-1+ubuntu18.04.1+deb.sury.org+1).
default: mariadb-server is already the newest version (1:10.3.22+maria~bionic).
default: nodejs is already the newest version (10.19.0-1nodesource1).
default: git-lfs is already the newest version (2.10.0).
default: 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
default: * Removing unnecessary packages...
default: Reading package lists...
default: Building dependency tree...
default:
default: Reading state information...
default: 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
default: * Cleaning apt caches...
default: * Running tools_install
default: * Disabling active debug PHP mods
default: * Disabling if present: 'xdebug, xhgui, tideways_xhprof, pcov'
default: * Disabling active module: 'tideways_xhprof'
default: * Restarting PHP FPM's so the change takes effect
default: * Checking for NVM
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.14.4
default: updated 1 package in 4.761s
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@4.1.1
default: updated 6 packages in 11.387s
default: * Making sure the composer cache is not owned by root
default: * Checking for Composer
default: * Updating Composer...
default: Changed current directory to /usr/local/src/composer
default: You are already using composer version 1.10.1 (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: Loading composer repositories with package information
default: Updating dependencies (including require-dev)
default: Nothing to install or update
default: Package phpunit/phpunit-mock-objects is abandoned, you should avoid using it. No replacement was suggested.
default: Generating autoload files
default: 1 package you are using is looking for funding.
default: Use the `composer fund` command to find out more!
default: * Updating Grunt CLI
default: * Updated Grunt CLI
default: * Adding graphviz symlink for Webgrind...
default: * Installing Shyaml for bash provisioning..
default: Requirement already satisfied: shyaml in /usr/local/lib/python2.7/dist-packages
default: Requirement already satisfied: pyyaml in /usr/local/lib/python2.7/dist-packages (from shyaml)
default:
default: * Setting up database 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: * Checking the root user password is root
default: /tmp/vagrant-shell: line 742: * The root password is the expected value: command not found
default: * Restarting mysql service
default:
default: * No custom MySQL scripting found in database/init-custom.sql, skipping...
default: * Initial MySQL prep...
default: * Starting MariaDB Database Import
default: * Creating the `test` database if it doesn't already exist, and granting the wp user access
default: * Skipped import of `test` - tables exist
default: * Creating the `wordpress-one` database if it doesn't already exist, and granting the wp user access
default: * Skipped import of `wordpress-one` - tables exist
default: * Creating the `wordpresstrunk` database if it doesn't already exist, and granting the wp user access
default: mysql -u root -proot "wordpresstrunk" < "wordpresstrunk.sql"
default: * Import of `wordpresstrunk` successful
default: * Databases imported
default: * Setup configuration files...
default: * Copying /srv/config/init/vvv-start.conf to /etc/init/vvv-start.conf
default: cp: cannot create regular file '/etc/init/vvv-start.conf': No such file or directory
default: * Copying /srv/config/nginx-config/nginx.conf to /etc/nginx/nginx.conf
default: * Copying /srv/config/nginx-config/nginx-wp-common.conf to /etc/nginx/nginx-wp-common.conf
default: * Copying /srv/config/nginx-config/php7.2-upstream.conf to /etc/nginx/upstreams/php72.conf
default: * Rsync'ing /srv/config/nginx-config/sites/ to /etc/nginx/custom-sites
default: sending incremental file list
default: deleting vvv-auto-wordpress-trunk-provision-857780011be848d6d4c5f93875ce6c77.conf
default: deleting vvv-auto-wordpress-one-provision-60730e707ede8a21f013860b6fc556e1.conf
default: deleting vvv-auto-test-provision-0d7c20757e5fdc8112d12297d9871b68.conf
default: default.conf
default: local-nginx-example.conf-sample
default:
default: sent 1.90K bytes received 279 bytes 4.36K bytes/sec
default: total size is 4.08K speedup is 1.87
default: * Making sure the Nginx log files and folder exist
default: * Enabling MailHog Service
default: * Starting MailHog Service
default: * Copying /srv/config/php-config/php7.2-fpm.conf to /etc/php/7.2/fpm/php-fpm.conf
default: * Copying /srv/config/php-config/php7.2-www.conf to /etc/php/7.2/fpm/pool.d/www.conf
default: * Copying /srv/config/php-config/php7.2-custom.ini to /etc/php/7.2/fpm/conf.d/php-custom.ini
default: * Copying /srv/config/php-config/opcache.ini to /etc/php/7.2/fpm/conf.d/opcache.ini
default: * Copying /srv/config/php-config/xdebug.ini to /etc/php/7.2/mods-available/xdebug.ini
default: * Copying /srv/config/php-config/mailhog.ini to /etc/php/7.2/mods-available/mailhog.ini
default: * Copying /srv/config/memcached-config/memcached.conf to /etc/memcached.conf and /etc/memcached_default.conf
default:
default: * Restarting services...
default: * Disabling XDebug PHP extension
default: * Enabling MailHog for PHP
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: 1cd88616ce15c4c348603b327fc9043a
default: New version works. Proceeding to replace.
default: Success: Updated WP-CLI to the latest nightly release.
default:
default: * Install/Update PHP_CodeSniffer (phpcs), see https://github.com/squizlabs/PHP_CodeSniffer
default:
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:
default: Updating dependencies (including require-dev)
default: Package operations: 0 installs, 1 update, 0 removals
default: - Updating composer/installers (v1.8.0 => v1.9.0):
default: Downloading
default: (100%)
default: Writing lock file
default: 1 package you are using is looking for funding.
default: Use the `composer fund` command to find out more!
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/,./CodeSniffer/Standards/PHPCompatibilityParagonie/,./CodeSniffer/Standards/PHPCompatibilityWP/"
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 PEAR, Zend, PSR2, MySource, Squiz, PSR1, PSR12, WordPress, WordPress-Extra, WordPress-Docs, WordPress-Core, WordPressVIPMinimum, WordPress-VIP-Go, PHPCompatibility, PHPCompatibilityParagonieRandomCompat, PHPCompatibilityParagonieSodiumCompat and PHPCompatibilityWP
default: * Testing network connection to https://ppa.launchpad.net
default: * Succesful Network connection to https://ppa.launchpad.net detected...
default: * Testing network connection to https://mirror.herrbischoff.com
default: * Succesful Network connection to https://mirror.herrbischoff.com detected...
default: * Testing network connection to https://wordpress.org
default: * Succesful Network connection to https://wordpress.org detected...
default: * Testing network connection to https://github.com
default: * Succesful Network connection to https://github.com detected...
default: * Testing network connection to https://raw.githubusercontent.com
default: * Succesful Network connection to https://raw.githubusercontent.com detected...
default: * Testing network connection to https://getcomposer.org
default: * Succesful Network connection to https://getcomposer.org detected...
default: * Network checks succeeded
default:
default: * Searching for SVN repositories that need upgrading
default:
default: * Cleaning up Nginx configs
default: * Cleaning the virtual machine's /etc/hosts file...
default: -----------------------------
default: * Provisioning complete in 76 seconds
default: * For further setup instructions, visit http://vvv.test
==> default: Running provisioner: dashboard (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-1nvgrhg.sh
default: * Updating dashboard on the 'master' branch...
==> default: Running provisioner: utility-source-core (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-11lwk7t.sh
default: * Updating the "core" utility on the "master" branch...
==> default: Running provisioner: utility-core-tls-ca (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-xbefgc.sh
default: * Running utility provisioner for 'core/tls-ca'
default: * The 'core/tls-ca' provisioner completed in 1 seconds
==> default: Running provisioner: utility-core-phpmyadmin (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-1j13mys.sh
default: * Running utility provisioner for 'core/phpmyadmin'
default: * The 'core/phpmyadmin' provisioner completed in 1 seconds
==> default: Running provisioner: utility-core-memcached-admin (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-7mfsq3.sh
default: * Running utility provisioner for 'core/memcached-admin'
default: * The 'core/memcached-admin' provisioner completed in 0 seconds
==> default: Running provisioner: utility-core-opcache-status (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-14tfuba.sh
default: * Running utility provisioner for 'core/opcache-status'
default: From https://github.com/rlerdorf/opcache-status
default: * branch master -> FETCH_HEAD
default: * The 'core/opcache-status' provisioner completed in 1 seconds
==> default: Running provisioner: utility-core-webgrind (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-9hbho4.sh
default: * Running utility provisioner for 'core/webgrind'
default: Loading composer repositories with package information
default: Updating dependencies (including require-dev)
default: Package operations: 0 installs, 1 update, 0 removals
default: - Updating composer/installers (v1.8.0 => v1.9.0):
default: Loading from cache
default: Writing lock file
default: 1 package you are using is looking for funding.
default: Use the `composer fund` command to find out more!
default: * The 'core/webgrind' provisioner completed in 2 seconds
==> default: Running provisioner: utility-core-mongodb (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-1a8ppl1.sh
default: * Running utility provisioner for 'core/mongodb'
default: * The 'core/mongodb' provisioner completed in 0 seconds
==> default: Running provisioner: utility-core-tideways (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-1b01g36.sh
default: * Running utility provisioner for 'core/tideways'
default: * The 'core/tideways' provisioner completed in 4 seconds
==> default: Running provisioner: utility-core-php73 (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-1dse2po.sh
default: * Running utility provisioner for 'core/php73'
default: * The 'core/php73' provisioner completed in 4 seconds
==> default: Running provisioner: utility-core-php74 (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-ginafx.sh
default: * Running utility provisioner for 'core/php74'
default: * The 'core/php74' provisioner completed in 4 seconds
==> default: Running provisioner: site-wordpress-one (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-1jb7qgh.sh
default: * Running provisioner for site wordpress-one
default: * Updating wordpress-one in /srv/www/wordpress-one...
default: * Searching for a site template provisioner, vvv-init.sh
default: * Found vvv-init.sh at /srv/www/wordpress-one/provision/vvv-init.sh
default: * Script output will be logged to: log/provisioners/2020.04.07_11-22-59/provisioner-site-wordpress-one.log
default: * Site provisioner script finished successfully
default: * Adding domains to the virtual machine's /etc/hosts file...
default: * Adding hosts from the VVV config entry
default: - Added one.wordpress.test from /vagrant/config.yml
default: * Reloading Nginx
default: * wordpress-one provisioning finished in 5 seconds
==> default: Running provisioner: site-test (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-irtuug.sh
default: * Running provisioner for site test
default: * Updating test in /srv/www/test...
default: * Searching for a site template provisioner, vvv-init.sh
default: * Found vvv-init.sh at /srv/www/test/provision/vvv-init.sh
default: * Script output will be logged to: log/provisioners/2020.04.07_11-22-59/provisioner-site-test.log
default: * Site provisioner script finished successfully
default: * Adding domains to the virtual machine's /etc/hosts file...
default: * Adding hosts from the VVV config entry
default: - Added local.test.com from /vagrant/config.yml
default: * Reloading Nginx
default: * test provisioning finished in 5 seconds
==> default: Running provisioner: site-wordpress-trunk (shell)...
default: Running: /var/folders/jj/s46jg5r16778cnn0qms4tfxc0000gn/T/vagrant-shell20200407-4085-midwr0.sh
default: * Running provisioner for site wordpress-trunk
default: * Updating wordpress-trunk in /srv/www/wordpress-trunk...
default: * Searching for a site template provisioner, vvv-init.sh
default: * Found vvv-init.sh at /srv/www/wordpress-trunk/provision/vvv-init.sh
default: * Script output will be logged to: log/provisioners/2020.04.07_11-22-59/provisioner-site-wordpress-trunk.log
default: ---------------------------------------------
default:
default: ! Site provisioner failed! Check the full log for more details
default:
default: ---------------------------------------------
default: * Adding domains to the virtual machine's /etc/hosts file...
default: * Adding hosts from the VVV config entry
default: - Added trunk.wordpress.test from /vagrant/config.yml
default: * Reloading Nginx
default: ! wordpress-trunk provisioning had some issues, check the log as the site may not function correctly, provisioning took 2 seconds
==> default: Running action triggers after reload ...
==> default: Running trigger: VVV Post-Reload...
default: Running: inline script
default: Post Vagrant up script
default: Restarting Nginx and MySQL
default:
default: yay
default: ▄▀▀▀▄▄▄▄▄▄▄▀▀▀▄ __ __ __ __
default: █▒▒░░░░░░░░░▒▒█ Thanks for \ V\ V\ V /
default: █░░█░░░░░█░░█ using \_/\_/\_/
default: ▄▄ █░░░▀█▀░░░█ ▄▄
default: █░░█ ▀▄░░░░░░░▄▀ █░░█ Vagrant Up has finished! Visit http://vvv.test
default:
hmmm that error implies that provisioning is happening more than once at the same time, or, the terminal was closed in the middle of provisioning
If a halt
and up
doesn't resolve it, these commands should ( taken from https://itsfoss.com/could-not-get-lock-error/ ):
vagrant halt
vagrant up
vagrant ssh
then inside the VM:
sudo rm /var/lib/apt/lists/lock
sudo rm /var/cache/apt/archives/lock
sudo rm /var/lib/dpkg/lock
sudo dpkg --configure -a
Otherwise, you're the first person to ever encounter this issue in 6 years, congrats!
It's FOSS
Problem with Ubuntu package install? Easily fix E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? error.
Hello! I have the same problem! And I can't open http://mirror.herrbischoff.com with my browser. And
default: #################################################################
default:
default: ! Network Problem:
default:
default: VVV tried to ping several domains it needs but some failed:
default:
default: [✓] https://ppa.launchpad.net
default: [x] https://mirror.herrbischoff.com
default: [✓] https://wordpress.org
default: [✓] https://github.com
default: [✓] https://raw.githubusercontent.com
default: [✓] https://getcomposer.org
default:
default: Make sure you have a working internet connection, that you
default: restarted after installing VirtualBox and Vagrant, and that
default: they aren't blocked by a firewall or security software.
default: If you can load the address in your browser, then VVV should
default: be able to connect.
default:
default: Also note that some users have reported issues when combined
default: with VPNs, disable your VPN and reprovision to see if this is
default: the cause.
default:
default: Additionally, if you're at a contributor day event, be kind,
default: provisioning involves downloading things, a full provision may
default: ruin the wifi for everybody else :(
Seems that this mirror sometimes is a problem.
Sorry, I don't understand very well, but what I can do? I need to continue to work and need a server. Can I change something manually?
Seems that has some issues on that domain with internet. Maybe running again will fix because is something that we cannot fix, I don't remember if we added a way to disable this detection.
It just means that it wasn't possible to reach http://mirror.herrbischoff.com
via HTTP from your machine.
If this works in a browser but not in VVV, then there's a problem in VVV. Otherwise it's just a case that either the site is down, or unreachable from your location. Try another network, check VPNs, and anything else that might help diagnose why the connection between your computer, and that server might not be completed.
Maybe running again will fix because is something that we cannot fix, I don't remember if we added a way to disable this detection.
If they can't reach that domain, disabling the check won't help, they'll just get a cryptic error from apt get
that tries to tell them the same thing. Otherwise the only thing we can do is implement the issue that tries to add backups, or use alternative mirrors. I don't have any information or knowledge about which mirrors are more reliable, or have better connectivity though.
I do know though, that the connection between the users ISP, and the data centre that herrbischoff.com is on in Germany, is either broken, unreliable, interfered with, or misconfigured. I can't diagnose which of those from the UK, and I can't test which mirrors will work for these particular users from here either.
Sorry, I don't understand very well, but what I can do? I need to continue to work and need a server. Can I change something manually? @Timoffey
Same here the domain mirror.herrbischoff.com seems to be down sometimes. Tried it in browser and trace route, but it is not working at this moment anyway.
Temp fix to get your machine running for work is to comment out the domain mirror.herrbischoff.com in provision-helper.sh on line 64. Mind it is just a temp fix to get things running. Hope there is going to be a reliable way to fix this, maybe add a different domain?
Sorry, I don't understand very well, but what I can do? I need to continue to work and need a server. Can I change something manually? @Timoffey
Same here the domain mirror.herrbischoff.com seems to be down sometimes. Tried it in browser and trace route, but it is not working at this moment anyway.
Temp fix to get your machine running for work is to comment out the domain mirror.herrbischoff.com in provision-helper.sh on line 64. Mind it is just a temp fix to get things running. Hope there is going to be a reliable way to fix this, maybe add a different domain?
Developers fix this at develop
brunch
@herbie4 in the develop
branch we switched to a Digital Ocean mirror, but we're still at the mercy of the internet and ISP's at large.
If Digital Ocean goes down, a fibre connection between you and that server is cut, a data centra looses power, or your ISP makes a mistake on one of their routers then there's not much we can do.
It seems though that the Amsterdam Digital Ocean servers are better connected than Herrbischoff. Issue #1993 is really the solution we need.
As for commenting out the line in the network check, the network check just loads the main mirror index page, which is a lot faster than running apt
and finding out half way it's unreachable :(
I'm going to close this out now we're using different servers, lets focus on #1993
What was The Command Used To Provision
What Kind of VVV Provision Was This
No Fresh Install, it was running
Logs/What Broke
Possible Solution
Steps to Reproduce (for bugs)
Your Environment
Vagrant 2.2.7 MacOs Catalina 10.15.3