![]() We currently use a Heroku buildpack for deploying Metabase. To fix it: you can either clear the lock using the built-in release-locks command line function, or if needed you can login to your Metabase application database directly and delete the row in the DATABASECHANGELOGLOCK table. This can happen if for some reason Heroku kills your Metabase dyno at the wrong time during startup. The most likely culprit here is a stale database migrations lock that was not cleared.If your Metabase instance is getting stuck part way through the initialization process and only every shows roughly 30% completion on the loading progress.Now that you’ve installed Metabase, it’s time to set it up and connect it to your database. If this happens regularly we recommend upgrading to the standard-2x tier dyno. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |