Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-03-14 Thread Joseff Betancourt
On Tuesday, February 10, 2015 at 12:52:43 PM UTC-5, Adam Watkins wrote: > > For better or worse, these errors don't seem related to the use of S3QL. > (S3QL seems more intolerant of them than some other S3-compatible tools, > but its behaviour seems quite sensible to me.) I'm seeing them with '

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-10 Thread Adam Watkins
For better or worse, these errors don't seem related to the use of S3QL. (S3QL seems more intolerant of them than some other S3-compatible tools, but its behaviour seems quite sensible to me.) I'm seeing them with 's3cmd sync' between two buckets on StorageQloud as well, unfortunately. I am con

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-04 Thread Nikolaus Rath
Adam Watkins writes: > On Tuesday, 3 February 2015 18:57:44 UTC, Nikolaus Rath wrote: > > Could you try the attached patch and confirm that the 'NoneType' > error > no longer occurs? > > > It does seem to have fixed the 'NoneType' error, Great, thanks! Best, -Nikolaus -- GPG

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-04 Thread Adam Watkins
On Tuesday, 3 February 2015 18:57:44 UTC, Nikolaus Rath wrote: > > Could you try the attached patch and confirm that the 'NoneType' error > no longer occurs? > It does seem to have fixed the 'NoneType' error, Adam -- You received this message because you are subscribed to the Google Groups

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-03 Thread Nikolaus Rath
Adam Watkins writes: > Applied the patch, and ran it a few times. > > I've attached a log where the NoneType does *not* happen (22.07.30) > and a log where it *does* (22.13.02), in the off-chance that'll help. Thanks! I think I figured out what's happening here. It does not have any adverse effec

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-02 Thread Adam Watkins
Applied the patch, and ran it a few times. I've attached a log where the NoneType does *not* happen (22.07.30) and a log where it *does* (22.13.02), in the off-chance that'll help. Regards, Adam -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsu

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-02 Thread Nikolaus Rath
Adam Watkins writes: > Apologies Nikolaus. I've attached a full traceback. > > The "AttributeError: 'NoneType' object has no attribute 'close'" error > doesn't seem to reliably occur. This is really odd. Could you possibly apply the attached patch to your dugong installation, try to reproduce the

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-02 Thread Nikolaus Rath
Adam Watkins writes: > Apologies Nikolaus. I've attached a full traceback. > > The "AttributeError: 'NoneType' object has no attribute 'close'" error > doesn't seem to reliably occur. Thanks! > I have raised an issue with GreenQloud but they seem rather unwilling > to improve the S3-compatibilit

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-02 Thread Adam Watkins
Apologies Nikolaus. I've attached a full traceback. The "AttributeError: 'NoneType' object has no attribute 'close'" error doesn't seem to reliably occur. I have raised an issue with GreenQloud but they seem rather unwilling to improve the S3-compatibility of StorageQloud, which is a shame. Th

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-02 Thread Nikolaus Rath
Adam Watkins writes: > Encountered ConnectionClosed exception (connection closed > unexpectedly), retrying call to Backend.lookup for the 3-th time... > ..processed 147/16379 objects (0.9%, 0 bytes rewritten)..Uncaught > top-level exception: > > Original/inner traceback (most recent call last): >

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-01 Thread Adam Watkins
Here are the lines that I skipped over: # During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/s3qladm", line 9, in load_entry_point('s3ql==2.13', 'console_scripts', 's3qladm')() File "/usr/local/lib/python3.4/s

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-01 Thread Nikolaus Rath
Adam Watkins writes: > self._parse_error_response(resp) > File > "/usr/local/lib/python3.4/site-packages/s3ql-2.13-py3.4-linux-i686.egg/s3ql/backends/s3c.py", > line 539, in _parse_error_response > raise get_S3Error(tree.findtext('Code'), tree.findtext('Message'), > resp.headers) > s3ql.backends.s

Re: [s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-01 Thread Nikolaus Rath
Adam Watkins writes: > I am trying to upgrade my filesystem from revision 21 to 22, using > S3QL 2.13. > > However, I am getting the following error: > > # > >> s3qladm --authfile authinfo2 --backend-options dumb-copy upgrade > s3c://s.greenqloud.com:443/my-lovely-bucket > ... > "/usr/local/li

[s3ql] s3ql.backends.s3c.S3Error: CannotPutData: (upgrading from 21 to 22)

2015-02-01 Thread Adam Watkins
I am trying to upgrade my filesystem from revision 21 to 22, using S3QL 2.13. However, I am getting the following error: # > s3qladm --authfile authinfo2 --backend-options dumb-copy upgrade s3c://s.greenqloud.com:443/my-lovely-bucket ... Downloading & uncompressing metadata... Reading met