I created a new install with 2.1.0. When I stop the install, it says "Uh-oh! Local ran into an issue while dumping site database to the site’s “app/sql” directory. Please check the local-by-flywheel.log file for more details." There is not an app/sql folder being created by this install. That seems broken with 2.1.0. I also don’t know where local-by-flywheel.log is. Searching that on my Mac shows no results.

Hey Scott, If that error is showing now then was probably happening before. We just made it warning in 2.1.0 since it’s a big problem if you lose the VM. You can find local-by-flywheel.log by going to Help » Reveal Local’s Log.

Got it thanks. Nov 1, 2017, 3:11 PM PDT - info: [main/stopSite] Stopping site: running mydumper Nov 1, 2017, 3:11 PM PDT - info: [main/stopSite] Stopping site: killing container 91189a6d41b47562330cc4d9cb4ed25a27e5e388ec660653d8e78d4a32f36910 Nov 1, 2017, 3:11 PM PDT - error: [main/stopSite] mydumper stderr Segmentation fault Nov 1, 2017, 3:11 PM PDT - error: [main/stopSite] mydumper stdout

Should I be concerned? It’s happening every time I stop the VM, quite bothersome :frowning:

Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: running mydumper Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: running mydumper Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: running mydumper Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: running mydumper Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: running mydumper Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: killing container 084e95faa0b07918fbe551692908264f89cd43356c0f0b74cd01d1e1731da57d Nov 9, 2017, 7:15 AM GMT-7 - error: [main/stopSite] mydumper stderr Segmentation fault Nov 9, 2017, 7:15 AM GMT-7 - error: [main/stopSite] mydumper stdout Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: killing container 081564c89d4b8f25bc14170f376ca16a73e871da7250ce1945eb05c02f63c179 Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: killing container 27a99e1e0d2c3147496eea0ba2c5d3054d5e47dc80efe2547933d2227c99313a Nov 9, 2017, 7:15 AM GMT-7 - info: [main/stopSite] Stopping site: killing container e8001a0b630a1e6e4e7616672e0112478f66cf66a488072e2e8940a21b63921e Nov 9, 2017, 7:15 AM GMT-7 - error: [main/stopSite] mydumper stderr rm: cannot remove '/app/sql': Directory not empty Nov 9, 2017, 7:15 AM GMT-7 - error: [main/stopSite] mydumper stdout Nov 9, 2017, 7:16 AM GMT-7 - info: [main/stopSite] Stopping site: killing container 705dafb795fd886d2bd7882acdf3610e0cd24db75705ed04ee78942b912c3b65 Nov 9, 2017, 7:16 AM GMT-7 - error: [main/stopSite] mydumper stderr rm: cannot remove '/app/sql': Directory not empty Nov 9, 2017, 7:16 AM GMT-7 - error: [main/stopSite] mydumper stdout This is what’s showing in my log each time this is now happening to me. Just FYI. So far nothing has blown up, but annoying the warning shows up every time.

Issue stopping site on 2.1.0

Support

clay November 6, 2017, 8:16pm 5

Hey Scott,

Is this same site as 502 Bad Gateway (solved)?

If so, I would try opening Adminer and/or Sequel Pro and make sure you can export the site from there.

Topic		Replies	Views
Error backing up database when stopping site / mydumper Segmentation Fault Support	33	10329	June 10, 2020
Getting a dump error every time I shut down a site Uncategorized	5	1949	December 27, 2017
Error while backing up database on shutdown Support	0	1501	February 12, 2018
Could not dump database while exporting Uncategorized	13	3557	November 13, 2017
Site Database Backup Error Support	0	406	October 14, 2019

Issue stopping site on 2.1.0

Related topics