tlrobinson reopened this Jun 3, 2016 kritop commented Jul 5, 2016 anyone any clue on the health 503 errors? Reload to refresh your session. Join us to help others who have the same bug. I had docker, virtualbox and some other softwares like that. weblink
Thanks. It’s a large topic more fit for a DBA to answer, but as long as you have a dump of the Metabase database you’ll be good to go. We recommend upgrading to the latest Safari, Google Chrome, or Firefox. Thanks! https://github.com/metabase/metabase/issues/1853
And yes, it was a fresh install. Running the Jar File This is the simplest and most basic way of running Metabase. Terms Privacy Security Status Help You can't perform that action at this time. there is no .lock file in the /tmp folder and nothing else is using the H2 file.
We'll start recommending 2GB and try to find places to slim down. Was there an upgrade involved or did the server die? KeithFrohn 2016-11-03 18:27:17 UTC #3 I don't have a special file system. Run the Metabase data migration command using the appropriate environment variables for the target database you want to migrate to.
I'll be more vigilant about keeping logs if/when the container dies again. Metabase Mysql You mentioned that you ran the H2 shell to verify the database, you should make sure to completely close that down before launching Metabase because H2 doesn't like having multiple clients or had you run the metabase.jar file before? https://github.com/metabase/metabase/issues/2884 The machine is not especially locked down.
H2 (default) To use the H2 database for your Metabase instance you don’t need to do anything at all. Tired of useless tips? 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) camsaul added OS/Windows Running Metabase labels Aug 31, 2016 camsaul added this to the 0.20.0 milestone Aug 31, 2016 camsaul self-assigned this Aug 31, 2016 Contributor camsaul commented Aug 31, 2016
what version of Metabase are you running? http://discourse.metabase.com/t/h2-connection-timeout-on-launch/746 If for some reason you wanted to see what these changes are and run them manually on your database then we let you do that. Assert Failed: Unable To Connect To Metabase Db. For example: export MB_DB_TYPE=h2 export MB_DB_FILE=/the/path/to/my/h2.db java -jar metabase.jar Postgres For production installations of Metabase we recommend that users replace the H2 database with a more robust option such as Postgres. Connect To H2 Database We recommend upgrading to the latest Safari, Google Chrome, or Firefox.
Below we provide detailed instructions on how to install and run Metabase in a variety of common configurations. have a peek at these guys maliayas referenced this issue Jun 9, 2016 Closed How to recover data from H2 database #2720 Sign up for free to join this conversation on GitHub. The lock file is H2's lock file for it's own transactions/etc. Thanks for the help here, happy to provide any more info it it helps debug the issue more for you guys.
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 I found the crash time was close to the one that some pulses were scheduled to be handled. Looks like the docker container just quit during a db sync. check over here Propose a change on the source Need a different version of the docs?
camsaul closed this Jul 7, 2016 Sign up for free to join this conversation on GitHub. Log In H2 connection timeout on launch rcahearn 2016-10-07 13:14:06 UTC #1 We've been happy users of metabase for awhile now. I mean, I can start it, go to localhost:3000 but the loading screen stays (i can't access the create account screens) and in the logs, there are infinite calls to GET
cp /path/to/metabase.db.h2.db /path/to/metabase2.db.h2.db MB_DB_FILE=/path/to/metabase2.db java -jar metabase.jar camsaul added the Error label Jul 5, 2016 thekantian commented Jul 6, 2016 @camsaul interestingly that seems to have fixed the issue for us. export MB_DB_TYPE=postgres export MB_DB_DBNAME=metabase export MB_DB_PORT=5432 export MB_DB_USER= export MB_DB_PASS= export MB_DB_HOST=localhost java -jar metabase.jar load-from-h2 It is expected that you will run the command against a brand new (empty!) database The server itself stayed up, and all the other containers on the machine appear to have continued running. Contributor camsaul commented Feb 20, 2016 Powershell?
This offers a greater degree of performance and reliability when Metabase is running with many users. Any insight much appreciated... You can change the application database to use MySQL using these environment variables. http://globalcryptonews.com/connect-to/tectia-failed-to-connect-to-broker.html Using HTTPS with Metabase If you have an ssl certificate and would prefer to have Metabase run over HTTPS directly using its webserver you can do so by using the following
For example: export MB_DB_TYPE=mysql export MB_DB_DBNAME=metabase export MB_DB_PORT=3306 export MB_DB_USER=
Contributor camsaul commented Jul 7, 2016 Glad it worked @thekantian. agilliland added the Error label Feb 4, 2016 chtefi commented Feb 4, 2016 I'm not on my PC right now but I was running on Windows 10, metabase.jar from the website