Since upgrading to rclone 1.46 my automated jobs have all gotten stuck with endless 403 errors when trying to upload to Drive. The API console consistently shows queries per 100 seconds approaching 1000 from a single instance of rclone trying to upload a few hundred files to a very large Drive.
I dug into the problem and found that the jobs that hung all used the --files-from switch.
Steps to reproduce:
/mnt/media/Plex contains 646 files of varying size, from a few KB to several GB.
~/dl/filelist is a list of those files
Drive is a crypt drive backed by a Google Drive
rclone copy -vvP --files-from ~/dl/filelist /mnt/media/Plex/ Drive:
Result: rclone stalls forever at 0 kb/s throwing constant 403 rate limit errors and eventually hits the daily cap leading to a 24 hour ban. It never even checks any files.
Transferred: 0 / 0 Bytes, -, 0 Bytes/s, ETA - Errors: 0 Checks: 0 / 0, - Transferred: 0 / 0, -
Pointing rclone directly at the local directory:
rclone copy -vvP /mnt/media/Plex/ Drive:
Result: rclone immediately starts checking files, copies everything normally with very few 403 errors.
I have reproduced this bug on two different machines, both running rclone 1.46 release and 16.04.1-Ubuntu.