Closed carlotrimarchi closed 5 years ago
Hello can you send over a full provisioner log? That error basically says something happened and it couldn't continue, but because you only shared that bit of the log I've no idea what the error was.
Please make sure the provisioner log includes the splash screen as it includes important information
On Sun, 16 Jun 2019 at 12:58, Carlo notifications@github.com wrote:
I'm trying to install VVV on a MacOs Sierra 10.12.6
When running the vagrant up command I get a list a error messages, the first being:
default: Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ... default: Checking for services that may need to be restarted... default: done. default: Checking for services that may need to be restarted... default: done. default: Checking init scripts... default: No apport report written because the error message indicates its a followup error from a previous failure. default: dpkg: error processing package libssl1.1:amd64 (--configure): default: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 default: dpkg: dependency problems prevent configuration of libaprutil1:amd64: default: libaprutil1:amd64 depends on libssl1.1 (>= 1.1.0); however: default: Package libssl1.1:amd64 is not configured yet. default: default: dpkg: error processing package libaprutil1:amd64 (--configure): default: dependency problems - leaving unconfigured
Then at the end:
default: Processing was halted because there were too many errors. default: E default: : default: Sub-process /usr/bin/dpkg returned an error code (1) 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.
After this, accessing http://vvv.test and all the other urls work, but I simply get the nginx welcome page.
It might be worth mentioning that I have another vagrant session successfully running a homestead image. Your Environment
- VVV version: 3.0.0
- VVV Git Branch: master
- Vagrant version: 2.2.4
- VM Provider name: VirtualBox
- VM Provider version: 6.0
- Operating System and version:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1862?email_source=notifications&email_token=AAAOLZ7GNZ54U6QWLEIL6XLP2YTETA5CNFSM4HYRAN6KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZXVTNA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOLZ6V647XAQJGS6S2DV3P2YTETANCNFSM4HYRAN6A .
Also if you switch to the develop
branch and recreate the VM fresh, does the problem go away?
@tomjn, thanks for your reply.
What would be the best way to switch to develop
and recreate the VM? Can l just try installing it again in another directory, so to have both the master and develop branch?
For now, here's the full log (I used the command vagrant up --debug &> vagrant.log
):
Holy moly that's massive, I wasn't expecting a full debug verbose log :( it'll take me quite a while to sift through the output in that form
What would be the best way to switch to develop and recreate the VM?
git checkout develop
to switch over, vagrant destroy
to destroy it, and vagrant up --provision
to recreate it. Be sure to clear out the database/data
subfolder folder
Installing it in another folder also works
@carlotrimarchi can you reprovision and log the output without the --debug
option? There's so much vagrant internal debug output generated by the --debug
flag that I can't find anything from the main provisioner to look at
Ah, sorry about that, I thought it was needed :\
I hope this is ok
that looks very unusual, does this happen on the develop
branch too?
yes, it seems a bit different though:
[1;38;5;196m[38;5;9m__ [1;38;5;2m__ [38;5;4m__ __
[38;5;9m\ V[1;38;5;2m\ V[38;5;4m\ V / [38;5;9mVarying [1;38;5;2mVagrant [38;5;4mVagrants
[38;5;9m \_/[1;38;5;2m\_/[38;5;4m\_/ [38;5;5mv3.1.0[0m-[38;5;6mgit::develop
[38;5;3mPlatform: [38;5;3mplatform-darwin13.4.0 shell:/bin/zsh vagrant-hostsupdater shared_db_folder_disabled
[1;38;5;2mVagrant: [1;38;5;2mv2.2.4, [38;5;4mVirtualBox: [38;5;4mv6.0.8r130520
[38;5;5mVVV Path: "/Users/carlo/vagrant/VVV-dev"
[0mDocs: [4;38;5;3mhttps://varyingvagrantvagrants.org/
[0mContribute: [4;38;5;3mhttps://github.com/varying-vagrant-vagrants/vvv
[0mDashboard: [4;38;5;3mhttp://vvv.test[0m
==> default: Running action triggers before provision ...
==> default: Running trigger...
==> default: ༼ つ ◕_◕ ༽つ Provisioning can take a few minutes, go make a cup of tea and sit back. If you only wanted to turn VVV on, use vagrant up
==> 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 two.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: Running provisioner: file...
default: /Users/carlo/vagrant/VVV-dev/version => /home/vagrant/version
==> default: Running provisioner: file...
default: /Users/carlo/vagrant/VVV-dev/vvv-custom.yml => /home/vagrant/vvv-custom.yml
==> default: Running provisioner: initial-setup (shell)...
default: Running: inline script
==> default: Running provisioner: default (shell)...
default: Running: /var/folders/dm/87lh_cn57hq6nry2zrfdtfcw0000gn/T/vagrant-shell20190616-6564-p4en9h.sh
default: Succesful Network connection to ppa.launchpad.net detected...
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/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: Succesful Network connection to ppa.launchpad.net detected...
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: Hit:1 http://mirrors.coreix.net/mariadb/repo/10.3/ubuntu bionic InRelease
default: Hit:2 http://nginx.org/packages/mainline/ubuntu bionic InRelease
default: Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
default: Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
default: Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
default: Hit:6 http://ppa.launchpad.net/varying-vagrant-vagrants/php/ubuntu bionic InRelease
default: Hit:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
default: Hit:8 https://deb.nodesource.com/node_11.x bionic InRelease
default: Hit:9 http://security.ubuntu.com/ubuntu bionic-security InRelease
default: Hit:10 https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease
default: Fetched 88.7 kB in 2s (39.2 kB/s)
default: Reading package lists...
default: Installing apt-get packages...
default: Reading package lists...
default: Building dependency tree...
default:
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.7).
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.4).
default: imagemagick is already the newest version (8:6.9.7.4+dfsg-16ubuntu6.4).
default: memcached is already the newest version (1.5.6-0ubuntu1.1).
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.9).
default: vim is already the newest version (2:8.0.1453-1ubuntu1.1).
default: git-svn is already the newest version (1:2.17.1-1ubuntu0.4).
default: ntp 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.0-1~bionic).
default: php-imagick is already the newest version (3.4.3-4+ubuntu18.04.1+deb.sury.org+1).
default: php-memcache is already the newest version (3.0.9~20170802.e702b5f-1+ubuntu18.04.1+deb.sury.org+10).
default: php-memcached is already the newest version (3.1.3+2.2.0-1+ubuntu18.04.1+deb.sury.org+1).
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.1.2+0.13-4+ubuntu18.04.1+deb.sury.org+1).
default: php-xdebug is already the newest version (2.7.1+2.5.5-1+ubuntu18.04.1+deb.sury.org+1).
default: php-yaml is already the newest version (2.0.2+1.3.1-4+ubuntu18.04.1+deb.sury.org+10).
default: php7.2-bcmath is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-cli is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-common is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-curl is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-dev is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-fpm is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-gd is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-imap is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-json is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-mbstring is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-mysql is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-soap is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-xml is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: php7.2-zip is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1).
default: mariadb-server is already the newest version (1:10.3.15+maria~bionic).
default: nodejs is already the newest version (11.15.0-1nodesource1).
default: git-lfs is already the newest version (2.7.2).
default: 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
default: 2 not fully installed or removed.
default: After this operation, 0 B of additional disk space will be used.
default: Setting up mariadb-server-10.3 (1:10.3.15+maria~bionic) ...
default: 2019-06-16 14:53:53 0 [Note] /usr/sbin/mysqld (mysqld 10.3.15-MariaDB-1:10.3.15+maria~bionic) starting as process 2799 ...
default: 2019-06-16 14:53:53 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Uses event mutexes
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Number of pools: 1
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Completed initialization of buffer pool
default: 2019-06-16 14:53:53 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
default: 2019-06-16 14:53:53 0 [Warning] InnoDB: Failed to set O_DIRECT on file./ibdata1; OPEN: Invalid argument, continuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662.
default: 2019-06-16 14:53:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
default: 2019-06-16 14:53:53 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Waiting for purge to start
default: 2019-06-16 14:53:53 0 [Note] InnoDB: 10.3.15 started; log sequence number 1603986; transaction id 9
default: 2019-06-16 14:53:53 0 [Note] Plugin 'FEEDBACK' is disabled.
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
default: 2019-06-16 14:53:53 0 [Note] Recovering after a crash using tc.log
default:
default: 2019-06-16 14:53:53 0 [ERROR] Can't init tc log
default: 2019-06-16 14:53:53 0 [Note] InnoDB: Buffer pool(s) load completed at 190616 14:53:53
default: 2019-06-16 14:53:53 0 [ERROR] Aborting
default: Configuring mariadb-server-10.3
default: -------------------------------
default:
default: Unable to set password for the MariaDB "root" user
default:
default: An error occurred while setting the password for the MariaDB administrative
default: user. This may have happened because the account already has a password, or
default: because of a communication problem with the MariaDB server.
default:
default: You should check the account's password after the package installation.
default:
default: Please read the /usr/share/doc/mariadb-server-10.3/README.Debian file for
default: more information.
default: Job for mariadb.service failed because the control process exited with error code.
default: See "systemctl status mariadb.service" and "journalctl -xe" for details.
default: invoke-rc.d: initscript mysql, action "start" failed.
default: [0;1;31m●[0m mariadb.service - MariaDB 10.3.15 database server
default: Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
default: Drop-In: /etc/systemd/system/mariadb.service.d
default: └─migrated-from-my.cnf-settings.conf
default: Active: [0;1;31mfailed[0m (Result: exit-code) since Sun 2019-06-16 14:53:59 UTC; 8ms ago
default: Docs: man:mysqld(8)
default: https://mariadb.com/kb/en/library/systemd/
default: Process: 3106 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION [0;1;31m(code=exited, status=1/FAILURE)[0m
default: Process: 2958 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
default: Process: 2951 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
default: Process: 2941 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
default: Main PID: 3106 (code=exited, status=1/FAILURE)
default:
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 0 [Note] Starting crash recovery...[0m
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 0 [Note] Crash recovery finished.[0m
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 0 [Note] InnoDB: Buffer pool(s) load completed at 190616 14:53:59[0m
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")[0m
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist[0m
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 0 [Note] Server socket created on IP: '127.0.0.1'.[0m
default: Jun 16 14:53:59 vvv mysqld[3106]: [0;1;31m[0;1;39m[0;1;31m2019-06-16 14:53:59 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist[0m
default: Jun 16 14:53:59 vvv systemd[1]: [0;1;39m[0;1;31m[0;1;39mmariadb.service: Main process exited, code=exited, status=1/FAILURE[0m
default: Jun 16 14:53:59 vvv systemd[1]: [0;1;39m[0;1;31m[0;1;39mmariadb.service: Failed with result 'exit-code'.[0m
default: Jun 16 14:53:59 vvv systemd[1]: [0;1;31m[0;1;39m[0;1;31mFailed to start MariaDB 10.3.15 database server.[0m
default: No apport report written because the error message indicates its a followup error from a previous failure.
default: dpkg: error processing package mariadb-server-10.3 (--configure):
default: installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 1
default: dpkg: dependency problems prevent configuration of mariadb-server:
default: mariadb-server depends on mariadb-server-10.3 (>= 1:10.3.15+maria~bionic); however:
default: Package mariadb-server-10.3 is not configured yet.
default:
default: dpkg: error processing package mariadb-server (--configure):
default: dependency problems - leaving unconfigured
default: Errors were encountered while processing:
default: mariadb-server-10.3
default: mariadb-server
default: E
default: : Sub-process /usr/bin/dpkg returned an error code (1)
default: Installing apt-get packages returned a failure code, cleaning up apt caches then exiting
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.
How much RAM and free disk space do you have on your computer?
On Sun, 16 Jun 2019 at 15:55, Carlo notifications@github.com wrote:
yes, it seems a bit different though:
�[1;38;5;196m�[38;5;9m �[1;38;5;2m �[38;5;4m
�[38;5;9m\ V�[1;38;5;2m\ V�[38;5;4m\ V / �[38;5;9mVarying �[1;38;5;2mVagrant �[38;5;4mVagrants
�[38;5;9m _/�[1;38;5;2m_/�[38;5;4m_/ �[38;5;5mv3.1.0�[0m-�[38;5;6mgit::develop
�[38;5;3mPlatform: �[38;5;3mplatform-darwin13.4.0 shell:/bin/zsh vagrant-hostsupdater shared_db_folder_disabled
�[1;38;5;2mVagrant: �[1;38;5;2mv2.2.4, �[38;5;4mVirtualBox: �[38;5;4mv6.0.8r130520
�[38;5;5mVVV Path: "/Users/carlo/vagrant/VVV-dev"
�[0mDocs: �[4;38;5;3mhttps://varyingvagrantvagrants.org/
�[0mContribute: �[4;38;5;3mhttps://github.com/varying-vagrant-vagrants/vvv
�[0mDashboard: �[4;38;5;3mhttp://vvv.test�[0m
==> default: Running action triggers before provision ...
==> default: Running trigger...
==> default: ༼ つ ◕_◕ ༽つ Provisioning can take a few minutes, go make a cup of tea and sit back. If you only wanted to turn VVV on, use vagrant up
==> 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 two.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: Running provisioner: file...
default: /Users/carlo/vagrant/VVV-dev/version => /home/vagrant/version
==> default: Running provisioner: file...
default: /Users/carlo/vagrant/VVV-dev/vvv-custom.yml => /home/vagrant/vvv-custom.yml
==> default: Running provisioner: initial-setup (shell)...
default: Running: inline script
==> default: Running provisioner: default (shell)...
default: Running: /var/folders/dm/87lh_cn57hq6nry2zrfdtfcw0000gn/T/vagrant-shell20190616-6564-p4en9h.sh default: Succesful Network connection to ppa.launchpad.net detected... 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/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: Succesful Network connection to ppa.launchpad.net detected... 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: Hit:1 http://mirrors.coreix.net/mariadb/repo/10.3/ubuntu bionic InRelease default: Hit:2 http://nginx.org/packages/mainline/ubuntu bionic InRelease default: Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease default: Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] default: Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease default: Hit:6 http://ppa.launchpad.net/varying-vagrant-vagrants/php/ubuntu bionic InRelease default: Hit:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease default: Hit:8 https://deb.nodesource.com/node_11.x bionic InRelease default: Hit:9 http://security.ubuntu.com/ubuntu bionic-security InRelease default: Hit:10 https://packagecloud.io/github/git-lfs/ubuntu bionic InRelease default: Fetched 88.7 kB in 2s (39.2 kB/s) default: Reading package lists... default: Installing apt-get packages... default: Reading package lists... default: Building dependency tree... default: 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.7). 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.4). default: imagemagick is already the newest version (8:6.9.7.4+dfsg-16ubuntu6.4). default: memcached is already the newest version (1.5.6-0ubuntu1.1). 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.9). default: vim is already the newest version (2:8.0.1453-1ubuntu1.1). default: git-svn is already the newest version (1:2.17.1-1ubuntu0.4). default: ntp 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.0-1~bionic). default: php-imagick is already the newest version (3.4.3-4+ubuntu18.04.1+deb.sury.org+1). default: php-memcache is already the newest version (3.0.9~20170802.e702b5f-1+ubuntu18.04.1+deb.sury.org+10). default: php-memcached is already the newest version (3.1.3+2.2.0-1+ubuntu18.04.1+deb.sury.org+1). 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.1.2+0.13-4+ubuntu18.04.1+deb.sury.org+1). default: php-xdebug is already the newest version (2.7.1+2.5.5-1+ubuntu18.04.1+deb.sury.org+1). default: php-yaml is already the newest version (2.0.2+1.3.1-4+ubuntu18.04.1+deb.sury.org+10). default: php7.2-bcmath is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-cli is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-common is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-curl is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-dev is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-fpm is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-gd is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-imap is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-json is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-mbstring is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-mysql is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-soap is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-xml is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: php7.2-zip is already the newest version (7.2.19-1+ubuntu18.04.1+deb.sury.org+1). default: mariadb-server is already the newest version (1:10.3.15+maria~bionic). default: nodejs is already the newest version (11.15.0-1nodesource1). default: git-lfs is already the newest version (2.7.2). default: 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. default: 2 not fully installed or removed. default: After this operation, 0 B of additional disk space will be used. default: Setting up mariadb-server-10.3 (1:10.3.15+maria~bionic) ... default: 2019-06-16 14:53:53 0 [Note] /usr/sbin/mysqld (mysqld 10.3.15-MariaDB-1:10.3.15+maria~bionic) starting as process 2799 ... default: 2019-06-16 14:53:53 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive default: 2019-06-16 14:53:53 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins default: 2019-06-16 14:53:53 0 [Note] InnoDB: Uses event mutexes default: 2019-06-16 14:53:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 default: 2019-06-16 14:53:53 0 [Note] InnoDB: Number of pools: 1 default: 2019-06-16 14:53:53 0 [Note] InnoDB: Using SSE2 crc32 instructions default: 2019-06-16 14:53:53 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M default: 2019-06-16 14:53:53 0 [Note] InnoDB: Completed initialization of buffer pool default: 2019-06-16 14:53:53 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). default: 2019-06-16 14:53:53 0 [Warning] InnoDB: Failed to set O_DIRECT on file./ibdata1; OPEN: Invalid argument, continuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662. default: 2019-06-16 14:53:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active. default: 2019-06-16 14:53:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables default: 2019-06-16 14:53:53 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... default: 2019-06-16 14:53:53 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. default: 2019-06-16 14:53:53 0 [Note] InnoDB: Waiting for purge to start default: 2019-06-16 14:53:53 0 [Note] InnoDB: 10.3.15 started; log sequence number 1603986; transaction id 9 default: 2019-06-16 14:53:53 0 [Note] Plugin 'FEEDBACK' is disabled. default: 2019-06-16 14:53:53 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool default: 2019-06-16 14:53:53 0 [Note] Recovering after a crash using tc.log default: default: 2019-06-16 14:53:53 0 [ERROR] Can't init tc log default: 2019-06-16 14:53:53 0 [Note] InnoDB: Buffer pool(s) load completed at 190616 14:53:53 default: 2019-06-16 14:53:53 0 [ERROR] Aborting default: Configuring mariadb-server-10.3 default: ------------------------------- default: default: Unable to set password for the MariaDB "root" user default: default: An error occurred while setting the password for the MariaDB administrative default: user. This may have happened because the account already has a password, or default: because of a communication problem with the MariaDB server. default: default: You should check the account's password after the package installation. default: default: Please read the /usr/share/doc/mariadb-server-10.3/README.Debian file for default: more information. default: Job for mariadb.service failed because the control process exited with error code. default: See "systemctl status mariadb.service" and "journalctl -xe" for details. default: invoke-rc.d: initscript mysql, action "start" failed. default: �[0;1;31m●�[0m mariadb.service - MariaDB 10.3.15 database server default: Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) default: Drop-In: /etc/systemd/system/mariadb.service.d default: └─migrated-from-my.cnf-settings.conf default: Active: �[0;1;31mfailed�[0m (Result: exit-code) since Sun 2019-06-16 14:53:59 UTC; 8ms ago default: Docs: man:mysqld(8) default: https://mariadb.com/kb/en/library/systemd/ default: Process: 3106 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION �[0;1;31m(code=exited, status=1/FAILURE)�[0m default: Process: 2958 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) default: Process: 2951 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) default: Process: 2941 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) default: Main PID: 3106 (code=exited, status=1/FAILURE) default: default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 0 [Note] Starting crash recovery...�[0m default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 0 [Note] Crash recovery finished.�[0m default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 0 [Note] InnoDB: Buffer pool(s) load completed at 190616 14:53:59�[0m default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")�[0m default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist�[0m default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 0 [Note] Server socket created on IP: '127.0.0.1'.�[0m default: Jun 16 14:53:59 vvv mysqld[3106]: �[0;1;31m�[0;1;39m�[0;1;31m2019-06-16 14:53:59 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist�[0m default: Jun 16 14:53:59 vvv systemd[1]: �[0;1;39m�[0;1;31m�[0;1;39mmariadb.service: Main process exited, code=exited, status=1/FAILURE�[0m default: Jun 16 14:53:59 vvv systemd[1]: �[0;1;39m�[0;1;31m�[0;1;39mmariadb.service: Failed with result 'exit-code'.�[0m default: Jun 16 14:53:59 vvv systemd[1]: �[0;1;31m�[0;1;39m�[0;1;31mFailed to start MariaDB 10.3.15 database server.�[0m default: No apport report written because the error message indicates its a followup error from a previous failure. default: dpkg: error processing package mariadb-server-10.3 (--configure): default: installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 1 default: dpkg: dependency problems prevent configuration of mariadb-server: default: mariadb-server depends on mariadb-server-10.3 (>= 1:10.3.15+maria~bionic); however: default: Package mariadb-server-10.3 is not configured yet. default: default: dpkg: error processing package mariadb-server (--configure): default: dependency problems - leaving unconfigured default: Errors were encountered while processing: default: mariadb-server-10.3 default: mariadb-server default: E default: : Sub-process /usr/bin/dpkg returned an error code (1) default: Installing apt-get packages returned a failure code, cleaning up apt caches then exiting 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.
— 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/1862?email_source=notifications&email_token=AAAOLZ7WOEPOD523W23RDQDP2ZH7HA5CNFSM4HYRAN6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZOY2Y#issuecomment-502459499, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOLZ5XAD2UGD3HM3CMQELP2ZH7HANCNFSM4HYRAN6A .
16Gb of RAM and 22Gb of free disk space
I have got the same error on an installed 2.2.4 version. Everything was working fine yesterday - and today it cannot start...
...
Processing triggers for mime-support (3.60ubuntu1) ...
Setting up python-certifi (2018.1.18-2) ...
Setting up python-pkg-resources (39.0.1-2) ...
Setting up python-cffi-backend (1.11.5-1) ...
Setting up python-six (1.11.0-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ...
Checking for services that may need to be restarted...done.
Checking for services that may need to be restarted...done.
Checking init scripts...
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
Setting up python-enum34 (1.1.6-2) ...
dpkg: dependency problems prevent configuration of python-cryptography:
python-cryptography depends on libssl1.1 (>= 1.1.1); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package python-cryptography (--configure):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up libpython2.7-minimal:amd64 (2.7.15-4ubuntu4~18.04) ...
Setting up libpci3:amd64 (1:3.5.2-1ubuntu1.1) ...
Setting up python-apt (1.6.4) ...
Setting up python-ipaddress (1.0.17-1) ...
dpkg: dependency problems prevent configuration of libpython2.7-stdlib:amd64:
libpython2.7-stdlib:amd64 depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package libpython2.7-stdlib:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up python2.7-minimal (2.7.15-4ubuntu4~18.04) ...
Setting up python-urllib3 (1.22-1ubuntu0.18.04.1) ...
Setting up python-chardet (3.0.4-1) ...
dpkg: dependency problems prevent configuration of python-openssl:
python-openssl depends on python-cryptography (>= 2.1.4); however:
Package python-cryptography is not configured yet.
dpkg: error processing package python-openssl (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libssl-dev:amd64:
libssl-dev:amd64 depends on libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.2); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package libssl-dev:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python2.7:
python2.7 depends on libpython2.7-stdlib (= 2.7.15-4ubuntu4~18.04); however:
Package libpython2.7-stdlib:amd64 is not configured yet.
dpkg: error processing package python2.7 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpython2.7:amd64:
libpython2.7:amd64 depends on libpython2.7-stdlib (= 2.7.15-4ubuntu4~18.04); however:
Package libpython2.7-stdlib:amd64 is not configured yet.
dpkg: error processing package libpython2.7:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up pciutils (1:3.5.2-1ubuntu1.1) ...
Setting up python-requests (2.18.4-2ubuntu0.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
libssl1.1:amd64
python-cryptography
libpython2.7-stdlib:amd64
python-openssl
libssl-dev:amd64
python2.7
libpython2.7:amd64
* ERROR: Failed to run install_ubuntu_stable_deps()!!!
Stderr from the command:
Since yesterday I've got same error; the only solution seems to downgrade from ubuntu 16 and going on.
default: Package configuration┌──────────────────────┤ Configuring libssl1.1:amd64 ├──────────────────────┐│││ There are services installed on your system which need to be restarted ││ when certain libraries, such as libpam, libc, and libssl, are upgraded. ││ Since these restarts may cause interruptions of service for the system, ││ you will normally be prompted on each upgrade for the list of services ││ you wish to restart. You can choose this option to avoid being││ prompted; instead, all necessary restarts will be done for you││ automatically so you can avoid being asked questions on each library││ upgrade.││││ Restart services during package upgrades without asking?││││<Yes><No>│││└───────────────────────────────────────────────────────────────────────────┘ default: done. No default: Checking for services that may need to be restarted... ^[[B^[[A^[[BNdone.
@RedsAnDev do you mean you switched down to VVV 2? v3 is running Ubuntu 18 LTS
Can somebody with this issue SSH in with vagrant ssh
and run:
sudo dpkg --configure -a
Then tell me the results?
It's a very long list of errors like this:
Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ...
Checking for services that may need to be restarted...done.
Checking for services that may need to be restarted...done.
Checking init scripts...
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of libaprutil1:amd64:
libaprutil1:amd64 depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1:amd64 is not configured yet.
Do you need the full log?
thanks for the fast reply, 🤔 I think instead it might be useful to trigger it for a specific package rather than all of them, try this:
sudo dpkg --configure -D 777 libssl1.1:amd64
or
sudo dpkg --configure -D 777 libssl1.1
For reference i'm going off of this stack exchange answer https://askubuntu.com/a/449022/269594
Ask UbuntuWhen i want to install any package i getting this: root@kd32206:~# apt-get install nginx Reading package lists... Done Building dependency tree Reading state information... Done nginx is already the
Thank you for your support :) (also, as a side not, for me personally is not an urgent matter. I wanted to have VVV for the contributor day at the Wordcamp, but in the training team is not really needed. So, I would like to try it eventually, but I can patiently wait)
Anyway, here's the output:
vagrant@vvv:~$ sudo dpkg --configure -D 777 libssl1.1:amd64
D000001: ensure_diversions: new, (re)loading
D000001: process queue pkg libssl1.1:amd64 queue.len 0 progress 1, try 1
D000040: checking dependencies of libssl1.1:amd64 (- <none>)
D000400: checking group ...
D000400: checking possibility -> libc6
D000400: checking non-provided pkg libc6:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> debconf
D000400: checking non-provided pkg debconf:all
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000040: ok 2 msgs >><<
D000040: checking Breaks
Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ...
D000002: fork/exec /var/lib/dpkg/info/libssl1.1:amd64.postinst ( configure 1.1.0g-2ubuntu4.3 )
Checking for services that may need to be restarted...done.
Checking for services that may need to be restarted...done.
Checking init scripts...
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
D000001: ensure_diversions: same, skipping
D000040: checking dependencies of libc-bin:amd64 (- <none>)
D000400: checking group ...
D000400: checking possibility -> libc6
D000400: checking non-provided pkg libc6:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> libc6
D000400: checking non-provided pkg libc6:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000040: ok 2 msgs >><<
Processing triggers for libc-bin (2.27-3ubuntu1) ...
D000002: fork/exec /var/lib/dpkg/info/libc-bin.postinst ( triggered ldconfig )
D000001: ensure_diversions: same, skipping
Errors were encountered while processing:
libssl1.1:amd64
For Europe? I'll be there with pre-provisioned USB drives :) Im running the machine set up workshop
On Tue, 18 Jun 2019 at 18:10, Carlo notifications@github.com wrote:
Thank you for your support :) (also, as a side not, for me personally is not an urgent matter. I wanted to have VVV for the contributor day at the Wordcamp, but in the training team is not really needed. So, I would like to try it eventually, but I can patiently wait)
Anyway, here's the output:
vagrant@vvv:~$ sudo dpkg --configure -D 777 libssl1.1:amd64
D000001: ensure_diversions: new, (re)loading D000001: process queue pkg libssl1.1:amd64 queue.len 0 progress 1, try 1 D000040: checking dependencies of libssl1.1:amd64 (-
) D000400: checking group ... D000400: checking possibility -> libc6 D000400: checking non-provided pkg libc6:amd64 D000400: is installed, ok and found D000400: found 3 D000400: found 3 matched 0 possfixbytrig - D000400: checking group ... D000400: checking possibility -> debconf D000400: checking non-provided pkg debconf:all D000400: is installed, ok and found D000400: found 3 D000400: found 3 matched 0 possfixbytrig - D000040: ok 2 msgs >><< D000040: checking Breaks Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ... D000002: fork/exec /var/lib/dpkg/info/libssl1.1:amd64.postinst ( configure 1.1.0g-2ubuntu4.3 ) Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D000001: ensure_diversions: same, skipping D000040: checking dependencies of libc-bin:amd64 (- ) D000400: checking group ... D000400: checking possibility -> libc6 D000400: checking non-provided pkg libc6:amd64 D000400: is installed, ok and found D000400: found 3 D000400: found 3 matched 0 possfixbytrig - D000400: checking group ... D000400: checking possibility -> libc6 D000400: checking non-provided pkg libc6:amd64 D000400: is installed, ok and found D000400: found 3 D000400: found 3 matched 0 possfixbytrig - D000040: ok 2 msgs >><< Processing triggers for libc-bin (2.27-3ubuntu1) ... D000002: fork/exec /var/lib/dpkg/info/libc-bin.postinst ( triggered ldconfig ) D000001: ensure_diversions: same, skipping Errors were encountered while processing: libssl1.1:amd64 — 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/1862?email_source=notifications&email_token=AAAOLZ2WN2CLZG343X4YNP3P3ECGFA5CNFSM4HYRAN6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7EWQI#issuecomment-503204673, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOLZ5GRN7C75IEUT6U43DP3ECGFANCNFSM4HYRAN6A .
Yes, the one in Berlin. Hope to meet you there then :)
Did you get this sorted by any chance? The same has begun happening to me today. I've destroyed and reprovisioned several times and it seems to get stuck on mariadb quite a lot for me. I tried some of the steps above:
vagrant@vvv:~$ sudo dpkg --configure -a
Setting up mariadb-server-10.3 (1:10.3.16+maria~bionic) ...
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
● mariadb.service - MariaDB 10.3.16 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Tue 2019-07-23 11:43:57 UTC; 19ms ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1926 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 1776 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 1765 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1754 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 1926 (code=exited, status=1/FAILURE)
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 0 [Note] Starting crash recovery...
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 0 [Note] Crash recovery finished.
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 0 [Note] InnoDB: Buffer pool(s) load completed at 190723 11:43:57
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 0 [Note] Server socket created on IP: '127.0.0.1'.
Jul 23 11:43:57 vvv mysqld[1926]: 2019-07-23 11:43:57 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
Jul 23 11:43:57 vvv systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 23 11:43:57 vvv systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jul 23 11:43:57 vvv systemd[1]: Failed to start MariaDB 10.3.16 database server.
dpkg: error processing package mariadb-server-10.3 (--configure):
installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server:
mariadb-server depends on mariadb-server-10.3 (>= 1:10.3.16+maria~bionic); however:
Package mariadb-server-10.3 is not configured yet.
dpkg: error processing package mariadb-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mariadb-server-10.3
mariadb-server
vagrant@vvv:~$ sudo dpkg --configure -D 777 mariadb-server-10.3
D000001: ensure_diversions: new, (re)loading
D000001: process queue pkg mariadb-server-10.3:amd64 queue.len 0 progress 1, try 1
D000040: checking dependencies of mariadb-server-10.3:amd64 (- <none>)
D000400: checking group ...
D000400: checking possibility -> galera-3
D000400: checking non-provided pkg galera-3:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> gawk
D000400: checking non-provided pkg gawk:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> iproute
D000400: not installed
D000400: returning 0
D000400: found 0
D000400: checking possibility -> iproute2
D000400: checking non-provided pkg iproute2:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> libdbi-perl
D000400: checking non-provided pkg libdbi-perl:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> lsb-base
D000400: checking non-provided pkg lsb-base:all
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> lsof
D000400: checking non-provided pkg lsof:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> mariadb-client-10.3
D000400: checking non-provided pkg mariadb-client-10.3:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> mariadb-server-core-10.3
D000400: checking non-provided pkg mariadb-server-core-10.3:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> passwd
D000400: checking non-provided pkg passwd:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> perl
D000400: checking non-provided pkg perl:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> psmisc
D000400: checking non-provided pkg psmisc:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> rsync
D000400: checking non-provided pkg rsync:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> socat
D000400: checking non-provided pkg socat:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> debconf
D000400: checking non-provided pkg debconf:all
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> libc6
D000400: checking non-provided pkg libc6:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> libpam0g
D000400: checking non-provided pkg libpam0g:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> libssl1.1
D000400: checking non-provided pkg libssl1.1:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> libstdc++6
D000400: checking non-provided pkg libstdc++6:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> zlib1g
D000400: checking non-provided pkg zlib1g:amd64
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> adduser
D000400: checking non-provided pkg adduser:all
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> debconf
D000400: checking non-provided pkg debconf:all
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000400: checking group ...
D000400: checking possibility -> mariadb-common
D000400: checking non-provided pkg mariadb-common:all
D000400: is installed, ok and found
D000400: found 3
D000400: found 3 matched 0 possfixbytrig -
D000040: ok 2 msgs >><<
D000040: checking Breaks
D000400: checking breaker mariadb-server-core-10.3:amd64 virtbroken <none>
D000400: checking virtbroken default-mysql-server
D000400: checking virtbroken virtual-mysql-server
Setting up mariadb-server-10.3 (1:10.3.16+maria~bionic) ...
D000002: fork/exec /var/lib/dpkg/info/mariadb-server-10.3.postinst ( configure )
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
● mariadb.service - MariaDB 10.3.16 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Tue 2019-07-23 11:44:25 UTC; 10ms ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 2432 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 2284 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 2278 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 2266 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 2432 (code=exited, status=1/FAILURE)
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 0 [Note] Starting crash recovery...
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 0 [Note] Crash recovery finished.
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 0 [Note] InnoDB: Buffer pool(s) load completed at 190723 11:44:25
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 0 [Note] Server socket created on IP: '127.0.0.1'.
Jul 23 11:44:25 vvv mysqld[2432]: 2019-07-23 11:44:25 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
Jul 23 11:44:25 vvv systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 23 11:44:25 vvv systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jul 23 11:44:25 vvv systemd[1]: Failed to start MariaDB 10.3.16 database server.
dpkg: error processing package mariadb-server-10.3 (--configure):
installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 1
D000001: ensure_diversions: same, skipping
Errors were encountered while processing:
mariadb-server-10.3
Note that sudo dpkg --configure -D 777 mariadb-server-10.3
led to a screen asking for a root pwd for MariaDB, and I left it blank.
Using the messages above I found this suggestion about purging everything and re-installing. I tried it and it failed when configuring MariaDB:
2019-07-23 11:56:43 0 [ERROR] Can't init tc log
2019-07-23 11:56:43 0 [ERROR] Aborting
Created symlink /etc/systemd/system/mysql.service → /lib/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/mysqld.service → /lib/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/multi-user.target.wants/mariadb.service → /lib/systemd/system/mariadb.service.
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
● mariadb.service - MariaDB 10.3.16 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Tue 2019-07-23 11:56:53 UTC; 13ms ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 7407 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 7259 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 7252 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 7241 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 7407 (code=exited, status=1/FAILURE)
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 0 [Note] InnoDB: Buffer pool(s) load completed at 190723 11:56:53
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 0 [Note] Server socket created on IP: '127.0.0.1'.
Jul 23 11:56:53 vvv mysqld[7407]: 2019-07-23 11:56:53 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
Jul 23 11:56:53 vvv systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 23 11:56:53 vvv systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jul 23 11:56:53 vvv systemd[1]: Failed to start MariaDB 10.3.16 database server.
dpkg: error processing package mariadb-server-10.3 (--configure):
installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server:
mariadb-server depends on mariadb-server-10.3 (>= 1:10.3.16+maria~bionic); however:
Package mariadb-server-10.3 is not configured yet.
dpkg: error processing package mariadb-server (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.24) ...
Errors were encountered while processing:
mariadb-server-10.3
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
There doesn't seem to be much information about what went wrong, unless I'm just not seeing it.
I'm closing this out for now, if it resurfaces on the develop
branch or v3.1.1+ please comment
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
I'm trying to install VVV on a MacOs Sierra 10.12.6
When running the
vagrant up
command I get a list a error messages, the first being:Then at the end:
After this, accessing http://vvv.test and all the other urls work, but I simply get the nginx welcome page.
It might be worth mentioning that I have another vagrant session successfully running a
homestead
image.Your Environment