I attempted to upgrade from version 0.23.1 to 0.28.5 thinking that minor version updates would be innocuous and as simple as the upgrade instructions indicated. After following those instructions, however, I am unable to use my Metabase, and am concerned that the hundreds of questions my organization has created may be lost.
I’m looking for pretty broad advice at this point, and any help would be greatly appreciated in either:
- Fixing the issue with my current metabase
- Finding a strategy to import the queries from my old database to use a new metabase instance
I am:
- Deploying using AWS
- Have a separately hosted MySQL database for Metabase data
- Not super familiar with Docker so apologies in advance
When I pull the logs from my instance after attempting to deploy 0.28.5 I see the following:
04-10 22:35:30 e[1mINFO metabase.dbe[0m :: e[36mVerifying mysql Database Connection ...e[0m
04-10 22:35:30 e[1mINFO metabase.dbe[0m :: Verify Database Connection ... ✅
04-10 22:35:30 e[1mINFO metabase.dbe[0m :: Running Database Migrations...
04-10 22:35:30 e[1mINFO metabase.dbe[0m :: Setting up Liquibase...
04-10 22:35:30 e[1mINFO metabase.dbe[0m :: Liquibase is ready.
04-10 22:35:30 e[1mINFO metabase.dbe[0m :: Checking if Database has unrun migrations...
04-10 22:36:23 e[1mWARN liquibasee[0m :: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
04-10 22:36:23 e[1mWARN liquibasee[0m :: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
04-10 22:36:23 e[1mINFO metabase.dbe[0m :: Database has unrun migrations. Waiting for migration lock to be cleared...
04-10 22:36:25 e[1mWARN metabase.utile[0m :: e[31mauto-retry metabase.db$wait_for_migration_lock_to_be_cleared$fn__19114@79200f8: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.e[0m
04-10 22:36:27 e[1mWARN metabase.utile[0m :: e[31mauto-retry metabase.db$wait_for_migration_lock_to_be_cleared$fn__19114@79200f8: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.e[0m
04-10 22:36:29 e[1mWARN metabase.utile[0m :: e[31mauto-retry metabase.db$wait_for_migration_lock_to_be_cleared$fn__19114@79200f8: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.e[0m
04-10 22:36:31 e[1mWARN metabase.utile[0m :: e[31mauto-retry metabase.db$wait_for_migration_lock_to_be_cleared$fn__19114@79200f8: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.e[0m
04-10 22:36:33 e[1mWARN metabase.utile[0m :: e[31mauto-retry metabase.db$wait_for_migration_lock_to_be_cleared$fn__19114@79200f8: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.e[0m
java.lang.Exception: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.
at metabase.db$wait_for_migration_lock_to_be_cleared$fn__19114.invoke(db.clj:153)
Any ideas on how to solve this?