Rclone size on a dropbox container guarantees a too_many_requests error
What is your rclone version (output from rclone version)
1.57 (error appeared somewhere in-between the 1.54 and 1.57 {I double checked} [I believe with the recent batch mode dropbox update in 1.56])
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Windows 10, 64 bit
Which cloud storage system are you using? (eg Google Drive)
Dropbox
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone size dropbox:
The rclone config contents with secrets removed.
I don't feel comfortable doing this, don't feel like decrypting my config, and don't think it is relevant (the names of the containers are accurate to what they are)
A log from the command with the -vv flag
C:\rclone>rclone size dropbox: -vv
2021/12/08 02:22:03 DEBUG : rclone: Version "v1.57.0" starting with parameters ["rclone" "size" "dropbox:" "-vv"]
2021/12/08 02:22:03 DEBUG : Creating backend with remote "dropbox:"
Enter configuration password:
password:
2021/12/08 02:22:10 DEBUG : Using config file from "C:\\rclone\\rclone.conf"
2021/12/08 02:23:50 NOTICE: too_many_requests/..: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 02:23:50 DEBUG : pacer: low level retry 1/10 (error too_many_requests/..)
2021/12/08 02:23:50 DEBUG : pacer: Rate limited, increasing sleep to 5m0s
2021/12/08 02:23:50 DEBUG : pacer: Reducing sleep to 3m45s
2021/12/08 02:23:50 NOTICE: too_many_requests/..: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 02:23:50 DEBUG : pacer: low level retry 1/10 (error too_many_requests/..)
2021/12/08 02:23:50 DEBUG : pacer: Reducing sleep to 2m48.75s
2021/12/08 02:23:50 DEBUG : pacer: Rate limited, increasing sleep to 5m0s
2021/12/08 02:23:50 DEBUG : pacer: Reducing sleep to 3m45s
2021/12/08 02:23:50 NOTICE: too_many_requests/.: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 02:23:50 DEBUG : pacer: low level retry 1/10 (error too_many_requests/.)
2021/12/08 02:23:50 DEBUG : pacer: Rate limited, increasing sleep to 5m0s
2021/12/08 02:23:50 NOTICE: too_many_requests/...: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 02:23:50 DEBUG : pacer: low level retry 1/10 (error too_many_requests/...)
2021/12/08 02:23:50 NOTICE: too_many_requests/..: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 02:23:50 DEBUG : pacer: low level retry 2/10 (error too_many_requests/..)
2021/12/08 02:23:51 DEBUG : pacer: Reducing sleep to 3m45s
2021/12/08 02:24:16 INFO : Signal received: interrupt
2021/12/08 02:24:16 INFO : Dropbox root '': Commiting uploads - please wait...
2021/12/08 02:24:16 INFO : Exiting...
I wanted to add as well that the total speed indicator and ETA (everything past the %) for -P progress on copy broke as well for dropbox in between these versions, but that's a very insignificant bug so it honestly doesn't seem worth making a whole report
I am playing with some (throttling) improvements to the pacer and is therefore a curious to know if a (automatic) reduction of the checkers would work in this situation too (and perhaps give a result quicker than --tps-limit).
Are you able to get a result without too_many_requests if you do like this
4 fails as well. I can try 2/1 but they take quite some time:
etexter@seraphite ~ % rclone size DB: --checkers 4
2021/12/08 11:04:03 NOTICE: too_many_requests/: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 11:04:03 NOTICE: too_many_requests/.: Too many requests or write operations. Trying again in 300 seconds.
2021/12/08 11:04:04 NOTICE: too_many_requests/: Too many requests or write operations. Trying again in 300 seconds.
The other piece that I commented the linked issue was confirming that the API as per app registration not per user as I was originally told from DB Support.
So you can easily test with making another app registration so you don't break your main use.
