obsync crashes when src file is unreadable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello. I'm trying to synchronize 2 Amazon S3 buckets, but obsync keeps
crashing when it tries to read a certain file. Here is the message
displayed when run with --verbose --more-verbose:

Mon, 16 Jul 2012 15:24:48 GMT
/src-bucket/1356/file
Traceback (most recent call last):
  File "/usr/bin/obsync", line 1165, in <module>
    sobj = src_all_objects.next()
  File "/usr/bin/obsync", line 636, in next
    k = self.bucket.get_key(key.name)
  File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line 195,
in get_key
    response.status, response.reason, '')
S3ResponseError: S3ResponseError: 403 Forbidden

ERROR TYPE: unknown, ORIGIN: source

I checked with other S3 clients the state of the file and indeed, it
can not be read and I can't change its ACLs. From what I gather, this
is one of those very rare cases of unreadable Amazon S3 files due to
the failure of Amazon's underlying storage (I think the file will be
automatically recovered at some point later by S3).

It would be nice if obsync would get over this error, continue with
the other files and just display a warning message that the file
couldn't be read. Is there something I can do right now that can make
obsync continue copying (maybe a quick hack in the code or something)?

This is happening on Ubuntu 12.10 2012-07-05, obsync version 0.47.2-0ubuntu2.

Thanks.
--
Fita Adrian
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux