Local DB is wiped every time after vagrant halt

[luuptekman]

There seem to be a problem with the latest vagrant box.

Steps to reproduce:

1. Clone the latest from the repo & use the latest vagrant box 20201205.0.0
2. Use vagrant up to boot your local setup
3. Do some changes in the local development site (create for pages, activate some plugins etc..)
4. Do vagrant halt to close the virtual machine
5. Next time begin your work by booting up with vagrant up
6. Go to see your wp-admin contents

Actual results: All the changes you did to site are gone. Content need to be reinserted.

Expected: All the changes made to local db should be there (at least it has work like that before).

[ottok]

Running vagrant halt worked as expected and I was unable to reproduce this.

After a vagrant halt running vagrant up starts it and the database is inside Vagrant still as it was before the halt:

DEVELOPMENT [@wordpress:~] $ ls -latr /data/mariadb/
total 155712
drwx------  2 vagrant vagrant      4096 Nov 27 12:23 performance_schema
drwx------  2 vagrant vagrant      4096 Nov 27 12:23 mysql
-rw-r--r--  1 vagrant vagrant         0 Nov 27 12:23 debian-10.5.flag
-rw-rw----  1 vagrant vagrant       860 Jan 10 21:15 ib_buffer_pool
-rw-rw----  1 vagrant vagrant        52 Jan 10 21:15 aria_log_control
-rw-rw----  1 vagrant vagrant     24576 Jan 10 21:15 aria_log.00000001
-rw-rw----  1 vagrant vagrant         0 Jan 10 21:15 multi-master.info
-rw-rw----  1 vagrant vagrant  12582912 Jan 10 21:21 ibdata1
drwxr-xr-x  5 vagrant vagrant      4096 Jan 10 21:21 .
-rw-rw----  1 vagrant vagrant  12582912 Jan 10 21:21 ibtmp1
-rw-rw----  1 vagrant vagrant      4511 Jan 10 21:21 wordpress.err
drwxr-xr-x 13 vagrant vagrant      4096 Jan 10 21:21 ..
drwx------  2 vagrant vagrant      4096 Jan 10 21:23 vagrant
-rw-rw----  1 vagrant vagrant 134217728 Jan 10 21:23 ib_logfile0
DEVELOPMENT [@wordpress:~] $ ls -latr /data/mariadb/vagrant/
total 1696
-rw-rw---- 1 vagrant vagrant     67 Jan 10 21:15 db.opt
drwxr-xr-x 5 vagrant vagrant   4096 Jan 10 21:21 ..
-rw-rw---- 1 vagrant vagrant   3033 Jan 10 21:23 wp_commentmeta.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_commentmeta.ibd
-rw-rw---- 1 vagrant vagrant   6679 Jan 10 21:23 wp_comments.frm
-rw-rw---- 1 vagrant vagrant 180224 Jan 10 21:23 wp_comments.ibd
-rw-rw---- 1 vagrant vagrant   8102 Jan 10 21:23 wp_links.frm
-rw-rw---- 1 vagrant vagrant 114688 Jan 10 21:23 wp_links.ibd
-rw-rw---- 1 vagrant vagrant   2854 Jan 10 21:23 wp_options.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_options.ibd
-rw-rw---- 1 vagrant vagrant   3030 Jan 10 21:23 wp_postmeta.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_postmeta.ibd
-rw-rw---- 1 vagrant vagrant   7211 Jan 10 21:23 wp_posts.frm
-rw-rw---- 1 vagrant vagrant 163840 Jan 10 21:23 wp_posts.ibd
-rw-rw---- 1 vagrant vagrant   1496 Jan 10 21:23 wp_term_relationships.frm
-rw-rw---- 1 vagrant vagrant 114688 Jan 10 21:23 wp_term_relationships.ibd
-rw-rw---- 1 vagrant vagrant   2209 Jan 10 21:23 wp_term_taxonomy.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_term_taxonomy.ibd
-rw-rw---- 1 vagrant vagrant   3030 Jan 10 21:23 wp_termmeta.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_termmeta.ibd
-rw-rw---- 1 vagrant vagrant   3592 Jan 10 21:23 wp_terms.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_terms.ibd
-rw-rw---- 1 vagrant vagrant   3031 Jan 10 21:23 wp_usermeta.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 10 21:23 wp_usermeta.ibd
-rw-rw---- 1 vagrant vagrant   6962 Jan 10 21:23 wp_users.frm
drwx------ 2 vagrant vagrant   4096 Jan 10 21:23 .
-rw-rw---- 1 vagrant vagrant 147456 Jan 10 21:23 wp_users.ibd

