Database rolling back after restarting Local

Support
1

Hello,

Since a few days one of the sites in Local is having problems with the database.
Every time I close the program and restart it my database seems to reverted to a version of the 24th of May (6 days ago). This doesn’t occur when I just stop the site and start it again. Restarting Local machine also doesn’t reset my database.

I am on OSX 10.13.4
I was using Local by Flywheel 2.2.4
This morning I have tried Local by Flywheel 2.3.1 (Pre-release) and the same behavior happens.
MySQL version is 5.6.34

The website has a database that was imported through Sequel Pro as it was running live elsewhere.
The Local instal ran for 10 days without any problems.
The website is a multisite instal.
As far as I can tell this doesn’t happen for other sites.

Attached is the log (I redacted some stuff).
It is quite clean until I started using the Pre-release 2.3.1
local-by-flywheel.log (435.9 KB)

Any idea’s what could be the problem?

Thanks.

Edit:

A little update, in trying to export the site I received an error. The database couldn’t be exported.
The following is in the log:

May 30, 2018, 10:43 AM GMT+2 - error: [worker: export-site-worker] (HTTP code 500) server error - Container     92e0055c39597e3474080b4c0a79b3017e7da3009d918a640721051644419a43 is not running 
Error: (HTTP code 500) server error - Container 92e0055c39597e3474080b4c0a79b3017e7da3009d918a640721051644419a43 is not running 
    at /Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:239:17
    at getCause (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:269:7)
    at Modem.buildPayload (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:238:5)
    at IncomingMessage.<anonymous> (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:214:14)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:188:7)
    at endReadableNT (_stream_readable.js:975:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
2

Setting up a new site and migrating everything over seems to have fixed the problem.
No idea what could have caused this strange corruption, but it seems we can continue without losing data again.

2 Likes