I re-ran it with --debug all and got this output:
[...]
Opening connection to
/backups/cloudcache/s3:=2F=2Feastporterunitrends=2Farchive=2F.db
dump_table(contents): writing 1 rows
..ext_attributes..
Opening connection to
/backups/cloudcache/s3:=2F=2Feastporterunitrends=2Farchive=2F.db
dump_table(ext_attributes): writing 0 rows
Compressing and uploading metadata...
open_write(s3ql_seq_no_1): start
ObjectW(s3ql_seq_no_1).close(): start
_do_request(): start with parameters ('PUT', '/archive/s3ql_seq_no_1',
None, Non
e, {'x-amz-meta-compression': 'BZIP2', 'x-amz-meta-meta-00': 'gAJOLg==',
'Conten
t-Length': 44, 'x-amz-meta-encryption': 'None'}, <open file '<fdopen>',
mode 'w+
b' at 0xc345d20>)
_send_request(): sending request for /archive/s3ql_seq_no_1
_send_request(): Waiting for 100-cont..
Waiting for 100-continue...

It looks like it is near the beginning.   Any ideas what is wrong with this?

On Tue, Oct 21, 2014 at 2:44 PM, Andy Cress <[email protected]> wrote:

>
> Using s3ql-1.17, I encountered an issue that I haven't seen before, where
> mkfs.s3ql seems to be waiting forever (more than a few hours).  An strace
> shows it waiting forever at
> recvfrom(4,
>
> I have a variety of other configurations that work fine, but I don't know
> what is going wrong with this one.  Any ideas?
>
> Output:
> # /usr/bin/python2.7 /usr/bin/mkfs.s3ql --plain --cachedir
> /backups/cloudcache --force --authfile /usr/bp/lists.dir/.s3qlauth
> s3://bucket/subdir/
> Before using S3QL, make sure to read the user's guide, especially
> the 'Important Rules to Avoid Loosing Data' section.
> Creating metadata tables...
> Dumping metadata...
> ..objects..
> ..blocks..
> ..inodes..
> ..inode_blocks..
> ..symlink_targets..
> ..names..
> ..contents..
> ..ext_attributes..
> Compressing and uploading metadata...
>
>

-- 
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.

Reply via email to