B2 timeouts

776 views
Skip to first unread message

alex...@silvagoncalves.com

unread,
Jan 9, 2021, 7:00:12 AM1/9/21
to s3ql
Hello,
In a backblaze backend I'm seeing lots of warnings like this:

Encountered B2Error (503 : service_unavailable - no tomes available), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 4)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
WARNING: Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 5)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 4)...
WARNING: Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 5)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 4)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 4)...
WARNING: Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 5)...
WARNING: Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 6)...
WARNING: Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 7)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 3)...
Encountered ConnectionClosed (server closed connection), retrying ObjectW.close (attempt 4)...

It looks it's some sort of timeout. Is there any setting that can solve this?

Thanks.

alex...@silvagoncalves.com

unread,
Jan 9, 2021, 7:02:04 AM1/9/21
to s3ql
s3ql version: 3.7.0
Backblaze backend: b2://backend

Daniel Jagszent

unread,
Jan 9, 2021, 7:05:21 PM1/9/21
to s3ql
Hi,

Encountered B2Error (503 : service_unavailable - no tomes available), retrying ObjectW.close (attempt 3)...
does S3QL stop or is this just a warning? Looks like a "tome" is a storage unit ( https://help.backblaze.com/hc/en-us/articles/218485257-B2-Resiliency-Durability-and-Availability ) and B2 had none available there for a while.


It looks it's some sort of timeout. Is there any setting that can solve this?
The S3QL B2 backend should handle these according to https://www.backblaze.com/b2/docs/integration_checklist.html so there actually is no need to "solve" this. S3QL should retry the upload for 24 hours when getting these warnings.
Reply all
Reply to author
Forward
0 new messages