Hello Everyone,
I encountered an issue while trying to restore Metabase after mistakenly attempting a downgrade. Here’s a detailed account of what happened:
- Initial Downgrade Attempt: I mistakenly attempted to downgrade Metabase from version 1.46.6.3 to version 0.50.18. This resulted in the following error message:
yaml
Copy code
Liquibase is ready.
2024-08-04 05:13:48,761 INFO db.liquibase :: Checking if Database has unrun migrations...
2024-08-04 05:13:49,361 INFO db.liquibase :: Database has unrun migrations. Checking if migration lock is taken...
2024-08-04 05:13:51,369 WARN util.jvm :: auto-retry metabase.db.liquibase$wait_for_migration_lock$fn__44585@3639bf18: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.
2024-08-04 05:13:53,374 WARN util.jvm :: auto-retry metabase.db.liquibase$wait_for_migration_lock$fn__44585@3639bf18: Database has migration lock; cannot run migrations. You can force-release these locks by running `java -jar metabase.jar migrate release-locks`.
...
2024-08-04 05:14:01,401 INFO metabase.core :: Metabase Shutting Down ...
2024-08-04 05:14:01,401 INFO metabase.server :: Shutting Down Embedded Jetty Webserver
2024-08-04 05:14:01,410 WARN db.liquibase :: ()
2024-08-04 05:14:01,411 INFO metabase.core :: Metabase Shutdown COMPLETE
- Attempt to Restore with Current Version: After this, I attempted to install the current version (1.46.6.3), but encountered the following error during initialization:
php
Copy code
2024-08-04 08:17:17,814 WARN plugins.lazy-loaded-driver :: Warning: plugin manifest for :bigquery does not include connection properties
2024-08-04 08:17:17,814 DEBUG plugins.lazy-loaded-driver :: Registering lazy loading driver :bigquery...
...
2024-08-04 08:17:18,181 INFO db.liquibase :: Checking if Database has unrun migrations...
2024-08-04 08:17:19,676 ERROR metabase.core :: Metabase Initialization FAILED
liquibase.exception.ValidationFailedException: Validation Failed:
100 change sets check sum
migrations/000_migrations.yaml::v45.00-001::snoe was: 9:24324f06a65a9bb339c735f02cbfb47f but is now: 8:ec8c30ee4f53a15a36c402d8124bb8af
migrations/000_migrations.yaml::v45.00-002::snoe was: 9:d2c9f50f5a29947a07e4808957d63ab6 but is now: 8:6da7a6285edb138c404de0eeba209570
...
at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:296)
...
at clojure.lang.RestFn.invoke(RestFn.java:397)
at clojure.lang.AFn.applyToHelper(AFn.java:152)
at clojure.lang.RestFn.applyTo(RestFn.java:132)
at clojure.lang.Var.applyTo(Var.java:705)
at clojure.core$apply.invokeStatic(core.clj:667)
at clojure.core$apply.invoke(core.clj:662)
at metabase.bootstrap$_main.invokeStatic(bootstrap.clj:31)
at metabase.bootstrap$_main.doInvoke(bootstrap.clj:28)
at clojure.lang.RestFn.invoke(RestFn.java:397)
at clojure.lang.AFn.applyToHelper(AFn.java:152)
at clojure.lang.RestFn.applyTo(RestFn.java:132)
at clojure.lang.Var.applyTo(Var.java:705)
at clojure.core$apply.invokeStatic(core.clj:667)
at clojure.core$apply.invoke(core.clj:662)
at metabase.bootstrap.main(Unknown Source)
2024-08-04 08:17:19,690 INFO metabase.core :: Metabase Shutting Down ...
2024-08-04 08:17:19,691 INFO metabase.server :: Shutting Down Embedded Jetty Webserver
2024-08-04 08:17:19,701 INFO metabase.core :: Metabase Shutdown COMPLETE
Request for Assistance: Can anyone provide guidance on how to resolve these issues? Specifically:
- How can I safely release the migration lock if the previous attempts didn’t work?
- What steps should I follow to address the checksum validation errors and restore Metabase to a working state?
Thank you in advance for your help!