![]() ![]() 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. Sometimes Metabase may run out of memory and you will see messages like Error R14 (Memory quota exceeded) in the Heroku logs.You can resolve this by upgrading to the hobby tier or higher. This prevents things like Pulses and Metabase background tasks from running when scheduled and at times makes the app appear to be slow when really it’s just Heroku reloading your app. Metabase heroku free#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |