You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The doco suggests: -v '/path/to/rclone.conf':'/config/rclone/rclone.conf' \
I have found that when UPB user does not have write access to the folder containing rclone.conf it sometimes triggers errors like this when it tries to write changes to the conf file:
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:27 DEBUG : Setting --config "/config/rclone/rclone.conf" from environment variable RCLONE_CONFIG="/config/rclone/rclone.conf"
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:27 DEBUG : rclone: Version "v1.58.1-DEV" starting with parameters ["rclone" "delete" "-vv" "Onedrive:/Unifi-Protect-Backup/Front Doorbell/2022-11-29/2022-11-29T11-42-25 ring.mp4"]
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:27 DEBUG : Creating backend with remote "Onedrive:/Unifi-Protect-Backup/Front Doorbell/2022-11-29/2022-11-29T11-42-25 ring.mp4"
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:27 DEBUG : Using config file from "/config/rclone/rclone.conf"
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:27 DEBUG : Onedrive: Loaded invalid token from config file - ignoring
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:27 DEBUG : Saving config "token" in section "Onedrive" of the config file
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:33 ERROR : Failed to save config after 10 tries: Failed to move previous config to backup location: rename /config/rclone/rclone.conf /config/rclone/rclone.conf.old: device or resource busy
2023-07-08T15:13:38.528300383+10:00 stderr F 2023/07/08 05:13:33 DEBUG : Onedrive: Saved new token in config file
So I created a conf subfolder in my upb application folder, alongside the db folder, gave upb user rights to that folder, dropped in rclone.conf to it and set the command as: -v '/opt/upb-docker/conf/':'/config/rclone' \
It seems to be working OK, and no more complaints about not being able to save config.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Sebastian, quick comment on the rclone path...
The doco suggests:
-v '/path/to/rclone.conf':'/config/rclone/rclone.conf' \
I have found that when UPB user does not have write access to the folder containing rclone.conf it sometimes triggers errors like this when it tries to write changes to the conf file:
So I created a conf subfolder in my upb application folder, alongside the db folder, gave upb user rights to that folder, dropped in rclone.conf to it and set the command as:
-v '/opt/upb-docker/conf/':'/config/rclone' \
It seems to be working OK, and no more complaints about not being able to save config.
Beta Was this translation helpful? Give feedback.
All reactions