I encountered a client s3ql system with its system date/time set at about 4
hours before the  actual time.
On that system, attempting to do fsck.s3ql to the cloud resulted in an
infinite set of retries with these messages:

Encountered RequestTimeTooSkewedError exception (RequestTimeTooSkewed: The
difference between the request time and the current time is too large.),
retrying call to Backend.open_read

Is there a way to limit the retries on this?  If it returned, it would be
easy to check for this condition.
Or is there a different way to check for time skew before calling fsck.s3ql?

Andy

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