Both when running halt and vagrant destroy, a shutdown dump is created as expected:

wordpress master+* ± vagrant destroy --force
==> wordpress-box: Running action triggers before destroy ...
==> wordpress-box: Running trigger...
==> wordpress-box: Dump WordPress database into: .vagrant/shutdown-dump.sql
==> wordpress-box: Connecting to development environment... (ssh -- /usr/local/bin/wp-vagrant-dump-db)
==> wordpress-box: 
==> wordpress-box: SSH connection confirmed
==> wordpress-box: 
==> wordpress-box: --> Dumping database contents into /data/wordpress/.vagrant/shutdown-dump.sql
==> wordpress-box: 
==> wordpress-box: Forcing shutdown of VM...
==> wordpress-box: Destroying VM and associated drives...
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts
==> wordpress-box: [vagrant-hostsupdater] Removing hosts

However, after a vagrant destroy running vagrant up did not load the dump as expected. These lines did not trigger in the Vagrantfile:

      elsif File.exists?(File.join(DIR,'.vagrant','shutdown-dump.sql'))
        # Return the state where we last left if WordPress isn't currently installed
        # First part in the command prevents overriding existing database
        run_command("wp core is-installed --quiet &>/dev/null || wp-vagrant-import-db", machine)

This is because the site is always installed by the time Vagrantfile triggers. I have an idea how to fix it.

While waiting for it, you can run

± vagrant ssh -c wp-vagrant-import-db
Connecting to development environment... (ssh -- /usr/local/bin/wp-vagrant-import-db)
SSH connection confirmed
Success: Imported from '/data/wordpress/.vagrant/shutdown-dump.sql'.
Success: The cache was flushed.

--> Loading contents from /data/wordpress/.vagrant/shutdown-dump.sql to database
--> Flushing cache to ensure new database contents is used on site
Connection to 127.0.0.1 closed.

Or alternatively configure config.yml and have a "real" site to develop on and not only the default project template.

[luuptekman]

Thanks for the comments.

Or alternatively configure config.yml and have a "real" site to develop on and not only the default project template. ==> Yes that's what I ended up ==> setting the site first in production and get db from there.

I let you know if this is still reproduced when I continue developing.

[luuptekman]

@ottok Seems this is not reproduced anymore after I pulled the db from live with wp-pull-production-db. After that vagrant halt is not wiping the db.

[tume91]

We are experiencing the same kind of error. When halting for the first time, creating the db dump goes as expected. But when booting the box and halting again, the dump got stuck in the middle of process.

==> meom-box: Running action triggers before halt ...
==> meom-box: Running trigger...
==> meom-box: Dump WordPress database into: .vagrant/shutdown-dump.sql
==> meom-box: Connecting to development environment... (ssh -- /usr/local/bin/wp-vagrant-dump-db)
==> meom-box:
==> meom-box: SSH connection confirmed
==> meom-box:
==> meom-box: --> Dumping database contents into /data/wordpress/.vagrant/shutdown-dump.sql
==> meom-box:
==> meom-box: mariadb-dump: Error 2013: Lost connection to MySQL server during query when dumping table `wrdp_posts` at row: 2429

I will also check with plain install -->

[tume91]

Tested this with plain install and it didn't give me any errors. When having a plain install and adding a production site configs to config.yml it starts to give me errors.

