Metabase deploy failing in free plan

hey there :wave: :wave:,

i tried to deploy metabase:v0.43.3 in free plan it continuously failing when i check logs nothing there except this
June 15 08:31:04 AM 2022-06-15 03:01:04,884 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__30535@5ce323f: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.
June 15 08:31:07 AM 2022-06-15 03:01:07,084 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__30535@5ce323f: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.
June 15 08:31:09 AM 2022-06-15 03:01:09,783 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__30535@5ce323f: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.
June 15 08:31:11 AM 2022-06-15 03:01:11,992 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__30535@5ce323f: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.
June 15 08:31:14 AM 2022-06-15 03:01:14,094 WARN metabase.util :: auto-retry metabase.db.liquibase$wait_for_migration_lock_to_be_cleared$fn__30535@5ce323f: Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.
June 15 08:31:16 AM 2022-06-15 03:01:16,288 ERROR metabase.core :: Metabase Initialization FAILED
June 15 08:31:16 AM liquibase.exception.LockException: 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.liquibase$wait_for_migration_lock_to_be_cleared$fn__30535.invoke(liquibase.clj:125)
at metabase.util$do_with_auto_retries.invokeStatic(util.clj:494)
at metabase.util$do_with_auto_retries.invoke(util.clj:486)
at metabase.util$do_with_auto_retries.invokeStatic(util.clj:501)
at metabase.util$do_with_auto_retries.invoke(util.clj:486)
at metabase.util$do_with_auto_retries.invokeStatic(util.clj:501)
at metabase.util$do_with_auto_retries.invoke(util.clj:486)
at metabase.util$do_with_auto_retries.invokeStatic(util.clj:501)
at metabase.util$do_with_auto_retries.invoke(util.clj:486)
at metabase.util$do_with_auto_retries.invokeStatic(util.clj:501)
at metabase.util$do_with_auto_retries.invoke(util.clj:486)
at metabase.util$do_with_auto_retries.invokeStatic(util.clj:501)
at metabase.util$do_with_auto_retries.invoke(util.clj:486)
at metabase.db.liquibase$wait_for_migration_lock_to_be_cleared.invokeStatic(liquibase.clj:120)
at metabase.db.liquibase$wait_for_migration_lock_to_be_cleared.invoke(liquibase.clj:116)
at metabase.db.liquibase$migrate_up_if_needed_BANG_.invokeStatic(liquibase.clj:136)
at metabase.db.liquibase$migrate_up_if_needed_BANG_.invoke(liquibase.clj:130)
at metabase.db.setup$fn__34835$migrate_BANG___34840$fn__34841$fn__34842.invoke(setup.clj:68)
at metabase.db.liquibase$fn__30492$do_with_liquibase__30497$fn__30498.invoke(liquibase.clj:59)
at metabase.db.liquibase$fn__30492$do_with_liquibase__30497.invoke(liquibase.clj:51)
at metabase.db.setup$fn__34835$migrate_BANG___34840$fn__34841.invoke(setup.clj:63)
at metabase.db.setup$fn__34835$migrate_BANG___34840.invoke(setup.clj:40)
at metabase.db.setup$fn__34894$run_schema_migrations_BANG___34899$fn__34900.invoke(setup.clj:121)
at metabase.db.setup$fn__34894$run_schema_migrations_BANG___34899.invoke(setup.clj:115)
at metabase.db.setup$fn__34946$setup_db_BANG___34951$fn__34952$fn__34955$fn__34956.invoke(setup.clj:147)
at metabase.util$do_with_us_locale.invokeStatic(util.clj:715)
at metabase.util$do_with_us_locale.invoke(util.clj:701)
at metabase.db.setup$fn__34946$setup_db_BANG___34951$fn__34952$fn__34955.invoke(setup.clj:145)
at metabase.db.setup$fn__34946$setup_db_BANG___34951$fn__34952.invoke(setup.clj:144)
at metabase.db.setup$fn__34946$setup_db_BANG___34951.invoke(setup.clj:138)
at metabase.db$setup_db_BANG_$fn__34981.invoke(db.clj:65)
at metabase.db$setup_db_BANG_.invokeStatic(db.clj:60)
at metabase.db$setup_db_BANG_.invoke(db.clj:51)
at metabase.core$init_BANG__STAR_.invokeStatic(core.clj:98)
at metabase.core$init_BANG__STAR_.invoke(core.clj:81)
at metabase.core$init_BANG_.invokeStatic(core.clj:138)
at metabase.core$init_BANG_.invoke(core.clj:133)
at metabase.core$start_normally.invokeStatic(core.clj:150)
at metabase.core$start_normally.invoke(core.clj:144)
at metabase.core$_main.invokeStatic(core.clj:183)
at metabase.core$_main.doInvoke(core.clj:177)
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 metabase.core.main(Unknown Source)
June 15 08:31:16 AM 2022-06-15 03:01:16,383 INFO metabase.core :: Metabase Shutting Down …
June 15 08:31:16 AM 2022-06-15 03:01:16,482 INFO metabase.server :: Shutting Down Embedded Jetty Webserver
June 15 08:31:16 AM 2022-06-15 03:01:16,682 INFO metabase.core :: Metabase Shutdown COMPLETE
June 15 08:31:54 AM Warning: environ value jdk-11.0.15+10 for key :java-version has been overwritten with 11.0.15
June 15 08:31:54 AM WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
June 15 08:32:15 AM 2022-06-15 03:02:15,586 INFO metabase.util :: Maximum memory available to JVM: 123.8 MB

you can test deploying free plan of metabase using my repo

Hi there,
We aren’t able to actually support Metabase itself, the errors from that output provide instructions:

Database has migration lock; cannot run migrations. You can force-release these locks by running java -jar metabase.jar migrate release-locks.

You might find that Metabase doesn’t run very well on the free plan, it has limited resources so may fail to run optimally,

Regards,

John B

ok thank you @John_B for your reply and i have another question ,
when i connect my postgres db with psycopg2 api when it is in suspend status i am not getting status code. instead of that i am getting exception but when i try metabase api clearly giving me status code <Response [503]> it means service unavailable.
So how can i get status code for postgres when my service is in suspend status is there any way?? please suggest one way how can i get status code when it is unavailable
i hope i get a reply
Thank you

You’d need to catch the exception and return a status code.

John B