After trying to update ghost from 2.12 to 2.13 we are getting a failure with the database migration
Before upgrading we checked the migration lock and we noticed it was unlocked after trying to update it will be stuck restarting because of some failure during the migration process.
Our database is stored on google’s Cloud SQL and unfortunately we have a very large database.
We noticed from googles end that before it aborts the connection it tries to load all the posts.
We think there may be a timeout perhaps that might be breaking the migration before it has completed thus leaving the migration lock on.
Sorry for the bother and thanks for any help!
Steps to Reproduce
- ghost update
Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
OS: Ubuntu, v18.04
Node Version: v8.14.0
Ghost-CLI Version: 1.9.9
Command: ‘ghost update 2.13.0’
Message: Migration lock was never released or currently a migration is running.
Help: If you are sure no migration is running, check your data and if your database is in a broken state, you could run
knex-migrator rollback .
Suggestion: journalctl -u ghost_localhost -n 50
Stack: Error: Migration lock was never released or currently a migration is running.
at Server.server.close (/usr/lib/node_modules/ghost-cli/lib/utils/port-polling.js:38:28)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Server.emit (events.js:208:7)
at emitCloseNT (net.js:1664:8)
at _combinedTickCallback (internal/process/next_tick.js:136:11)
at process._tickCallback (internal/process/next_tick.js:181:9)