We’ve been happy users of metabase for awhile now. Yesterday, the docker container exited (not sure why) and when trying to start the container again we get this error:
10-07 13:08:20 INFO metabase.core :: Starting Metabase in STANDALONE mode
10-07 13:08:20 INFO metabase.core :: Launching Embedded Jetty Webserver with config:
{:port 3000, :host "3a68e9e9bf23"}
10-07 13:08:20 INFO metabase.core :: Starting Metabase version v0.19.3 (796613e release-0.19.3) ...
10-07 13:08:20 INFO metabase.core :: System timezone is 'GMT' ...
10-07 13:08:22 DEBUG metabase.driver :: Registered driver :bigquery 🚚
10-07 13:08:22 DEBUG metabase.driver :: Registered driver :crate 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :druid 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :h2 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :mongo 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :mysql 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :postgres 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :redshift 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :sqlite 🚚
10-07 13:08:23 DEBUG metabase.driver :: Registered driver :sqlserver 🚚
10-07 13:08:24 INFO metabase.db :: Verifying h2 Database Connection ...
10-07 13:08:29 ERROR metabase.driver :: Failed to connect to database: Timed out after 5000 milliseconds.
java.lang.AssertionError: 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))
at metabase.db$verify_db_connection.invokeStatic(db.clj:223)
at metabase.db$verify_db_connection.invoke(db.clj:218)
at metabase.db$setup_db.invokeStatic(db.clj:237)
at metabase.db$setup_db.doInvoke(db.clj:229)
at clojure.lang.RestFn.invoke(RestFn.java:421)
at metabase.core$init_BANG_.invokeStatic(core.clj:142)
at metabase.core$init_BANG_.invoke(core.clj:126)
at metabase.core$start_normally.invokeStatic(core.clj:226)
at metabase.core$start_normally.invoke(core.clj:220)
at metabase.core$_main.invokeStatic(core.clj:260)
at metabase.core$_main.doInvoke(core.clj:255)
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)
10-07 13:08:29 ERROR metabase.core :: 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))
10-07 13:08:29 INFO metabase.core :: Metabase Shutting Down ...
10-07 13:08:29 INFO metabase.core :: Metabase Shutdown COMPLETE
We’re running on a t2.micro
AWS instance, and the metabase.db.h2.db
file is 70MB. The db lock file is created, the most recent of which contains:
#FileLock
#Fri Oct 07 13:15:33 GMT 2016
hostName=9f4e7848a1ef
id=1579f48d552e285c179f13cd7622a962af1261a96bc
method=file
server=172.17.0.3\:40948
I copied the db file to my iMac and was able to start up the container using that file, so I’m guessing it’s just not finishing processing in time? Is there a way to increase that 5 second timeout?