rclone combine: --poll-interval=0 is not disabling polling for Google Drive remotes.
Polling is disabled fine when mounting the individual remotes individually or if the combine is changed to a union instead
Polling is disabled fine for the individual Google Drive remotes when mounting one of them directly.
Also, changing the type to a union also disables polling fine.
As a sidenote, the polling interval cannot be changed to a non-default value for the combine either.
The problem is that with polling enabled for i.e. just 10 shared drives in the combine, the Google Drive remote will be permanently overwhelmed ("Error 403: Quota exceeded for quota metric ...") just by the polling performed.
Run the command 'rclone version' and share the full output of the command.
Which cloud storage system are you using? (eg Google Drive)
Google Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone mount
The rclone config contents with secrets removed.
[google_drive]
type = drive
scope = drive
token = ...
team_drive =
[shared-drive]
type = alias
remote = google_drive,team_drive=0AM...VA,root_folder_id=:
[AllDrives-combine]
type = combine
upstreams = "shared-drive=shared-drive:/"
[AllDrives-union]
type = union
upstreams = "shared-drive:/"
Command line
combine fails, performs polling:
/usr/bin/rclone mount AllDrives-combine: .... --poll-interval=0
union works fine, polling disabled:
/usr/bin/rclone mount AllDrives-union: .... --poll-interval=0
Would this cause the remotes to appear empty at times? I have an issue where the Google remote would appear empty at times and since I'm using it for Plex it would empty my library in plex causing me to have to re-scan everything in. It has only start the few weeks.
I had some trouble with this, since the documentation at https://rclone.org/drive/ for creating a key is no longer up to date.
This is due to the iam.disableServiceAccountKeyCreation policy now being enforced by default by Google.
So, before you are allowed to create keys for service accounts, you have to become a Organization Policy Administrator (or at least have the permissions orgpolicy.policies.create , orgpolicy.policies.delete , orgpolicy.policies.update , and orgpolicy.policy.get), and change the iam.disableServiceAccountKeyCreation policy to not enforced.
Ergo, first you need to add yourself as a Organization Policy Administrator at the organization level - this can be a bit confusing, as you don't have the needed permissions to do this inside the project, even as the owner of the project.
Anyway, service account and .json key is now added - it helped, thanks!
Thanks, works like a charm! - all noise is now completely gone
Ah yes, I am using a service account, based on a .json file. And this .json file has values for i.e. client_id and private_key in it - sorry for confusing things
The client id/secret path intimidated me with the "submit your app for verification" step last time I tried it, so I thought I'd try the other way this time.
