Skip to content

s3 request timeout  #101

@shulemmosko

Description

@shulemmosko

backups seem to work and upload fine to wasabi s3 but this is the second time im getting the following error in middle the backup process.
can it be a wasabi rate limit ? and is there a way to control it within backy2?

ERROR: [backy2.logging] S3 operation failed; code: RequestTimeout, message: Your socket connection to the server was not read from or written to within the timeout period, resource: None, request_id: 7E165C3811D9E95F:A, host_id: EDkmwXLfAEaFRAqyVz+/D7jxgCWg4BdyqPgjFeoQBelqdZffGexHP3WugRw9F245467ZBZ1yz8>
ERROR: [backy2.logging] Backy failed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions