Rclone.conf file overwritten/corrupted

Help and Support
1

What is the problem you are having with rclone?

I have setup rclone to copy local files periodically to 2 separate remote
google drives a few months ago. After the setup and making sure it was
working as intended (Copy files to Google Drive) after a few days I left it
alone to continuously copy files to Google Drive.

However, last week I noticed that no more files have being copied to Google
Drive for a few weeks and when I checked the rclone.conf file, all my
settings/client IDs/secrets/etc were gone.

Luckily I had a backup of the rclone.conf file and just copied it to the relevant
./config/rclone directory and everything worked again. Up until now, everything
is still working fine.

I've been trying to find out what caused the rclone.conf file to become
overwritten/corrupted and prevent it from happening again. I've read on some forums
that Google Drive tokens can expire and needs to be refreshed if not verified. Since
this is a small personal project, the authentication token isn't verified.

Is this the reason that the rclone.conf file got overwritten?
If yes, how come the exact same rclone.conf file can still work for a week with no problems?
If not, what could be causing the rclone.conf file to be overwritten?
Is there no backup .conf file I can setup to prevent this from happening again?

What is your rclone version (output from rclone version)

rclone v1.45

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Debian Buster IoT 10.3

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)

Paste command here

The rclone config contents with secrets removed.

[remote_1]
type = drive
client_id = XXX.apps.googleusercontent.com
client_secret = XXX
scope = drive
token = {"access_token":"XXX"}

[remote_2]
type = drive
client_id = XXX.apps.googleusercontent.com
client_secret = XXX
scope = drive
token = {"access_token":"XXX"}

A log from the command with the -vv flag

Did not create a log file
2

hello and welcome to the forum,

that version of rclone in many years old, it could/does have many bugs that have since been fixed.
you can update here

if there was a debug log for each run of rclone, you can look thru the logs.
if a token expires, rclone renews it. that can be seen in the rclone log file.

each user has their own config file.
so if you run rclone as a different user for the first time, rclone creates a new config file fo that user.
i would search the computer for all rclone.conf files.

3

Thank you for the response.

So this is an issue with the older version of rclone?

Will update rclone and setup rclone log file and test it out.

Thanks

4

no way to know as the the problem started in the past and when unnoticed for a period of time.

5

The candidates are

  • disk full on writing the file
  • fs corruption on power cycle

More modern rclone's try much harder to make sure the config file isn't ever corrupted.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.