On Apr 24 2015, [email protected] wrote:
> 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) ?

Hmm. After a 502 error S3QL tries to re-establish the connection
completely. The only difference is that it does not attempt to contact
the auth server again. Could it be that the auth server sends you to a
different endpoint when you restart S3QL?

If you run a traffic dump tool like Wireshark, you should be able to see
if S3QL connects to the same server when you restart.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

-- 
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.

Reply via email to