Hello, Sometimes, I see these errors (two time for the moment) :
<< mount.s3ql[26219:Thread-10] s3ql.backends.common.wrapped: Encountered HTTPError exception (502 Bad Gateway), retrying call to ObjectW.close for the 3-th time... mount.s3ql[26219:Thread-10] s3ql.backends.common.wrapped: Encountered HTTPError exception (502 Bad Gateway), retrying call to ObjectW.close for the 4-th time... mount.s3ql[26219:Thread-10] s3ql.backends.common.wrapped: Encountered HTTPError exception (502 Bad Gateway), retrying call to ObjectW.close for the 5-th time... mount.s3ql[26219:Thread-10] s3ql.backends.common.wrapped: Encountered HTTPError exception (502 Bad Gateway), retrying call to ObjectW.close for the 6-th time... ... >> This kind of error continue until I restart the S3QL process. For example, this error occur during more than 9 hours (retrying call to ObjectW.close for the 129-th time...). Like the message said, during this error I can't access to the S3QL partition. But when I kill the process and start it, the S3QL partition works again. So I don't understand why the "mount.s3ql" said that there is a 502 error (because when I restart, the gateway respond directly) ? The storage backend is a "OpenStack/Swift" backend and I use S3QL version 2.13. Thank you. -- 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]. For more options, visit https://groups.google.com/d/optout.
