Error updating from 4.3.3 to 4.13

I ended up upgrading Ubuntu - worst choice ever…

After it I tried updating Ghost from 4.3.3 to 4.13.0 - the update went well but when it was restarting ghost I’ve got the following error:
[Oddly enough, if I reboot the server, ghost status reports the ghost instance as running, but browsing the website gives the 502 Bad Gateway nginx error, when I ghost restart the error is as follows]

Running Ghost on a DigitalOcean server.
Debug Information:
** OS: Ubuntu, v20.04.3 LTS**
** Node Version: v14.17.6**
** Ghost Version: 4.13.0**
** Ghost-CLI Version: 1.17.3**
** Environment: production**
** Command: ‘ghost restart’**

Message: Ghost was able to start, but errored during boot with: 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_com -n 50

Stack: Error: Ghost was able to start, but errored during boot with: Migration lock was never released or currently a migration is running.
at Server. (/usr/lib/node_modules/ghost-cli/lib/utils/port-polling.js:73:28)
at Object.onceWrapper (events.js:519:28)
at Server.emit (events.js:400:28)
at emitCloseNT (net.js:1661:8)
at processTicksAndRejections (internal/process/task_queues.js:81:21)

I would love to just rollback and maybe figure it out how to upgrade later, but I never rolled back to another version, even though I’ve a backup from 4.3.3
Thanks for any help!

Hello,

You have to upgrade to the last minor of the major and then move to the next major and so on.

On the last versions, there have been a lot of changes on the ghost and sql side.

And don’t forget backups :smiley:

1 Like

Thanks! The ghost-CLI should help in that IMO…
Anyhow, any suggestion to operate the rollback?