New Google Drive config file appearing

What is the problem you are having with rclone?

No problems. I'm just wondering about a newly appearing config file, which has the name of example.conf947971726. It's the same config as I specify, but with different token.

Why is it created and what happens when in subsequent runs I still refer to the original config. I haven't seen anything like this documented in the docs.

Run the command 'rclone version' and share the full output of the command.

rclone v1.64.2

  • os/version: unknown
  • os/kernel: 3.10.105 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.21.3
  • go/linking: static
  • go/tags: none

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)

export RCLONE_CONFIG=example.conf
rclone sync ...

Any ideas for this one? Is it a bug, or a normal behaviour? In the days since, no new config files appeared, except the example.conf947971726 which was created on the first day.

That could happen if permissions were odd or something.

Rclone creates. temp conf file when it rewrites/updates it.

You'd see something like this if it works

2023/11/01 10:26:48 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "about" "DB:" "-vv"]
2023/11/01 10:26:48 DEBUG : Creating backend with remote "DB:"
2023/11/01 10:26:48 DEBUG : Using config file from "/Users/etexter/.config/rclone/rclone.conf"
2023/11/01 10:26:48 DEBUG : DB: Loaded invalid token from config file - ignoring
2023/11/01 10:26:48 DEBUG : Saving config "token" in section "DB" of the config file
2023/11/01 10:26:48 DEBUG : Keeping previous permissions for config file: -rw-r--r--
2023/11/01 10:26:48 DEBUG : DB: Saved new token in config file

I see, so maybe I just terminated it with Ctrl+C exactly when this temporary file was present. I'll just delete the file then.

How about the token's lifetime? Do I understand it right that I need to run it at least once per week so that the token doesn't expire? It'll be running in an overnight cronjob on a server, will it work like this or I should better migrate to using service account jsons?

I haven't used Google in like a month:

"expiry":"2023-11-01T14:26:48.225485-04:00"}

A token will refresh as I'm not sure on Google but I think 30 days maybe. I don't recall offhand.

2023/11/01 10:56:13 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "about" "GD:" "-vv"]
2023/11/01 10:56:13 DEBUG : Creating backend with remote "GD:"
2023/11/01 10:56:13 DEBUG : Using config file from "/Users/etexter/.config/rclone/rclone.conf"
2023/11/01 10:56:13 DEBUG : GD: Loaded invalid token from config file - ignoring
2023/11/01 10:56:13 DEBUG : Saving config "token" in section "GD" of the config file
2023/11/01 10:56:13 DEBUG : Keeping previous permissions for config file: -rw-r--r--
2023/11/01 10:56:13 DEBUG : GD: Saved new token in config file
Total:   16 GiB
Used:    1.863 GiB
Free:    10.384 GiB
Trashed: 1.068 KiB
Other:   3.753 GiB
2023/11/01 10:56:13 DEBUG : 9 go routines active

Mine refreshed from a month back.

OK, so an overnight sync job should take care of refreshing the token all the time. Good to know.

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