➜  seravo-test git:(master) ✗ vagrant halt
==> seravo-test-box: Running action triggers before halt ...
==> seravo-test-box: Running trigger...
==> seravo-test-box: Dump WordPress database into: .vagrant/shutdown-dump.sql
==> seravo-test-box: Connecting to development environment... (ssh -- /usr/local/bin/wp-vagrant-dump-db)
==> seravo-test-box:
==> seravo-test-box: SSH connection confirmed
==> seravo-test-box:
==> seravo-test-box: --> Dumping database contents into /data/wordpress/.vagrant/shutdown-dump.sql
==> seravo-test-box:
==> seravo-test-box: mariadb-dump: Couldn't execute 'show create table `wp_gf_draft_submissions`': Table 'vagrant.wp_gf_draft_submissions' doesn't exist in engine (1932)

Before halting, /data/mariadb/vagrant included these:

$ ls -latr /data/mariadb/vagrant/
total 36160
-rwxrwxr-x 1 vagrant vagrant       67 Jan 20 09:38 db.opt
drwxr-xr-x 5 vagrant vagrant     4096 Jan 20 13:19 ..
-rw-rw---- 1 vagrant vagrant     3033 Jan 20 13:27 wp_commentmeta.frm
-rw-rw---- 1 vagrant vagrant     6679 Jan 20 13:27 wp_comments.frm
-rw-rw---- 1 vagrant vagrant     2902 Jan 20 13:27 wp_gf_draft_submissions.frm
-rw-rw---- 1 vagrant vagrant     4933 Jan 20 13:27 wp_gf_entry.frm
-rw-rw---- 1 vagrant vagrant     3812 Jan 20 13:27 wp_gf_entry_meta.frm
-rw-rw---- 1 vagrant vagrant     3517 Jan 20 13:27 wp_gf_entry_notes.frm
-rw-rw---- 1 vagrant vagrant     1671 Jan 20 13:27 wp_gf_form.frm
-rw-rw---- 1 vagrant vagrant     1101 Jan 20 13:27 wp_gf_form_meta.frm
-rw-rw---- 1 vagrant vagrant     2009 Jan 20 13:27 wp_gf_form_revisions.frm
-rw-rw---- 1 vagrant vagrant     2073 Jan 20 13:27 wp_gf_form_view.frm
-rw-rw---- 1 vagrant vagrant     8102 Jan 20 13:27 wp_links.frm
-rw-rw---- 1 vagrant vagrant     1596 Jan 20 13:27 wp_nextend2_image_storage.frm
-rw-rw---- 1 vagrant vagrant     3886 Jan 20 13:27 wp_nextend2_section_storage.frm
-rw-rw---- 1 vagrant vagrant     2528 Jan 20 13:27 wp_nextend2_smartslider3_generators.frm
-rw-rw---- 1 vagrant vagrant     4189 Jan 20 13:27 wp_nextend2_smartslider3_sliders.frm
-rw-rw---- 1 vagrant vagrant     1478 Jan 20 13:27 wp_nextend2_smartslider3_sliders_xref.frm
-rw-rw---- 1 vagrant vagrant     6087 Jan 20 13:27 wp_nextend2_smartslider3_slides.frm
-rw-rw---- 1 vagrant vagrant     2854 Jan 20 13:27 wp_options.frm
-rw-rw---- 1 vagrant vagrant     3030 Jan 20 13:27 wp_postmeta.frm
-rw-rw---- 1 vagrant vagrant     7211 Jan 20 13:27 wp_posts.frm
-rw-rw---- 1 vagrant vagrant     1496 Jan 20 13:27 wp_term_relationships.frm
-rw-rw---- 1 vagrant vagrant     2209 Jan 20 13:27 wp_term_taxonomy.frm
-rw-rw---- 1 vagrant vagrant     3030 Jan 20 13:27 wp_termmeta.frm
-rw-rw---- 1 vagrant vagrant     3592 Jan 20 13:27 wp_terms.frm
-rw-rw---- 1 vagrant vagrant     3031 Jan 20 13:27 wp_usermeta.frm
-rw-rw---- 1 vagrant vagrant     6962 Jan 20 13:27 wp_users.frm
-rw-rw---- 1 vagrant vagrant     8702 Jan 20 13:27 wp_yoast_indexable.frm
-rw-rw---- 1 vagrant vagrant     2492 Jan 20 13:27 wp_yoast_indexable_hierarchy.frm
-rw-rw---- 1 vagrant vagrant     2202 Jan 20 13:27 wp_yoast_migrations.frm
-rw-rw---- 1 vagrant vagrant     2211 Jan 20 13:27 wp_yoast_primary_term.frm
-rw-rw---- 1 vagrant vagrant     3539 Jan 20 13:27 wp_yoast_seo_links.frm
-rw-rw---- 1 vagrant vagrant     1015 Jan 20 13:27 wp_yoast_seo_meta.frm
drwxrwxr-x 2 vagrant vagrant     4096 Jan 20 13:27 .
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_gf_entry.ibd
-rw-rw---- 1 vagrant vagrant   114688 Jan 20 13:27 wp_gf_draft_submissions.ibd
-rw-rw---- 1 vagrant vagrant   180224 Jan 20 13:27 wp_comments.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_commentmeta.ibd
-rw-rw---- 1 vagrant vagrant    98304 Jan 20 13:27 wp_gf_form.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_gf_entry_notes.ibd
-rw-rw---- 1 vagrant vagrant   147456 Jan 20 13:27 wp_gf_entry_meta.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_gf_form_view.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_gf_form_revisions.ibd
-rw-rw---- 1 vagrant vagrant    98304 Jan 20 13:27 wp_gf_form_meta.ibd
-rw-rw---- 1 vagrant vagrant   212992 Jan 20 13:27 wp_nextend2_smartslider3_slides.ibd
-rw-rw---- 1 vagrant vagrant   114688 Jan 20 13:27 wp_nextend2_smartslider3_sliders_xref.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_nextend2_smartslider3_sliders.ibd
-rw-rw---- 1 vagrant vagrant    98304 Jan 20 13:27 wp_nextend2_smartslider3_generators.ibd
-rw-rw---- 1 vagrant vagrant   163840 Jan 20 13:27 wp_nextend2_section_storage.ibd
-rw-rw---- 1 vagrant vagrant   114688 Jan 20 13:27 wp_nextend2_image_storage.ibd
-rw-rw---- 1 vagrant vagrant   114688 Jan 20 13:27 wp_links.ibd
-rw-rw---- 1 vagrant vagrant   229376 Jan 20 13:27 wp_options.ibd
-rw-rw---- 1 vagrant vagrant 10485760 Jan 20 13:27 wp_postmeta.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_term_taxonomy.ibd
-rw-rw---- 1 vagrant vagrant   114688 Jan 20 13:27 wp_term_relationships.ibd
-rw-rw---- 1 vagrant vagrant 22020096 Jan 20 13:27 wp_posts.ibd
-rw-rw---- 1 vagrant vagrant   147456 Jan 20 13:27 wp_users.ibd
-rw-rw---- 1 vagrant vagrant   180224 Jan 20 13:27 wp_usermeta.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_terms.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_termmeta.ibd
-rw-rw---- 1 vagrant vagrant   163840 Jan 20 13:27 wp_yoast_seo_meta.ibd
-rw-rw---- 1 vagrant vagrant   163840 Jan 20 13:27 wp_yoast_seo_links.ibd
-rw-rw---- 1 vagrant vagrant   131072 Jan 20 13:27 wp_yoast_primary_term.ibd
-rw-rw---- 1 vagrant vagrant   114688 Jan 20 13:27 wp_yoast_migrations.ibd
-rw-rw---- 1 vagrant vagrant   294912 Jan 20 13:27 wp_yoast_indexable.ibd
-rw-rw---- 1 vagrant vagrant   147456 Jan 20 13:27 wp_yoast_indexable_hierarchy.ibd

