Documentation

influxd inspect verify-wal

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The influxd inspect verify-wal command analyzes the Write-Ahead Log (WAL) to check if there are any corrupt files. If it finds corrupt files, the command returns the names of those files. It also returns the total number of entries in each scanned WAL file.

Usage

influxd inspect verify-wal [flags]

Output details

influxd inspect verify-wal outputs the following for each file:

  • The file name.
  • The first position of any identified corruption or “clean” if no corruption is found.

After the verification is complete, it returns a summary with:

  • The number of WAL files scanned.
  • The number of WAL entries scanned.
  • A list of files found to be corrupt.

Flags

FlagDescriptionInput Type
-h--helpHelp for the verify-wal command.
-v--verboseEnable verbose logging.
--wal-pathPath to WAL directory (default is ~/.influxdbv2/engine/wal)string

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2