Crashes / Can't save questions


Guys, this is driving me nuts. I simply, quite often, find myself unable to save a native question, for a unkown reason. It will simply stay like this:

It may stay like that for 10, 20 minutes, and do nothing. The most annoying thing is that I’m trying to correct a mistyped SQL in the question, at least in this example, and I’m not being able to.

And then, the most critical one, metabase simply stops. I run my instance from the jar file (currently on 0.29.3, still looking for agood moment to switch to 0.30, given it introduces major lauyout changes), in a debian, on Amazon EC2. The logging simply stops, and no relevant info is shown at the end. I though it might be due to java virtual machine memory, but my jenkins instance, also in java, is still running alright - problem is with my metabase instance (not with my browser or machine, it goes down for everyone in the company, in any browser, and, given the log is quiet, I think it is really gone, despite the process being running).

Any light on these issues? I’ve come to the point that we’ve created a custom command on our EC2, “metakill”, which kills metabase process and restarts it, so often it happens.

Related issues:

I can’t find any help on either of these topics, nor workarounds. It is really depleting metabase functionality for us, since we can’t really guarantee it is available at the moment.

EDIT: I was running metabase with the standard command, “java -jar metabase.jar” thing. Yesterday, I saw something in the logs related to OutOfMemory java error, and, then, I increased the memory alocated to Metabase process in the JVM, using something like “java -Xmx1024k -jar”. I’ve thougth of it as an idea stemming out of a Stack Overflow question reference below. So far, it SEEMS to have solved the crashing issue.

EDIT2: no good on the crasing issue, even with the memory enhancement. Still crashing, and most of the time with no data on the logs - everything is running finely, and, all of a sudden, log goes silent.

[ANSWERED] SQL advantages over the h2 file

Possibly related: Save question dialog box doesn't complete


Yeah, the behavior is pretty much the same. Thanks for pointing out, I hadn’t come across that question on my googling. But, relating to logs, I can’t see anything that might be related to that. The most weir thing I see is “Card X doesn’t have cached read_permissions”, but I’m nearly sure that is not the cause. If someone finds it needed, I might upload some piece of log when I see that behavior.

As for environment info, I’m running querying it mostly on Chrome, though I’m able to see the problem on Edge as well (both on windows OS, with, as mentioned before, metabase jar file running on Amazon EC2), querying against a MySQL database (also on Amazon).

Seeing my MySQL running queries, aparently, even after you click “Cancel” on Metabase, the query is still running. Using the “kill” command on MySQL, to effectively terminate the queries, seems to help with the not saving problem. I’m still to confirm this, though.


Hehe, that’s what you get when you ask two possibly unrelated questions and it’s easy for me to find a thread related to one of them. :wink: And yes root cause for the issue I linked above doesn’t seem like it’s nailed yet.

Anyway, re-reading what you said on the Metabase becoming unresponsive issue I would say there are other types of bugs than a crash (which you don’t see now that you feed it some more memory). For example if it’s waiting for some limited resource to become available for example. You mention you’re on EC2 and version 0.29.3. Depending on if you’re running behind e.g. an NGinx proxy with https and http/2 configured you may be experiencing the bug that was fixed in 0.30.2 and quite well covered on the forum here and in several GitHub issues. Might be worth upgrading to 0.30.2+


May it be related to be running with h2 file, instead of SQL?
Opened a diferent post for that doubt, it is linked to this one.