And after halting, the result was this:

$ ls -latr /data/mariadb/vagrant/
total 4860
-rwxrwxr-x 1 vagrant vagrant     67 Jan 20 09:38 db.opt
-rwxrwxr-x 1 vagrant vagrant   6962 Jan 20 09:38 wp_users.frm
-rwxrwxr-x 1 vagrant vagrant   3031 Jan 20 09:38 wp_usermeta.frm
-rwxrwxr-x 1 vagrant vagrant   2209 Jan 20 09:38 wp_term_taxonomy.frm
-rwxrwxr-x 1 vagrant vagrant   3592 Jan 20 09:38 wp_terms.frm
-rwxrwxr-x 1 vagrant vagrant   1496 Jan 20 09:38 wp_term_relationships.frm
-rwxrwxr-x 1 vagrant vagrant   3030 Jan 20 09:38 wp_termmeta.frm
-rwxrwxr-x 1 vagrant vagrant   7211 Jan 20 09:38 wp_posts.frm
-rwxrwxr-x 1 vagrant vagrant   3030 Jan 20 09:38 wp_postmeta.frm
-rwxrwxr-x 1 vagrant vagrant   2854 Jan 20 09:38 wp_options.frm
-rwxrwxr-x 1 vagrant vagrant   8102 Jan 20 09:38 wp_links.frm
-rwxrwxr-x 1 vagrant vagrant   6679 Jan 20 09:38 wp_comments.frm
-rwxrwxr-x 1 vagrant vagrant   3033 Jan 20 09:38 wp_commentmeta.frm
drwxrwxr-x 2 vagrant vagrant   4096 Jan 20 09:38 .
-rwxrwxr-x 1 vagrant vagrant 147456 Jan 20 10:02 wp_users.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_usermeta.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_term_taxonomy.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_terms.ibd
-rwxrwxr-x 1 vagrant vagrant 114688 Jan 20 10:02 wp_term_relationships.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_termmeta.ibd
-rwxrwxr-x 1 vagrant vagrant 475136 Jan 20 10:02 wp_posts.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_postmeta.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_options.ibd
-rwxrwxr-x 1 vagrant vagrant 114688 Jan 20 10:02 wp_links.ibd
-rwxrwxr-x 1 vagrant vagrant 180224 Jan 20 10:02 wp_comments.ibd
-rwxrwxr-x 1 vagrant vagrant 131072 Jan 20 10:02 wp_commentmeta.ibd
-rw-rw---- 1 vagrant vagrant   2902 Jan 20 12:24 wp_gf_draft_submissions.frm
-rw-rw---- 1 vagrant vagrant   4933 Jan 20 12:24 wp_gf_entry.frm
-rw-rw---- 1 vagrant vagrant   3812 Jan 20 12:24 wp_gf_entry_meta.frm
-rw-rw---- 1 vagrant vagrant   3517 Jan 20 12:24 wp_gf_entry_notes.frm
-rw-rw---- 1 vagrant vagrant   1671 Jan 20 12:24 wp_gf_form.frm
-rw-rw---- 1 vagrant vagrant   1101 Jan 20 12:24 wp_gf_form_meta.frm
-rw-rw---- 1 vagrant vagrant   2009 Jan 20 12:24 wp_gf_form_revisions.frm
-rw-rw---- 1 vagrant vagrant   2073 Jan 20 12:24 wp_gf_form_view.frm
-rw-rw---- 1 vagrant vagrant   1596 Jan 20 12:24 wp_nextend2_image_storage.frm
-rw-rw---- 1 vagrant vagrant   3886 Jan 20 12:24 wp_nextend2_section_storage.frm
-rw-rw---- 1 vagrant vagrant   2528 Jan 20 12:24 wp_nextend2_smartslider3_generators.frm
-rw-rw---- 1 vagrant vagrant   4189 Jan 20 12:24 wp_nextend2_smartslider3_sliders.frm
-rw-rw---- 1 vagrant vagrant   1478 Jan 20 12:24 wp_nextend2_smartslider3_sliders_xref.frm
-rw-rw---- 1 vagrant vagrant   6087 Jan 20 12:24 wp_nextend2_smartslider3_slides.frm
-rw-rw---- 1 vagrant vagrant   8702 Jan 20 12:24 wp_yoast_indexable.frm
-rw-rw---- 1 vagrant vagrant 294912 Jan 20 12:24 wp_yoast_indexable.ibd
-rw-rw---- 1 vagrant vagrant   2492 Jan 20 12:24 wp_yoast_indexable_hierarchy.frm
-rw-rw---- 1 vagrant vagrant 147456 Jan 20 12:24 wp_yoast_indexable_hierarchy.ibd
-rw-rw---- 1 vagrant vagrant   2202 Jan 20 12:24 wp_yoast_migrations.frm
-rw-rw---- 1 vagrant vagrant 114688 Jan 20 12:24 wp_yoast_migrations.ibd
-rw-rw---- 1 vagrant vagrant   2211 Jan 20 12:24 wp_yoast_primary_term.frm
-rw-rw---- 1 vagrant vagrant 131072 Jan 20 12:24 wp_yoast_primary_term.ibd
-rw-rw---- 1 vagrant vagrant   3539 Jan 20 12:24 wp_yoast_seo_links.frm
-rw-rw---- 1 vagrant vagrant 163840 Jan 20 12:24 wp_yoast_seo_links.ibd
-rw-rw---- 1 vagrant vagrant   1015 Jan 20 12:24 wp_yoast_seo_meta.frm
-rw-rw---- 1 vagrant vagrant 163840 Jan 20 12:24 wp_yoast_seo_meta.ibd
-rw-rw---- 1 vagrant vagrant 131072 Jan 20 12:24 wp_gf_entry_notes.ibd
-rw-rw---- 1 vagrant vagrant 147456 Jan 20 12:24 wp_gf_entry_meta.ibd
-rw-rw---- 1 vagrant vagrant 131072 Jan 20 12:24 wp_gf_entry.ibd
-rw-rw---- 1 vagrant vagrant 114688 Jan 20 12:24 wp_gf_draft_submissions.ibd
-rw-rw---- 1 vagrant vagrant  98304 Jan 20 12:24 wp_gf_form.ibd
-rw-rw---- 1 vagrant vagrant 131072 Jan 20 12:24 wp_gf_form_view.ibd
-rw-rw---- 1 vagrant vagrant 131072 Jan 20 12:24 wp_gf_form_revisions.ibd
-rw-rw---- 1 vagrant vagrant  98304 Jan 20 12:24 wp_gf_form_meta.ibd
-rw-rw---- 1 vagrant vagrant 212992 Jan 20 12:24 wp_nextend2_smartslider3_slides.ibd
-rw-rw---- 1 vagrant vagrant 114688 Jan 20 12:24 wp_nextend2_smartslider3_sliders_xref.ibd
-rw-rw---- 1 vagrant vagrant 131072 Jan 20 12:24 wp_nextend2_smartslider3_sliders.ibd
-rw-rw---- 1 vagrant vagrant  98304 Jan 20 12:24 wp_nextend2_smartslider3_generators.ibd
-rw-rw---- 1 vagrant vagrant 163840 Jan 20 12:24 wp_nextend2_section_storage.ibd
-rw-rw---- 1 vagrant vagrant 114688 Jan 20 12:24 wp_nextend2_image_storage.ibd
drwxr-xr-x 5 vagrant vagrant   4096 Jan 20 12:50 ..

