You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: improve troubleshooting and handle integrity check failures
Previously, the utility aborted immediately when an integrity check
failed after restoring the database. It now prints a complete report
along with the specific error that triggered the failure, making it
easier to diagnose issues before exiting.
When issues arise, you can use verbosity flags to understand what’s happening under the hood.
84
+
85
+
### Enable Debug Output
86
+
87
+
Running with `-v` enables debug logging. This shows all parameter combinations that `blobcheck` tries when connecting to the storage provider.
88
+
89
+
For example, connecting to a MinIO server with default settings may fail if virtual host–style requests are used (where the bucket name is treated as part of the hostname):
2025/09/29 14:32:54 DEBUG Failed to list objects error="operation error S3: ListObjectsV2, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Get \"http://test.localhost:29000/?list-type=2\": dial tcp: lookup test.localhost: no such host" env="map
94
+
```
95
+
96
+
In this case, blobcheck will continue trying alternative combinations until it finds one that works. The first successful combination is then used for backup/restore validation.
97
+
98
+
### Enable AWS SDK Tracing
99
+
100
+
Adding a second -v flag provides even deeper insight by enabling AWS SDK trace logs. These include full request/response details exchanged with the storage provider.
101
+
102
+
Using the same failing MinIO example, the output now shows the full request signature, headers, and why the request failed:
0 commit comments