On most systems this works fine, but on this one system, whenever it
does a large transfer, it gets hung during the umount.s3ql.
Using s3ql-1.19 since this system cannot move to python 3.3 yet.
This particular bucket is in the AWS S3 Ireland region.
Other buckets that have not had much data transferred will umount.s3ql fine.
The unmount.s3ql is invoked right after the data transfer finished
copying to the bucket.
ps -ef shows (edited bucketname):
root 4061 1 14 19:31 ? 00:27:07 /usr/bin/python2.7
/usr/bin/mount.s3ql --cachedir /backups/cloudcache --cachesize 512000
--compress none --authfile /mydir/s3qlauth s3://irelandbucket/subdir/
/backups/ireland
root 15551 15538 0 20:49 ? 00:00:00 sh -c umount.s3ql
/backups/ireland >/tmp/cloud_discon_15538 2>&1
root 15552 15551 0 20:49 ? 00:00:00 /usr/bin/python2.7
/usr/bin/umount.s3ql /backups/ireland
>From mount.log |grep 4061:
2017-01-11 19:31:31.937 [4060] MainThread: [daemonize] Daemonizing,
new PID is 4061
2017-01-11 19:33:01.342 [4061] Dummy-24: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
2017-01-11 19:34:55.897 [4061] Thread-14: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:35:21.011 [4061] Thread-10: [backend] Encountered error
exception ([Errno 104] Connection reset by peer), retrying call to
ObjectW.close...
2017-01-11 19:35:55.351 [4061] Thread-15: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:38:03.728 [4061] Thread-5: [backend] Encountered error
exception ([Errno 104] Connection reset by peer), retrying call to
ObjectW.close...
2017-01-11 19:39:17.903 [4061] Thread-8: [backend] Encountered error
exception ([Errno 104] Connection reset by peer), retrying call to
ObjectW.close...
2017-01-11 19:41:12.015 [4061] Thread-16: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:46:01.414 [4061] Thread-17: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:47:28.720 [4061] Thread-6: [backend] Encountered error
exception ([Errno 104] Connection reset by peer), retrying call to
ObjectW.close...
2017-01-11 19:48:06.767 [4061] Thread-18: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:50:20.140 [4061] Thread-11: [backend] Encountered error
exception ([Errno 104] Connection reset by peer), retrying call to
ObjectW.close...
2017-01-11 19:50:38.969 [4061] Thread-19: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:52:39.434 [4061] Thread-20: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
2017-01-11 19:54:02.386 [4061] Thread-3: [backend] Encountered error
exception ([Errno 110] Connection timed out), retrying call to
ObjectW.close...
The strange thing is that all of the data landed fine, and if I reboot
the system, no data blocks are removed by fsck.s3ql. It just never
finished the umount.s3ql.
Any suggestions? Anything else in the mount.log or cache directory
that would give better clues?
It is repeatable, so I could try whatever suggestions you have.
Andy
--
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.
