influxd inspect verify-wal
This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
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
| Flag | Description | Input Type | |
|---|---|---|---|
-h | --help | Help for the verify-wal command. | |
-v | --verbose | Enable verbose logging. | |
--wal-path | Path to WAL directory (default is ~/.influxdbv2/engine/wal) | string |
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.