google does not ban you, but it does block you ability to use the service for a period of time.
have you looked into the logs?
you should see something like 403 user rate limit exceeded
It means you are requesting too many API hits so it’s throttling you down a little.
or Error 403: The download quota for this file has been exceeded., downloadQuotaExceeded
you are blocked for 24 hours.
There are 2 ways you can do it. (aside from syslog which I also have no experience with... did you just copy this confguration from someone or do actually know to to use syslog? before if you do the same info should be found there I expect).
Normally if you just run rclone as a program in CMD or in your case terminal - then the log of what is happening will be displayed right in that window, which may be useful for real-time diagnosing an issue.
However, since you are running this as a service this window is effectively hidden from you as a bacground task. This means to see the log you will need to direct it to a file. You could just pipe the output like you probably have done in other commandline apps - but it is much easier to use the native rclone means to create a log.
Just add this to your config: --log-file "pathy/to/a/folder/rclonelog.txt"
You can then just read this to see output (you can open it while it is running, just don't save the file). Any important errors like 403 will show up even with a low-verbosity level like INFO that you use.
My best guess for what is going wrong is that you have too aggressive Plex scans enabled on auto.
Plex was designed to access local disks or network storage, not a mounted cloud-drive, so some of it's scanning types can be very agressive - reading loads of data and querying files very often to gather things like metadata, previews ect. While this is not such a big deal on local storage it can certainly be a problem on a cloud-based system since you obviously have much less transfer speed to it + also API restrictions (1000 requests pr 100 seconds). If Plex decides it wants to read all of your files 100% to generate previews in an advanced scan that could literally result in your entire archive being read via the internet - which would probably not be what you want.
The solution is usually that you disable the most agressive scanning options that can not do it's just jus based on the file-attributes from the listing it gets (and thus needs to actually access each file in sequence). Such scans should only be performed manually, and sparingly - in a "downtime" period when nothing else is going on.
If you can find the spesific error type (you will want to look/search for 403 in the log) I can say a little more about the spesific error. There are several type of 403 errors however. Be sure to paste the full error line including the text-description.
Yes, but obvious this was just an example and you need to change the path here to something that makes sense for you. Your part should probably look something close to this users/Alora/rclone/rclonelogs.txt
But obviously don't just copy/paste this blindly either. I assume you have to know how folders work on your system - otherwise it will be very difficult to help you
Guys, it has nothing to do with rclone or Gdrive limits. TheTVDB has been having issues once again. I've been dealing with it all day, on and off. That explains why the movies scanned just fine, but not the shows. When this happens, and it does happen frequently, all you can do is wait until TheTVDB fixes their server issues, and then scan again or refresh metadata in Plex.
Ok, thanks for the info.
It sounds like maybe the OP should just wait a little bit and see if the problem resolves itself then - and maybe check reddit for the ongoing status. It would be nice if we had a way to confirm this was the problem - but I am not sure how you might test this in Plex.
One way to test this outside of Plex is to use something like FileBot, which uses TVDB's API. I can confirm that nothing can be pulled from it at the moment.
