• Task
  • Version · 6.0
  • Troubleshoot

Recover a compressed log file after an interrupted run

Last updated: September 29, 2026

When Liquibase writes a compressed log file, it adds an end marker, also known as a trailer, as it closes the file. If the Liquibase process stops abruptly, that trailer is missing, and compression tools report the file as damaged. Your log data is still readable.

Before you begin

  • You have a compressed log file (.gz) from a Liquibase run that stopped abruptly

  • You have a tool that can decompress gzip files. gunzip is available on Linux and macOS, and on Windows through Git Bash or WSL

Procedure

1

Decompress the log file

Decompress the log file into a plain text file that you can open and share.

Be sure to:

  • Replace your_log_file with the name of your compressed log file. For example, liquibase-update.log.gz

The command writes the log to recovered.log, then reports unexpected end of file and exits with a non-zero status because the trailer is missing. The recovery still succeeded.

A script using set -e stops at that exit status even though the log was recovered.

Note: Every gzip tool reports this file as damaged, including an integrity check such as gunzip -t. That result reflects the missing trailer, not the contents, so it is not a reason to discard the file.

2

Open the recovered log

Open recovered.log in any text editor or log viewer. It contains the log up to the point where the run stopped. The file can end mid-line, because the run ended before Liquibase finished writing that entry.

3

Prevent the problem on future runs

If you run Liquibase where processes are stopped abruptly, write a plain .log file and compress it after the run finishes.

Be sure to:

  • Replace your_log_file with the name you want for the log file. For example, liquibase-update

PreviousHow does Liquibase find files?NextRelease notes