P.S : mount.s3ql --version
S3QL 2.15
Le jeudi 17 mai 2018 19:34:45 UTC+2, Elsa D. a écrit :
>
> Hello,
> While uploading data, mount.s3ql suddently crashed with this in the syslog
> Database was 14.9Mb
> Before the crash i have this in the log:
> May 17 18:36:11 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.mount.run: Dumping metadata...
> May 17 18:36:11 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..objects..
> May 17 18:36:12 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..blocks..
> May 17 18:36:12 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..inodes..
> May 17 18:36:13 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..inode_blocks..
> May 17 18:36:14 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..symlink_targets..
> May 17 18:36:14 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..names..
> May 17 18:36:14 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..contents..
> May 17 18:36:14 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.dump_metadata: ..ext_attributes..
> May 17 18:36:15 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.upload_metadata: Compressing and uploading metadata...
> May 17 18:36:21 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.upload_metadata: Wrote 14.9 MiB of compressed metadata.
> May 17 18:36:21 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.upload_metadata: Cycling metadata backups...
> May 17 18:36:21 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> s3ql.metadata.cycle_metadata: Backing up old metadata...
>
> Then :
>
> May 17 18:37:06 Aton mount.s3ql[1588:Metadata-Upload-Thread]
> root.excepthook: Uncaught top-level exception:#012Traceback (most recent
> call last):#012 File "/usr/lib/s3ql/s3ql/mount.py", line 64, in
> run_with_except_hook#012 run_old(*args, **kw)#012 File
> "/usr/lib/s3ql/s3ql/mount.py", line 657, in run#012
> upload_metadata(backend, fh, self.param)#012 File
> "/usr/lib/s3ql/s3ql/metadata.py", line 326, in upload_metadata#012
> cycle_metadata(backend)#012 File "/usr/lib/s3ql/s3ql/metadata.py", line
> 125, in cycle_metadata#012 cycle_fn("s3ql_metadata_bak_%d" % i,
> "s3ql_metadata_bak_%d" % (i + 1))#012 File
> "/usr/lib/s3ql/s3ql/backends/comprenc.py", line 312, in copy#012
> self._copy_or_rename(src, dest, rename=False, metadata=metadata)#012 File
> "/usr/lib/s3ql/s3ql/backends/comprenc.py", line 346, in
> _copy_or_rename#012 self.backend.copy(src, dest, metadata=meta_raw)#012
> File "/usr/lib/s3ql/s3ql/backends/swift.py", line 442, in copy#012
> self._copy_helper('POST', '/%s%s' % (self.prefix, dest), headers)#012 File
> "/usr/lib/s3ql/s3ql/backends/common.py", line 107, in wrapped#012 return
> method(*a, **kw)#012 File "/usr/lib/s3ql/s3ql/backends/swift.py", line
> 408, in _copy_helper#012 self._do_request(method, path,
> headers=headers)#012 File "/usr/lib/s3ql/s3ql/backends/swift.py", line
> 251, in _do_request#012 raise HTTPError(resp.status, resp.reason,
> resp.headers)#012s3ql.backends.s3c.HTTPError: 404 Not Found
>
> sorry for the lack of line return, but since i'm not sure where to put
> right return to make it more readable, i prefer to put none by myself.
> After, i used s3qladm download-metadata just to see wich metadata where in
> the storage, and i got this result:
> The following backups are available:
> No Name Date
> 0 s3ql_metadata 2018-05-17 18:32:09
> 1 s3ql_metadata_bak_0 2018-05-17 18:27:34
> 2 s3ql_metadata_bak_1 2018-05-17 18:23:42
> 3 s3ql_metadata_bak_10 2018-05-17 17:50:21
> 4 s3ql_metadata_bak_2 2018-05-17 18:18:51
> 5 s3ql_metadata_bak_3 2018-05-17 18:14:01
> 6 s3ql_metadata_bak_4 2018-05-17 18:08:36
> 7 s3ql_metadata_bak_5 2018-05-17 18:05:05
> 8 s3ql_metadata_bak_6 2018-05-17 18:01:33
> 9 s3ql_metadata_bak_7 2018-05-17 17:57:42
> 10 s3ql_metadata_bak_8 2018-05-17 17:57:42
> 11 s3ql_metadata_bak_9 2018-05-17 17:54:02
> 12 s3ql_metadata_new 2018-05-17 18:36:15
>
> Is this error related to S3QL itself (wich i doubt a bit about it), or is
> it the fault from the swift provider?
> thanks in advance for the help
>
>
>
--
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.
