[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Failures w/ S3 backend
From: |
Kenneth Loafman |
Subject: |
Re: [Duplicity-talk] Failures w/ S3 backend |
Date: |
Thu, 19 Mar 2009 14:43:21 -0500 |
User-agent: |
Thunderbird 2.0.0.19 (X11/20090105) |
Peter Schuller wrote:
>> Glad you found it. Looks like it may be a boto issue.
>
> IIRC the error message indicated that the S3 server actually failed
> the request due to the date being wrong according to the server. I
> suspect boto is simply sending the request in such a way that the date
> is included, thus allowing the S3 service to fail the request when
> detecting the problem.
>
> This could be wrong of course, just pointing out that it's not
> necessarily a bug in boto even if triggered by boto doing things
> differently.
>
>> I use ntp daemon for setting time. Lots of experience with funny
>> problems cause by time drift, especially when using tools like 'make'.
>
> Have you gotten ntp to react to suspend/resume and do some kind of
> insta-synch? Normally ntpd does not like the clock being significantly
> drifted and won't make a discontiguous jump until significant time has
> passed.
There is a script that runs ntpdate on startup. I guess the trick would
be to tie it into the suspend/resume scripts (forget where they are).
If you run VMware Toolkit in the guest, one of the options is to sync
time with the host. This works pretty well as long as you remember to
start it.
...Ken
signature.asc
Description: OpenPGP digital signature
Re: [Duplicity-talk] Failures w/ S3 backend, Maurizio Vitale, 2009/03/19