Backup fails
-
wrote on Nov 14, 2024, 12:04 PM last edited by
timestamp] /home/yellowtent/box/node_modules/aws-sdk/lib/services/s3.js:712
[no timestamp] resp.error = AWS.util.error(new Error(), {
[no timestamp] ^
[no timestamp]
[no timestamp] Part number must be in the range 1 - 10000 -
wrote on Nov 14, 2024, 12:16 PM last edited by
https://github.com/s3tools/s3cmd/issues/613
I can provide the full log if needed.
-
looks like a long fixed issue. Which S3 provider are you using?
For the moment maybe you can set a higher part-size in the advanced backup settings if something causes a part number higher than 10000 in your case. Maybe that helps for your case.
-
looks like a long fixed issue. Which S3 provider are you using?
For the moment maybe you can set a higher part-size in the advanced backup settings if something causes a part number higher than 10000 in your case. Maybe that helps for your case.
-
wrote on Nov 14, 2024, 6:39 PM last edited by
I tried to adjust the part size. I now get:
Task 3427 crashed with code 1
Looking at the logs, no footprint of a crash.
-
That is strange to not see any errors, maybe also increase the backup memory limit to ensure it doesn't run out of memory. Overall we also got news that Backblaze introduced rate-limits, so not sure how viable that is in the long run. Might be worth looking into another backup storage sadly.
-
That is strange to not see any errors, maybe also increase the backup memory limit to ensure it doesn't run out of memory. Overall we also got news that Backblaze introduced rate-limits, so not sure how viable that is in the long run. Might be worth looking into another backup storage sadly.