Sqlite corruption after 3.18.1 update

Issue Summary

I’m seeing ghost update fail trying to bump from 3.17.1 to 3.18.1, something in the migrations seems to munge our sqlite db. The update offers to roll back to 3.17.1 but that doesn’t work, as the db is left in a unusable state.

To Reproduce

cd /var/www/ghost && ghost update

The intial error message after that suggested running journalctl -u ghost_ideas-rejuvenation-com -n 50 (should say to that with sudo?) which returns

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?

Technical details:

• Ghost Version: 3.17.1
• Node Version: 12.18.0
• Browser/OS: Ubuntu 16.04
• Database: sqlite

[acburdine]

@tobiasboyd the changes in that commit actually convert relative sqlite paths to be absolute, so you’d essentially be manually applying the changes 😄. If you do that prior to the changes in that commit shipping, then once a new version of the CLI is released it will ignore your absolute sqlite path

[ErisDS]

Sorry, I moved the issue and then got distracted before I finished writing a comment.

This is caused by having a relative path in your config, as Vikas said we’re not quite sure why it broke recently yet. The workaround is to change the path to your sqlite DB to be absolute in your config as seen here: https://forum.ghost.org/t/unable-to-upgrade-ghost-from-v3-16-1-to-v3-18-0/14836/5

I’m gonna close this now as it’s fixed in master by https://github.com/TryGhost/Ghost-CLI/commit/3f07b05a63cbaa94dd02a26b66a83901e0bdab3c, but thanks for the nicely written report 😃