Checking snapshot status via Kopia server this morning, I discovered a lot of pending snapshot tasks together with these messages in the logs:
Error: error flushing writer: error flushing manifests: unable to write content: unable to create pending pack: unable to get session ID: unable to write session marker: unable to write session marker: sa3cd1f223784cfe2d06708352f5550ed-sd7eece2028c4c1db102: unable to complete PutBlob(sa3cd1f223784cfe2d06708352f5550ed-sd7eece2028c4c1db102) despite 10 retries.
and
Error: unable to determine if maintenance is required: error getting status: error reading schedule blob: unable to complete GetBlob(kopia.maintenance,0,-1) despite 10 retries.
While I was looking through the Tasks screen I saw Kopia automatically kick off a periodic maintenance task which completed successfully. The pending snapshot tasks then began to successfully execute.
The Tasks screen in Kopia server shows errors going back 6 hours. If I view the snapshot history for the failed snapshots and select “Show (n) identical snapshots” I can see a gap starting at 2300 yesterday for one snapshot, 0000 this morning for another snapshot. Snapshots are set to run hourly.
I am using s3 provider (Wasabi) and Kopia 0.8.0-beta3. https://status.wasabi.com shows 100% uptime for my storage region. My ISP’s service status pages don’t indicate any planned or unplanned downtime. Any ideas?