Total amount seems to be changing, but same files can be found.

And /data/mariadb before:

ls -latr
total 221256
drwxrwxr-x  2 vagrant vagrant      4096 Nov 27 12:23 performance_schema
drwxrwxr-x  2 vagrant vagrant      4096 Nov 27 12:23 mysql
-rwxrwxr-x  1 vagrant vagrant         0 Nov 27 12:23 debian-10.5.flag
-rwxrwxr-x  1 vagrant vagrant       860 Jan 20 09:38 ib_buffer_pool
-rwxrwxr-x  1 vagrant vagrant         0 Jan 20 09:38 multi-master.info
-rwxrwxr-x  1 vagrant vagrant      9300 Jan 20 10:03 wordpress.err
-rw-rw----  1 vagrant vagrant        52 Jan 20 13:19 aria_log_control
-rw-rw----  1 vagrant vagrant      8192 Jan 20 13:19 aria_log.00000001
drwxr-xr-x  5 vagrant vagrant      4096 Jan 20 13:19 .
drwxr-xr-x 13 vagrant vagrant      4096 Jan 20 13:20 ..
-rwxrwxr-x  1 vagrant vagrant     16576 Jan 20 13:22 seravo-test.err
drwxrwxr-x  2 vagrant vagrant      4096 Jan 20 13:27 vagrant
-rw-rw----  1 vagrant vagrant  12582912 Jan 20 13:27 ibtmp1
-rwxrwxr-x  1 vagrant vagrant  79691776 Jan 20 13:27 ibdata1
-rw-rw----  1 vagrant vagrant 134217728 Jan 20 13:27 ib_logfile0

