It does not output anything in the log. This appears when starting rclone.
Job for rclone-vfs.service failed because a timeout was exceeded.
See "systemctl --user status rclone-vfs.service" and "journalctl --user -xe" for details.
Ah, darn. I exited the terminal that had that information. I don't have that at the moment as the new current config works (very different config). I'll test the old config soon. In the meantime, I do have this to share. When running systemctl status on rclone previously it seemed to be stuck on starting/activating. ps aux | grep rclone would show it as active as well.
● rclone-vfs.service - RClone VFS Service
Loaded: loaded (/home/redacted/.config/systemd/user/rclone-vfs.service; enabled; vendor preset: enabled)
Active: activating (start) since Thu 2023-03-09 21:59:20 CET; 38s ago
Main PID: 89673 (rclone)
CGroup: /user.slice/user-1038.slice/user@1038.service/rclone-vfs.service
└─89673 /home/redacted/bin/rclone mount gdrive: /home/redacted/gdrive --config /home/redacted/.config/rclone/rclone.conf --use-mmap --allow-other --buffer-size 256M --drive-chunk-size 128M --dir-cache-t
Mar 09 21:59:20 pollux systemd[128020]: Starting RClone VFS Service...
i would take the working config, add one or two flags at a time and see when the problem re-occurs.
that way might figure out which flag(s) is the issue.
what do you do with the rclone mount? stream from plex or what?
not sure these are needed or need to be set to such high values, as most configs do not use them.
what do you do with the rclone mount? stream from plex or what?
Yeah, Plex.
not sure these are needed or need to be set to such high values, as most configs do not use them.
I tried to cache as much as possible to prevent Google from kicking us off for daily limits. Not sure if it made sense though. I have a large library being shared among family + friends.