Re: [Duplicity-talk] Duplicity bug report: crash if the system date is wrong

[Maurizio Vitale]

Maurizio Vitale <address@hidden> writes:

> I don't think so, but I'll find the log and send it to you (which I
> should have done in the first place, laziness...)

of course I shouldn't think too much about things I don't know...
from the log I think the check happens on the Amazon side, but anyhow
well within the boto backend. So, yeah, it appears to be S3 specific.

here's the tail of the log (this one would be huge and I would have
had to comb through it to see if propietary info was in there). Let me
know if you need other portions:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 589, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 582, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 562, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 235, in full_backup
    bytes_written = write_multivol("full", tarblock_iter, globals.backend)
  File "/usr/bin/duplicity", line 162, in write_multivol
    (tdp, dest_filename)))
  File "/usr/lib/python2.5/site-packages/duplicity/asyncscheduler.py", line 
148, in schedule_task
    return self.__run_synchronously(fn, params)
  File "/usr/lib/python2.5/site-packages/duplicity/asyncscheduler.py", line 
174, in __run_synchronously
    ret = fn(*params)
  File "/usr/bin/duplicity", line 161, in <lambda>
    async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename: 
put(tdp, dest_filename),
  File "/usr/bin/duplicity", line 115, in put
    backend.put(tdp, dest_filename)
  File "/usr/lib/python2.5/site-packages/duplicity/backends/botobackend.py", 
line 155, in put
    self.bucket = self.conn.create_bucket(self.bucket_name)
  File "/usr/lib/python2.5/site-packages/boto/s3/connection.py", line 284, in 
create_bucket
    raise S3ResponseError(response.status, response.reason, body)
S3ResponseError: S3ResponseError: 403 Forbidden
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>RequestTimeTooSkewed</Code><Message>The difference between the 
request time and the current time is too 
large.</Message><MaxAllowedSkewMilliseconds>900000</MaxAllowedSkewMilliseconds><RequestId>62F2B0B9C7D70948</RequestId><HostId>ADhowK1n2plGL6vsLDQ4WaWYlRNaxnNF7t/Toli1I8Mv7irNtBe88PljCmljF5BR</HostId><RequestTime>Thu,
 12 Mar 2009 02:49:42 
GMT</RequestTime><ServerTime>2009-03-12T14:00:18Z</ServerTime></Error>

> Maurizio Vitale
>
> Polymath Solutions
> 309 Denniston Ave
> Pittsburgh, PA 15206
>
> T +1.412.453.5606
> M address@hidden
> W www.polymath-solutions.com
>
>
> On Mar 12, 2009, at 2:54 PM, Kenneth Loafman wrote:
>
>> Maurizio Vitale wrote:
>>> I don't seem to be getting the registration confirmation from
>>> Savannah,
>>> hence cannot properly report bugs.
>>> Hope mailing here works as a temporary substitute.
>>>
>>> When starting a backup or a restore on a system where the date is
>>> very
>>> wrong (w.r.t to the system containing
>>> the backup) results in duplicity crashing with a stack dump. The logs
>>> contain enough information to quickly
>>> find and fix the problem, but it would be nice if duplicity exited
>>> cleanly with an error message.
>>
>> Is this related to the S3 restore problem you're having?
>>
>> ...Ken
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk

-- 
Maurizio Vitale
Polymath Solutions