Metabase Jar file version 0.43.2 Issue

{
  "browser-info": {
    "language": "en-US",
    "platform": "Win32",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "Cp1252",
    "java.runtime.name": "Java(TM) SE Runtime Environment",
    "java.runtime.version": "10.0.2+13",
    "java.vendor": "Oracle Corporation",
    "java.vendor.url": "http://java.oracle.com/",
    "java.version": "10.0.2",
    "java.vm.name": "Java HotSpot(TM) 64-Bit Server VM",
    "java.vm.version": "10.0.2+13",
    "os.name": "Windows Server 2012",
    "os.version": "6.2",
    "user.language": "en",
    "user.timezone": "Asia/Calcutta"
  },
  "metabase-info": {
    "databases": [
      "mysql",
      "h2",
      "sqlserver",
      "postgres"
    ],
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "11.8"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.2.18"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2021-08-03",
      "tag": "v0.40.2",
      "branch": "release-x.40.x",
      "hash": "b884d29"
    },
    "settings": {
      "report-timezone": "Asia/Calcutta"
    }
  }
}

Hi,

We recently tried upgrading our metabase version to the latest available version 0.43.2. After completing all the steps as mentioned in the documentation, it was taking too long to host the service. We waited for 45 mins max. Later we rolled back to previous version.

Is any one facing same issue with the latest version of jar file.
Any help / guidance will be apppreciated

Hi @abhijeetkumkale
You need to upgrade to 0.40.7 immediately, or newer: https://github.com/metabase/metabase/security/advisories/GHSA-vmm4-cwrm-38rj
Then upgrade to Java 11: https://www.metabase.com/docs/latest/operations-guide/java-versions.html

Without seeing the logs during the failed startup, then it's impossible to know what is going on.