Having some issues


#1

I’m currently running metabase in a docker container for my organization. It’s using it’s own h2 database as I understand it. Something happened however and now metabase cannot connect to it’s own h2 instance. as a result, metabase exits, the container relaunches on exit, rinse, repeat.

01-03 15:42:22 e[1mINFO metabase.coree[0m :: Starting Metabase version v0.27.1 (055e448 release-0.27.0) …
01-03 15:42:22 e[1mINFO metabase.coree[0m :: System timezone is ‘GMT’ …
01-03 15:42:24 e[1mWARN metabase.drivere[0m :: No -init-driver function found for ‘metabase.driver.google’
01-03 15:42:24 e[1mINFO metabase.coree[0m :: Setting up and migrating Metabase DB. Please sit tight, this may take a minute…
01-03 15:42:24 e[1mINFO metabase.dbe[0m :: e[36mVerifying h2 Database Connection …e[0m
01-03 15:42:24 e[1mERROR metabase.drivere[0m :: Failed to connect to database: org.h2.jdbc.JdbcSQLException: Sequence “SYSTEM_SEQUENCE_DCA4F94B_C473_412E_A755_C0EC7CA1ACE7” not found; SQL statement:
CREATE CACHED TABLE PUBLIC.METABASE_FIELDVALUES(
ID INT DEFAULT (NEXT VALUE FOR PUBLIC.SYSTEM_SEQUENCE_DCA4F94B_C473_412E_A755_C0EC7CA1ACE7) NOT NULL NULL_TO_DEFAULT SEQUENCE PUBLIC.SYSTEM_SEQUENCE_DCA4F94B_C473_412E_A755_C0EC7CA1ACE7 SELECTIVITY 100,
CREATED_AT TIMESTAMP NOT NULL SELECTIVITY 100,
UPDATED_AT TIMESTAMP NOT NULL SELECTIVITY 100,
VALUES CLOB,
HUMAN_READABLE_VALUES CLOB,
FIELD_ID INT NOT NULL SELECTIVITY 100
) [90036-194]
01-03 15:42:24 e[1mERROR metabase.coree[0m :: Metabase Initialization FAILED: Assert failed: Unable to connect to Metabase h2 DB.
(binding [allow-potentailly-unsafe-connections true] (require (quote metabase.driver)) ((resolve (quote metabase.driver/can-connect-with-details?)) engine details))
01-03 15:42:24 e[1mINFO metabase.coree[0m :: Metabase Shutting Down …
01-03 15:42:24 e[1mINFO metabase.coree[0m :: Metabase Shutdown COMPLETE
01-03 15:42:34 e[1mINFO metabase.utile[0m :: Loading Metabase…
01-03 15:42:39 e[1mINFO util.encryptione[0m :: DB details encryption is DISABLED for this Metabase instance. :unlock:
See http://www.metabase.com/docs/latest/operations-guide/start.html#encrypting-your-database-connection-details-at-rest for more information.
01-03 15:42:45 e[1mINFO metabase.coree[0m :: Starting Metabase in STANDALONE mode
01-03 15:42:45 e[1mINFO metabase.coree[0m :: Launching Embedded Jetty Webserver with config:
{:port 3000, :host “0.0.0.0”}

01-03 15:42:45 e[1mINFO metabase.coree[0m :: Starting Metabase version v0.27.1 (055e448 release-0.27.0) …
01-03 15:42:45 e[1mINFO metabase.coree[0m :: System timezone is ‘GMT’ …
01-03 15:42:46 e[1mINFO metabase.coree[0m :: Metabase Shutting Down …
01-03 15:42:46 e[1mINFO metabase.coree[0m :: Metabase Shutdown COMPLETE

It just does this over and over again and I’m not quite sure where to start on either recovering the database or resolving the issue.

Since i’m using docker, I have a bind mount to my system, I don’t see a metabase.db.h2.db in that folder anymore. I only see metabase.db.mv.db and metabase.db.trace.db. did something happen that corrupted this data base? Are there any tools that would easily allow me to fix the h2 database instance?