After:

$ ls -latr
total 155720
drwxrwxr-x  2 vagrant vagrant      4096 Nov 27 12:23 performance_schema
drwxrwxr-x  2 vagrant vagrant      4096 Nov 27 12:23 mysql
-rwxrwxr-x  1 vagrant vagrant         0 Nov 27 12:23 debian-10.5.flag
-rwxrwxr-x  1 vagrant vagrant       860 Jan 20 09:38 ib_buffer_pool
-rwxrwxr-x  1 vagrant vagrant         0 Jan 20 09:38 multi-master.info
drwxrwxr-x  2 vagrant vagrant      4096 Jan 20 09:38 vagrant
-rwxrwxr-x  1 vagrant vagrant  12582912 Jan 20 10:02 ibdata1
-rwxrwxr-x  1 vagrant vagrant      9300 Jan 20 10:03 wordpress.err
-rw-rw----  1 vagrant vagrant        52 Jan 20 13:40 aria_log_control
-rw-rw----  1 vagrant vagrant      8192 Jan 20 13:40 aria_log.00000001
-rw-rw----  1 vagrant vagrant  12582912 Jan 20 13:40 ibtmp1
drwxr-xr-x  5 vagrant vagrant      4096 Jan 20 13:40 .
-rwxrwxr-x  1 vagrant vagrant     18531 Jan 20 13:40 seravo-test.err
-rw-rw----  1 vagrant vagrant 134217728 Jan 20 13:40 ib_logfile0
drwxr-xr-x 13 vagrant vagrant      4096 Jan 20 13:41 ..

