Wasabi is experiencing issues currently, and its greatly reduced
capacity results in overloaded messages. Adding a quick bit of debug
code to print one out, they look like this:
503 Service Unavailable
Connection: close
Content-Type: application/xml
Date: Mon, 07 Oct 2019 20:02:31 +0000
Content-Length: 218
<ErrorResponse
xmlns="https://iam.amazonaws.com/doc/2010-05-08/";><Error><Type>Sender</Type><Code>TemporarilyUnavailable</Code><Message>Maximum
number of server active requests exceeded</Message></Error></ErrorResponse>
Unfortunately, S3QL (still on 3.0 here, but looks to be the same in HEAD
from the code) doesn't handle them. Most trivially, the line:
raise get_S3Error(tree.findtext('Code'), tree.findtext('Message'),
resp.headers)
doesn't work; seems it needs
tree.findtext('.//{https://iam.amazonaws.com/doc/2010-05-08/}Code') and
the same with Message to actually find the elements. (Or of course pass
a namespace map to abbreviate). Not sure if actual Amazon S3 produces
the same XML or not...
Other than this, it'd be nice of S3QL would retry these requests,
instead of exiting. But at least the above gets the actual error reported.
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/730bdc99-6035-3196-d778-8724e870eee3%40metrics.net.
