Upgrade from 4.1 to 4.8 failing


Metabase is running jar file version 0.4.1 on windows server 2019. It is using postgresql database. All good there.

We decided to upgrade to the latest version 0.4.81. Tried twice and both times failed.

According to instructions you stop the service, replace jar file and restart the service. Simple enough.

But after restarting service metabase is starting up showing welcoming pages forever.
I can't find the logs to see what might be wrong and there is nothing in windows event logs at all.

I know I can get logs from metabase once you get into from troubleshooting section but that option is unavailable since we can't login in.

Is there another way to get metabase logs to see what went wrong with update?
Searched hard disks but could not locate any metabase related logs.

Java version looking fine:
openjdk version "11.0.11" 2021-04-20
OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode)

Windows server 2019 is up to date...

Help would be much appreciated.


Forgot to include diagnostic info:

"browser-info": {
"language": "en-GB",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36 Edg/",
"vendor": "Google Inc."
"system-info": {
"file.encoding": "Cp1252",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.11+9",
"java.vendor": "AdoptOpenJDK",
"java.vendor.url": "https://adoptopenjdk.net/",
"java.version": "11.0.11",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.11+9",
"os.name": "Windows Server 2019",
"os.version": "10.0",
"user.language": "en",
"user.timezone": "Australia/Brisbane"
"metabase-info": {
"databases": [
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "13.3"
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.3.2"
"run-mode": "prod",
"version": {
"date": "2022-05-16",
"tag": "v0.43.1",
"branch": "release-x.43.x",
"hash": "7f1a1c4"
"settings": {
"report-timezone": "Australia/Queensland"

Try running the jar file in the cmd console directly, that way you get all the output in the console.

Or a better option, setup Log4J, you do it once then forget it, log files are always there. See Metabase logs

This is my log4j2.xml file:

<?xml version="1.0" encoding="UTF-8"?>
    <Console name="STDOUT" target="SYSTEM_OUT">
      <PatternLayout pattern="%date %level %logger{2} :: %message%n%throwable">
        <replace regex=":basic-auth \\[.*\\]" replacement=":basic-auth [redacted]"/>

    <!-- This file appender is provided as an example -->
    <RollingFile name="FILE" fileName="./log/metabase.log" filePattern="./log/metabase.log.%i">
        <SizeBasedTriggeringPolicy size="500 MB"/>
      <DefaultRolloverStrategy max="2"/>
      <PatternLayout pattern="%d{DEFAULT}{Pacific/Auckland} ::::: [%t] %-6p%c - %m%n">
        <replace regex=":basic-auth \\[.*\\]" replacement=":basic-auth [redacted]"/>


    <Logger name="metabase" level="INFO"/>
    <Logger name="metabase-enterprise" level="INFO"/>
    <Logger name="metabase.plugins" level="DEBUG"/>
    <Logger name="metabase.server.middleware" level="DEBUG"/>
    <Logger name="metabase.query-processor.async" level="DEBUG"/>
    <Logger name="com.mchange" level="ERROR"/>

    <Root level="WARN">
      <AppenderRef ref="STDOUT"/>
	  <AppenderRef ref="FILE"/>

Hope that helps.

(Edited to add link to Metabase logs page)

send the logs when you upgrade

Thanks notrom, will talk with sysadmins to see if that can be done in our environment.

Thanks luiggi, will do