Cannot upgrade METABASE from 0.34.2 to latests

Dear all,

Since months we have not been able to upgrade metabase from current version (0.34.2).

In the past we were simply replacing the JAR file in our linux server, each couple of months, but since that version this has not been possible.

We have tried with 0.36 and 0.38 and now with 0.39 without success.

Any ideas why this could be happening?

Thanks in advance!

  "browser-info": {
    "language": "en-US",
    "platform": "Win32",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "": "Java(TM) SE Runtime Environment",
    "java.runtime.version": "1.8.0_201-b09",
    "java.vendor": "Oracle Corporation",
    "java.vendor.url": "",
    "java.version": "1.8.0_201",
    "": "Java HotSpot(TM) 64-Bit Server VM",
    "java.vm.version": "25.201-b09",
    "": "Linux",
    "os.version": "3.8.13-118.31.1.el7uek.x86_64",
    "user.language": "en",
    "user.timezone": "Europe/Madrid"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "mysql",
    "application-database-details": {
      "database": {
        "name": "MariaDB",
        "version": "10.1.38-MariaDB"
      "jdbc-driver": {
        "name": "MariaDB Connector/J",
        "version": "2.5.1"
    "run-mode": "prod",
    "version": {
      "tag": "v0.34.2",
      "date": "2020-02-04",
      "branch": "release-0.34.x",
      "hash": "dab738c"
    "settings": {
      "report-timezone": null

Hi @grimete

Could it be that you are running Metabase as a service?
Upgrading would then require that you shutdown the service before replacing the JAR file, and then start the service again.

Or could it be that you are actually using a different file location than where you are replacing?
Check if any processes are using the JAR-file
lsof | grep "metabase.jar"
Check your service (systemd) configuration to figure out which working directory it's using.

Make sure that you backup the application database before upgrading.

Also, the minimum recommended version of MariaDB as application database is 10.2.2:

Hi Flamber,

thanks for your quick response.

Yes, we are running it as a service but always stopping it before proceeding with the upgrade and replacing the jar file.

As regards MariaDB, I will check with DB Admin, as I can see that indeed, we are not compliant with the minimum requirements (10.1.38 < 10.2.2).

I'll provide feedback as soon as I've managed to get the DB server upgraded first.

Thanks again for your help and for this great tool !!
Metabase Rocks :muscle: :blue_heart:

Hello everyone,

After modifying the CHARACTER SET to utf8mb4 as required, the upgrade gone quickly and smoothly as always.

We have also planned for MariaDB upgrade to be in compliance.

Thanks a lot for your support @flamber.