Derailed topic that turned into GDrive API errors - ON HOLD but likely resolved

The cache is not used on my upload box, only on my plex box and the automation box that provides the directory structure of empty files to the upload box

These are my graphs for the last 4 days:

Where are you pulling up errors by credential?

all I see is this

It shows up for me in

https://console.developers.google.com/apis/api/drive.googleapis.com/metrics

I had not found that page. It’s not directly linked from where I was at I guess. Thank you.

Also I’m going to try the suggestions for removing cache and going to VFS. Thank hell all my service and config files are git managed.

omg I just never clicked Google Drive in the api list.

I feel so effin retarded atm.

haha, yep find stuff in google’s console is sometimes a little how shall we say challenging :slight_smile:

2 Likes

How do you think I feel. I actually used VFS mode before I switched down a different path. :rofl:

1 Like

I’ll try to put all my changes in tonight. I’ll report back here how it goes, and if it’s all successful I’m going to make a public git repo and share it here for others to find the files (and make suggestions of changes if they know how to use git)

Well I just went from Plex analyzing new files at approximately 6 episodes a minute to around 40-50 a minute.

holy crap

Yep I’m going to institute these changes across the board, initiate a bunch of git pulls and some reboots and see what happens. I’ll report back when I’ve completed and analyzed.

1 Like

One other thing I would add.

I did find that after the initial mount of the drive, the first scan could be a bit slow

So I enable rc on my mounts like this e.g:

--rc --rc-addr=10.0.0.31:5583

or

--rc --rc-addr=localhost:5583

(if using ip address, change ip address and port to your own details, and you will need to use different ports if you have more than one mount)

and then I run this after the drive has mounted

rclone rc vfs/refresh dir="/plex" recursive=true --rc-addr=10.0.0.31:5583

Seemed to help.

Im definitely not seeing slow scans here. Its Insane. Its just scanned and added metadata for 30 shows of varying sizes in around 10 minutes. Whilst simultaneously analyzing episodes for other shows at around 40-50 episodes a minute.

You solved one thing for me though. I saw --rc in the mount command I snateched from the rclone forums. I didn’t know what it was so I just left it out. :upside_down_face:

all good then :slight_smile:

I was just adding it as a tip just in case… was just something I noticed on mine.

1 Like

No worries Im probably in no way at optimal settings I just tend to follow the lead of a couple of always active guys on the rclone forums.
You on a seedbox or a dedi?

that’ll be at least animosity022 I guess :slight_smile:

I run on both my hetzner dedi (for me and a few friends) and a synology nas at home as a backup for me, as (you probably know based on your name) we have crap upload speeds from home broadband here)

and a separate seedbox for collecting…

[Unit]
Description=rclone-crypt
After=network-online.target rclone-gdrive.service

[Service]
Type=simple
User=root
Group=root
ExecStart=/usr/bin/rclone mount GCrypt: /mnt/GCrypt --allow-other --read-only --buffer-size 256M --dir-cache-time 12h --drive-chunk-size 128M --vfs-read-chunk-size 128M --vfs-read-chunk-size-limit off --use-mmap --fast-list --tpslimit 5
ExecStop=/bin/fusermount -uz /mnt/GCrypt
Restart=always
RestartSec=2

[Install]
WantedBy=multi-user.target

:thinking:

Any comments?