What is the problem you are having with rclone?
Hello all,
I followed the guide in the wiki on Github (trying both approaches, for all users or single user): rclone/wiki/Systemd-rclone-mount#systemd
But after the boot, the mount does not work due to this error:
[mru@Pine64Pro ~]$ systemctl --user status rclone@GDrive
● rclone@GDrive.service - RClone mount of users remote GDrive using filesystem permissions
Loaded: loaded (/etc/xdg/systemd/user/rclone@.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-10-12 22:03:14 CEST; 45s ago
Docs: http://rclone.org/docs/
Process: 1045 ExecStartPre=/usr/bin/test -x /usr/bin/rclone (code=exited, status=0/SUCCESS)
Process: 1047 ExecStartPre=/usr/bin/test -d ${MOUNT_DIR} (code=exited, status=0/SUCCESS)
Process: 1048 ExecStartPre=/usr/bin/test -w ${MOUNT_DIR} (code=exited, status=0/SUCCESS)
Process: 1049 ExecStartPre=/usr/bin/test -f ${RCLONE_CONF} (code=exited, status=0/SUCCESS)
Process: 1050 ExecStartPre=/usr/bin/test -r ${RCLONE_CONF} (code=exited, status=0/SUCCESS)
Process: 1052 ExecStart=/usr/bin/rclone mount --config=${RCLONE_CONF} --cache-tmp-upload-path=${RCLONE_TEMP_DIR}/upload --cache-chunk-path=${RCLONE_TEMP_DIR}/chunks --cache-workers=8 --cache-writes --cache-dir=${RCLONE_TEMP_DIR}/vf>
Main PID: 1052 (code=exited, status=1/FAILURE)
ott 12 22:03:09 Pine64Pro systemd[1037]: Starting RClone mount of users remote GDrive using filesystem permissions...
ott 12 22:03:14 Pine64Pro rclone[1052]: 2020/10/12 22:03:14 Failed to create file system for "GDrive:/": couldn't find root directory ID: Get "https://www.googleapis.com/drive/v3/files/root?alt=json&fields=id&prettyPrint=false&supports>
ott 12 22:03:14 Pine64Pro systemd[1037]: rclone@GDrive.service: Main process exited, code=exited, status=1/FAILURE
ott 12 22:03:14 Pine64Pro systemd[1037]: rclone@GDrive.service: Failed with result 'exit-code'.
ott 12 22:03:14 Pine64Pro systemd[1037]: Failed to start RClone mount of users remote GDrive using filesystem permissions.
Everything goes fine when I start it manually:
[mru@Pine64Pro ~]$ systemctl --user status rclone@GDrive
● rclone@GDrive.service - RClone mount of users remote GDrive using filesystem permissions
Loaded: loaded (/etc/xdg/systemd/user/rclone@.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2020-10-12 22:07:27 CEST; 3s ago
Docs: http://rclone.org/docs/
Process: 1880 ExecStartPre=/usr/bin/test -x /usr/bin/rclone (code=exited, status=0/SUCCESS)
Process: 1881 ExecStartPre=/usr/bin/test -d ${MOUNT_DIR} (code=exited, status=0/SUCCESS)
Process: 1882 ExecStartPre=/usr/bin/test -w ${MOUNT_DIR} (code=exited, status=0/SUCCESS)
Process: 1883 ExecStartPre=/usr/bin/test -f ${RCLONE_CONF} (code=exited, status=0/SUCCESS)
Process: 1884 ExecStartPre=/usr/bin/test -r ${RCLONE_CONF} (code=exited, status=0/SUCCESS)
Main PID: 1885 (rclone)
CGroup: /user.slice/user-1000.slice/user@1000.service/rclone.slice/rclone@GDrive.service
└─1885 /usr/bin/rclone mount --config=/home/mru/.config/rclone/rclone.conf --cache-tmp-upload-path=/tmp/rclone/mru/GDrive/upload --cache-chunk-path=/tmp/rclone/mru/GDrive/chunks --cache-workers=8 --cache-writes --cache-dir>
ott 12 22:07:26 Pine64Pro systemd[1037]: Starting RClone mount of users remote GDrive using filesystem permissions...
ott 12 22:07:27 Pine64Pro systemd[1037]: Started RClone mount of users remote GDrive using filesystem permissions.
What is your rclone version (output from rclone version)
[mru@Pine64Pro ~]$ rclone version
rclone v1.53.1
- os/arch: linux/arm64
- go version: go1.15.2
Which OS you are using and how many bits (eg Windows 7, 64 bit)
OS: Manjaro ARM Linux aarch64
Host: Pine64 Pinebook Pro
Kernel: 5.7.19-1-MANJARO-ARM
Which cloud storage system are you using? (eg Google Drive)
Google Drive
The rclone config contents with secrets removed.
mru@Pine64Pro ~]$ cat /home/mru/.config/rclone/rclone.conf
[GDrive]
type = drive
scope = drive
token = {
Searching on the forum, I saw this hint: clone-mount-systemd/13268
Then I changed the /etc/fuse.conf file, removed the comment from row user_allow_other, and reload systemd configuration.
But at the boot I have the same error.