After the error when trying to download production db, it fails to same error message. Also db dump file cuts before given table name in error message, so db dump file is broken.

[ottok]

Tuomas: your database got corrupted. Luckily it is a dev database.. You need to start from scratch to recover from that.

[tume91]

Yep. At the moment it's happening very often, after updating to latest box version. Have to check if that's something to do with certain plugin.

[dubbajones]

Seems like I have the same problem. First vagrant up works fine, though wordpress is somewhat slow and gives a lot gateway timeouts, example when trying to install bigger plugins like woocommerce. When running vagrant halt and then vagrant up it doesnt find tables from the shutdown-dump.sql and the sitename.local gives me wp install view instead of the site in development.

After trying to wp-pull-production-db it gives me following error:

ERROR 1813 (HY000) at line 25: Tablespace for table '`vagrant`.`wp_commentmeta`' exists. Please DISCARD the tablespace before IMPORT
16.9KiB [ 472KiB/s] [  <=>                                                                                                                       ]
mysqldump: Got errno 32 on write

[ottok]

We identified some scenarios where the database could become corrupted due to the startup/shutdown process. Those issues should be fixed in latest https://app.vagrantup.com/seravo/boxes/wordpress-beta/versions/20210202.0.0

[ottok]

Please help out by testing with latest Seravo/wordpress-beta box and latest Vagrantfile from this repo and comment here if you are still able to get some (related) errors.

[tume91]

Thanks @ottok, will test that later this week

[dubbajones]

Cheers. Changed the vm box to 'wordpress-beta' and was able to halt vagrant and launch it up again without errors and this time after the halted site didnt go to the installation page anymore. However local sites are loading very slow and bigger sites just simply refuse to load at all.

[tume91]

