Metabase crashing and no info in Logs

Yeah, sorry about that.

Free memory: ~4091mb out of 8gb with Metabase running
I am running Red Hat Enterprise Linux 7.6 on a VMWare VM in our enterprise environment
Metabase: You’re on version v0.32.8, Built on 2019-05-13
(SELinux disabled)

Java:

openjdk version "1.8.0_212"
OpenJDK Runtime Environment (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)

Normally I am running Metabase as a service (from the docs, the init.d file)

And I did not see any anomalies in other logfiles unfortunately.

My current plan is to replace the init.d script with a systemd file that will restart on fail,
because the crash happens about every couple of hours

@naxels
Strange - and everything is up-to-date.
Without something more to go on besides “Killed”, I wouldn’t know where the problem could be.
There’s a couple of PRs that covers systemd, but this one is probably the most complete.

Thank you,
I now have Metabase running as a service using init.d still, however am continuously monitoring the memory of the system, hoping to find a spike somewhere that might explain the ‘Killed’, all the while doing what I was already doing before the crashes.

Hi @flamber,

I watched the memory as I was using Metabase, unfortunately the VM never ran out of memory yet the metabase service was killed anyway (no mention in the logs since i started from init.d)

I will now setup the service with systemd and an always Restart

1 Like