rclone[27561]: Failed to set permissions on config file: chmod /root/config/.rclone.conf2795095508: no such file or directory
every hour. Apart from that everything seems to work. It started after upgrading to FreeBSD 13.1. It is quite consistent app. 15 minutes after the hour. The PID corresponds to an overrunning rclone mount (same happens with cmount).
Run the command 'rclone version' and share the full output of the command.
Happened with 1.59.0 and now with this as well:
os/version: freebsd 13.1-release-p1 (64 bit)
os/kernel: 13.1-release-p1 (amd64)
os/type: freebsd
os/arch: amd64
go/version: go1.19
go/linking: dynamic
go/tags: cmount
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)
gdrive tokens expire after one hour.
when that happens, rclone requests a new token from gdrive.
now rclone has to save that token in the config file.
as i understand it, rclone
--- copies the rclone.conf to a temp config file with a random name.
--- writes that token to the temp config file.
--- renames the temp config file back to rclone.conf
so it could be a simple file/dir permissions issue.
which type of user is running rclone mount, root or non-root?
rclone mount runs as root. And the strange thing is: Nothing on the setup changed. No permissions I am aware of. No other user running. Only a FreeBSD upgrade. The contents of rclone.conf seems to change (and the new tokens are written to the file). Will verify this though. Should happen again in appr. 20 minutes.
So there seems to be no functional impact. But the error messages are "new".
If it is a permissions error: Why is the new token successfully written to the rclone.conf?
verified. The token was just updated successfully (as expected).
Just looked at the source code. The 1 Mio $ question then is: Why does the chmod fail for the process even though it is running as root?
It is trying a chmod 0600 (which is what the file permissions are at). The directory settings are "drwxr-xr-x". And again: root should be able to chmod all the time. A manual "chmod 0600 .rclone.conf" also produces no error. Only thing I can think of is that the config file is within an encrypted filesystem (PEFS) which is mounted. But once more: All of this did not change in the past year. Maybe FreeBSD 13.1 introduced "something new" here which throws an error.
However: The error states "no such file or directory". So the question is: Why is the temp file not there?