On Thursday, August 14, 2014 9:02:40 PM UTC-4, Nikolaus Rath wrote: > > On 08/14/2014 03:17 PM, Adam Watkins wrote: > > Upgrading from revision 20 to 21... > > Unexpected server reply to copy operation: > > 200 OK > > Date: Thu, 14 Aug 2014 21:04:15 +0000 > > Server: RestServer/1.0 > > Content-Length: 189 > > Content-Type: application/xml > > ETag: "d7ed6a310a47b69a91e13e655245fac9" > > Cache-Control: no-cache > > Connection: close > > > > <?xml version="1.0" encoding="UTF-8"?> > > <CopyObjectResult><LastModified>2014-08-14T21:04:15.000Z</LastModified> > > <ETag>"d7ed6a310a47b69a91e13e655245fac9"</ETag> > > </CopyObjectResult> > > > > [...]
> > Does this look like a deviation from S3-compatibility, which I should > > report to GreenQloud? > > Yes. They are not declaring the proper XML namespace (which would be > http://s3.amazonaws.com/doc/2006-03-01/ > <http://www.google.com/url?q=http%3A%2F%2Fs3.amazonaws.com%2Fdoc%2F2006-03-01%2F&sa=D&sntz=1&usg=AFQjCNHS3kxugwRdqhZ6oS1Bzav7PPtrmQ>) > > for the CopyObjectResult tag. > > Best, > -Nikolaus > Sorry to re-open an old thread, But I've run into a similar problem with Dream Host's "S3 Compatible" DreamObjects. When I create a filesystem, touch a file, and then umount it I get the following: Unmounting file system... Dumping metadata... ..objects.. ..blocks.. ..inodes.. ..inode_blocks.. ..symlink_targets.. ..names.. ..contents.. ..ext_attributes.. Compressing and uploading metadata... Wrote 212 bytes of compressed metadata. Cycling metadata backups... Backing up old metadata... Unexpected server reply: expected XML, got: 200 OK Date: Mon, 01 Sep 2014 14:45:08 +0000 Server: Apache Transfer-Encoding: chunked Content-Type: binary/octet-stream Uncaught top-level exception: Traceback (most recent call last): File "/usr/bin/mount.s3ql", line 9, in <module> load_entry_point('s3ql==2.11', 'console_scripts', 'mount.s3ql')() File "/usr/lib/s3ql/s3ql/mount.py", line 251, in main cycle_metadata(backend) File "/usr/lib/s3ql/s3ql/metadata.py", line 127, in cycle_metadata backend.copy("s3ql_metadata", "s3ql_metadata_bak_0") File "/usr/lib/s3ql/s3ql/backends/comprenc.py", line 290, in copy self._copy_or_rename(src, dest, rename=False, metadata=metadata) File "/usr/lib/s3ql/s3ql/backends/comprenc.py", line 323, in _copy_or_rename self.backend.copy(src, dest, metadata=meta_raw) File "/usr/lib/s3ql/s3ql/backends/common.py", line 46, in wrapped return method(*a, **kw) File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 368, in copy root = self._parse_xml_response(resp, body) File "/usr/lib/s3ql/s3ql/backends/s3c.py", line 520, in _parse_xml_response raise RuntimeError('Unexpected server response') RuntimeError: Unexpected server response Is this the same problem? If so, I'd like to report the bug to Dream Host, but the link Nikolaus provided above does not work, so I don't know how to describe the bug to them. Could some one provide a link to (of description of) the S3 API call that I piont to when submitting a bug report to D H? Thanks, Rich -- 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.