Cheers. Changed the vm box to 'wordpress-beta' and was able to halt vagrant and launch it up again without errors and this time after the halted site didnt go to the installation page anymore. However local sites are loading very slow and bigger sites just simply refuse to load at all.

@dubbajones do you mean that you were not able to boot your site at all? Because I had that problem with bigger project after destroying the project. First I was able to boot and halt it, but after destroy I'm not able to boot it anymore. The project just dies at ssh connection. Had the ssh issue also with the smaller project, but I was able to sort it out with killing the box and reboot.

But I didn't have any issues related to database dump. So it worked okay for me. 👍

[dubbajones]

Hey. Thanks for the reply. I was able to halt and destroy smaller project and launch vm back up and it works (with wordpress-beta box). However the first time the local site loads anything after vagrant up it is very very slow.

With a bigger project 'vagrant up' doesn't go through at all (with wordpress-beta box). It dies at ssh connection just like yours.

[luuptekman]

I had similar problem with SSH connection. There is a separate issue in here somewhere. My workaround was to set my Virtualbox to version 6.1.6. Don't know if that helps for you...

[dubbajones]

Thanks, I will try that and let you know later.

[ottok]

Slowness issues are tracked and debugged in #171

[joniahola]

For me vagrant suspend also wipe database's data. Need to always to load db dump before to start development. I used latest master version.

[lecklin]

Not entirely sure if related, but seems similar to an issue I'm having on Windows. Database seems to get corrupted on vagrant halt. I'm currently running the stable box v20201205.0.0 on this particular site. I did notice mentions of the beta box in this thread that might have fixes to this, and will try that and report back. With the stable box the situation was as follows on a vagrant up:

Importing database from /data/wordpress/.vagrant/shutdown-dump.sql...
--> Loading contents from /data/wordpress/.vagrant/shutdown-dump.sql to database
ERROR 1813 (HY000) at line 25 in file: '/data/wordpress/.vagrant/shutdown-dump.sql': 
Tablespace for table '`vagrant`.`wp_commentmeta`' exists. Please DISCARD the tablespace before IMPORT

It then goes on and on with more errors like this one:

ERROR 1146 (42S02) at line 399 in file: '/data/wordpress/.vagrant/shutdown-dump.sql':
Table 'vagrant.wp_options' doesn't exist

It does ultimately output:

Success: Imported from '/data/wordpress/.vagrant/shutdown-dump.sql'.

However the site is in the install state, plus the install screen has errors about missing tables. As I did export my db before halt (because this happened earlier too), I thought I could just import that with wp db import to get back to where I was. However:

ERROR 1813 (HY000) at line 25: Tablespace for table '`vagrant`.`wp_commentmeta`' exists.
Please DISCARD the tablespace before IMPORT
Fail: Couldn't import vagrant-2021-04-28-84553fe.sql

Running the latest VirtualBox 6.1.20 and latest Vagrant 2.2.15. I actually updated those yesterday to see if that would fix the issue, since it started with earlier versions, but the outputs above are after updating VirtualBox/Vagrant and starting the development site from scratch again with a clone from live.

I haven't had issues earlier with any sites, they started with this site. Not really knowing the specifics of the whole scenario in running the local environment, it's hard to tell what is different. Did this site use an older box present on my system initially, but something in the files you clone from live when starting is different? Now of course the box is newer for this site, since I thought updating might fix the issues.

Anyway as I mentioned, I noticed that beta box might help with this. So I'll go ahead and try that. Will report back.

[lecklin]

The latest seravo/wordpress-beta box seems to fix the issues for me. Switched from the latest stable (v20201205.0.0) to the latest beta (v20210317.0.0).

1. Completely wiped the local environment I was having issues with in my previous comment
2. Cloned in production again
3. Changed the Vagrantfile to use the beta box
4. Ran first up

At least the first time after making some changes, halting, rebooting my computer entirely (just to simulate regular conditions) and bringing it up again resulted in everything being intact.

I guess in some cases you could just switch the box being run, but at least for me the database during the issues got corrupted entirely preventing even importing from production. So the only option was to start the local environment from scratch.