Error Copying Backup: InvalidObjectName: null
-
Hello,
I seem to be having an issue where Nextcloud backups aren't working properly. As of the past few days everything seems to have been working fine, but since yesterday I started getting the following error:box:backups [Nextcloud Domain] Unable to backup { BoxError: Error copying [DO Spaces Backup Name]: InvalidObjectName InvalidObjectName: null at Response.done (/home/yellowtent/box/src/storage/s3.js:247:52) at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:369:18) at Request.callListeners (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:688:14) at Request.transition (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:14:12) at /home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:690:12) name: 'BoxError', reason: 'External Error', details: {}, message: InvalidObjectName InvalidObjectName: null'
Any help with this would be greatly appreciated!
Thank you!
-
@robi Yes, that seems to have been the problem -- I turned off encryption and it seems to have worked out. Even manual backups were failing, just changed it back and it failed again. This seems to have happened right around the upgrade to 6.1.1. I'll have to dig into the issue more. I really appreciate your help!
-
@jlx89 In rsync mode + encryption, there are filename length limitations - https://docs.cloudron.io/backups/#encryption . You can run the command below to see if you have large filenames (you have to run this in Nextcloud's web terminal):
cd /app/data find . -type f -printf "%f\n" | awk '{ print length(), $0 | "sort -rn" }' | less
-
@girish Thanks! This ended up being a combination of issues I believe. So throttling on the backups due to using rsync, encryption, and file names ended up being too long (only a few) So I've changed some settings around and it seems to have been resolved. I appreciate the help from both @robi and yourself.