Read and respond to this message at:
ERROR: S3 error: 500 (Internal Server Error): InternalError
-Interesting, I have never seen one. What s3cmd command did you run?
She bombs every time on the following command:
/usr/bin/s3cmd sync /etc s3://mybucketname/syncetc 2>&1
Due to the nature of the this directory, could it be that she bombs if the file
being worked on changed during upload?
Or could it be related to the large number of files? Where are you storing all
the md5sum data for each file? In the last run she stopped at file 117 of 1661
which is part of prior attempts of that directory which contains 3617 files.
Though likely unrelated, sync does not always deleting remote files, log file
Summary: 0 local files to upload, 12 remote files to delete
I've got around the problem by taring the directory and uploading, however,
I have found that I can't use md5sums on stagnant tarred directories on account
that a simple change in the order of a file within the tar compilation causes
a different ms5sum result, hence, syncing files rather then tarred directories
is the most efficient though consumes more disk space.
Thank you for your assistance.
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: