Systemd rclone mount fail at boot (Google Drive)

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.

Can you include the .service file?

The .service file is a copy and paste from the template on Wiki (sorry I cannot insert the full URL github/rclone/rclone/wiki/Systemd-rclone-mount#systemd), without changes:

[mru@Pine64Pro user]$ pwd
/etc/systemd/user
[mru@Pine64Pro user]$ cat rclone\@.service 
[Unit]
Description=RClone mount of users remote %i using filesystem permissions
Documentation=http://rclone.org/docs/
After=network-online.target


[Service]
Type=notify
#Set up environment
Environment=REMOTE_NAME="%i"
Environment=REMOTE_PATH="/"
Environment=MOUNT_DIR="%h/%i"
Environment=RCLONE_CONF="%h/.config/rclone/rclone.conf"
Environment=RCLONE_TEMP_DIR="/tmp/rclone/%u/%i"

#Default arguments for rclone mount. Can be overridden in the environment file
Environment=RCLONE_MOUNT_ATTR_TIMEOUT="1s"
#TODO: figure out default for the following parameter
Environment=RCLONE_MOUNT_DAEMON_TIMEOUT="UNKNOWN_DEFAULT"
Environment=RCLONE_MOUNT_DIR_CACHE_TIME="60m"
Environment=RCLONE_MOUNT_DIR_PERMS="0777"
Environment=RCLONE_MOUNT_FILE_PERMS="0666"
Environment=RCLONE_MOUNT_GID="%G"
Environment=RCLONE_MOUNT_MAX_READ_AHEAD="128k"
Environment=RCLONE_MOUNT_POLL_INTERVAL="1m0s"
Environment=RCLONE_MOUNT_UID="%U"
Environment=RCLONE_MOUNT_UMASK="022"
Environment=RCLONE_MOUNT_VFS_CACHE_MAX_AGE="1h0m0s"
Environment=RCLONE_MOUNT_VFS_CACHE_MAX_SIZE="off"
Environment=RCLONE_MOUNT_VFS_CACHE_MODE="off"
Environment=RCLONE_MOUNT_VFS_CACHE_POLL_INTERVAL="1m0s"
Environment=RCLONE_MOUNT_VFS_READ_CHUNK_SIZE="128M"
Environment=RCLONE_MOUNT_VFS_READ_CHUNK_SIZE_LIMIT="off"
#TODO: figure out default for the following parameter
Environment=RCLONE_MOUNT_VOLNAME="UNKNOWN_DEFAULT"

#Overwrite default environment settings with settings from the file if present
EnvironmentFile=-%h/.config/rclone/%i.env

#Check that rclone is installed
ExecStartPre=/usr/bin/test -x /usr/bin/rclone

#Check the mount directory
ExecStartPre=/usr/bin/test -d "${MOUNT_DIR}"
ExecStartPre=/usr/bin/test -w "${MOUNT_DIR}"
#TODO: Add test for MOUNT_DIR being empty

#Check the rclone configuration file
ExecStartPre=/usr/bin/test -f "${RCLONE_CONF}"
ExecStartPre=/usr/bin/test -r "${RCLONE_CONF}"
#TODO: add test that the remote is configured for the rclone configuration

#Mount rclone fs
ExecStart=/usr/bin/rclone mount \
            --config="${RCLONE_CONF}" \
#See additional items for access control below for information about the following 2 flags
#            --allow-other \
#            --default-permissions \
            --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}/vfs" \
            --cache-db-path="${RCLONE_TEMP_DIR}/db" \
            --no-modtime \
            --drive-use-trash \
            --stats=0 \
            --checkers=16 \
            --bwlimit=40M \
            --cache-info-age=60m \
            --attr-timeout="${RCLONE_MOUNT_ATTR_TIMEOUT}" \
#TODO: Include this once a proper default value is determined
#           --daemon-timeout="${RCLONE_MOUNT_DAEMON_TIMEOUT}" \
            --dir-cache-time="${RCLONE_MOUNT_DIR_CACHE_TIME}" \
            --dir-perms="${RCLONE_MOUNT_DIR_PERMS}" \
            --file-perms="${RCLONE_MOUNT_FILE_PERMS}" \
            --gid="${RCLONE_MOUNT_GID}" \
            --max-read-ahead="${RCLONE_MOUNT_MAX_READ_AHEAD}" \
            --poll-interval="${RCLONE_MOUNT_POLL_INTERVAL}" \
            --uid="${RCLONE_MOUNT_UID}" \
            --umask="${RCLONE_MOUNT_UMASK}" \
            --vfs-cache-max-age="${RCLONE_MOUNT_VFS_CACHE_MAX_AGE}" \
            --vfs-cache-max-size="${RCLONE_MOUNT_VFS_CACHE_MAX_SIZE}" \
            --vfs-cache-mode="${RCLONE_MOUNT_VFS_CACHE_MODE}" \
            --vfs-cache-poll-interval="${RCLONE_MOUNT_VFS_CACHE_POLL_INTERVAL}" \
            --vfs-read-chunk-size="${RCLONE_MOUNT_VFS_READ_CHUNK_SIZE}" \
            --vfs-read-chunk-size-limit="${RCLONE_MOUNT_VFS_READ_CHUNK_SIZE_LIMIT}" \
#TODO: Include this once a proper default value is determined
#            --volname="${RCLONE_MOUNT_VOLNAME}"
            "${REMOTE_NAME}:${REMOTE_PATH}" "${MOUNT_DIR}"

#Unmount rclone fs
ExecStop=/bin/fusermount -u "${MOUNT_DIR}"

#Restart info
Restart=on-success
RestartSec=10

[Install]
WantedBy=default.target


Thanks for the fast feedback!

That's by far one of the most complex systemd I've ever seen in my life and it's got a bunch of things that aren't relevant or used anymore :frowning:

I'd probably scrap that and start with something simple and small.

Try something like this instead and let's get a base going.

felix@gemini:/etc/systemd/system$ cat rclone.service
[Unit]
Description=RClone Service
After=network-online.target

[Service]
Type=notify
KillMode=none
RestartSec=5
ExecStart=/usr/bin/rclone mount YOURREMOTENAME: /YOURMOUNTHERE \
--allow-other \
--dir-cache-time 1000h
ExecStop=/bin/fusermount -uz /YOURMOUNTHERE
Restart=on-failure
User=yourusername
Group=yourgroupname

[Install]
WantedBy=multi-user.target

Hello,
unfortunately stil not work!

During the manual start I receive this error:

[mru@Pine64Pro ~]$ systemctl --user status rclone@GDrive
● rclone@GDrive.service - RClone Service
     Loaded: loaded (/etc/xdg/systemd/user/rclone@.service; disabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Tue 2020-10-13 21:51:43 CEST; 4s ago
    Process: 7294 ExecStart=/usr/bin/rclone mount GDrive: /home/mru/GDrive --allow-other --dir-cache-time 1000h (code=exited, status=216/GROUP)
   Main PID: 7294 (code=exited, status=216/GROUP)

I tried with all the groups that belong to my user (mru), and after any change on service file I reloaded the daemon:

systemctl --user daemon-reload

But without success (manually or at the boot)

I tried also to specify root user and group root, but I retrieve always the same error

Can you post the updates service file you made and the journalctl output for the service as that should show what the issue that it is failing?

Sure, here my service file:

[mru@Pine64Pro ~]$ cat /etc/systemd/user/rclone@.service
[Unit]
Description=RClone Service
After=network-online.target

[Service]
Type=notify
KillMode=none
RestartSec=5
ExecStart=/usr/bin/rclone mount GDrive: /home/mru/GDrive \
--allow-other \
--dir-cache-time 1000h
ExecStop=/bin/fusermount -uz /home/mru/Gdrive
Restart=on-failure
User=mru
Group=mru

[Install]
WantedBy=multi-user.target

Here the journactl output:

[mru@Pine64Pro ~]$ journalctl --user -xe
-- 
-- The job identifier is 122 and the job result is failed.
Oct 13 22:29:33 Pine64Pro systemd[1059]: rclone@GDrive.service: Scheduled restart job, restart counter is at 8.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 13 22:29:33 Pine64Pro systemd[1059]: Stopped RClone Service.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 132 and the job result is done.
Oct 13 22:29:33 Pine64Pro systemd[1059]: Starting RClone Service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 132.
Oct 13 22:29:33 Pine64Pro systemd[1456]: rclone@GDrive.service: Failed to determine supplementary groups: Operation not permitted
Oct 13 22:29:33 Pine64Pro systemd[1456]: rclone@GDrive.service: Failed at step GROUP spawning /usr/bin/rclone: Operation not permitted
-- Subject: Process /usr/bin/rclone could not be executed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /usr/bin/rclone could not be executed and failed.
-- 
-- The error number returned by this process is ERRNO.
Oct 13 22:29:33 Pine64Pro systemd[1059]: rclone@GDrive.service: Main process exited, code=exited, status=216/GROUP
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit UNIT has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 216.
Oct 13 22:29:33 Pine64Pro systemd[1059]: rclone@GDrive.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Oct 13 22:29:33 Pine64Pro systemd[1059]: Failed to start RClone Service.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished with a failure.
-- 
-- The job identifier is 132 and the job result is failed.

Looks like you have a bad user name and group?

I tried to remove from the service file that you suggested me the row "User" and "Group"

Now the job start manually and also at the boot! :slight_smile:

But I still have a small issue: when I start manually I don't have error

[mru@Pine64Pro ~]$ systemctl --user status rclone@GDrive
* rclone@GDrive.service - RClone Service
     Loaded: loaded (/etc/xdg/systemd/user/rclone@.service; disabled; vendor preset: enabled)
     Active: active (running) since Wed 2020-10-14 22:18:36 CEST; 15s ago
   Main PID: 7269 (rclone)
     CGroup: /user.slice/user-1000.slice/user@1000.service/rclone.slice/rclone@GDrive.service
             `-7269 /usr/bin/rclone mount GDrive: /home/mru/GDrive --allow-other --dir-cache-time 1000h

Oct 14 22:18:34 Pine64Pro systemd[1013]: Starting RClone Service...
Oct 14 22:18:36 Pine64Pro systemd[1013]: Started RClone Service.
[mru@Pine64Pro ~]$ journalctl --user -xe                
-- 
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Oct 14 22:18:29 Pine64Pro systemd[1013]: Failed to start RClone Service.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished with a failure.
-- 
-- The job identifier is 2509 and the job result is failed.
Oct 14 22:18:32 Pine64Pro systemd[1013]: Reloading.
Oct 14 22:18:33 Pine64Pro systemd[7247]: Configuration file /etc/xdg/autostart/klipper.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-powerdevil-autostart.service, only Type=Application is supported.
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported.
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are not supported.
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported.
Oct 14 22:18:33 Pine64Pro systemd[7247]: kde-systemd-start-condition not found: No such file or directory
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported.
Oct 14 22:18:33 Pine64Pro systemd[7247]: kde-systemd-start-condition not found: No such file or directory
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-kaccess-autostart.service, only Type=Application is supported.
Oct 14 22:18:33 Pine64Pro systemd[7247]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported.
Oct 14 22:18:33 Pine64Pro systemd[1013]: Configuration file /etc/xdg/systemd/user/rclone@.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 14 22:18:33 Pine64Pro systemd[1013]: /etc/xdg/systemd/user/rclone@.service:7: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service t>
Oct 14 22:18:34 Pine64Pro systemd[1013]: rclone@GDrive.service: Scheduled restart job, restart counter is at 243.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 14 22:18:34 Pine64Pro systemd[1013]: Stopped RClone Service.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 2519 and the job result is done.
Oct 14 22:18:34 Pine64Pro systemd[1013]: Starting RClone Service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 2519.
Oct 14 22:18:36 Pine64Pro systemd[1013]: Started RClone Service.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 2519.
Oct 14 22:18:51 Pine64Pro systemd[1013]: Configuration file /etc/xdg/systemd/user/rclone@.service is marked executable. Please remove executable permission bits. Proceeding anyway.
lines 6524-6578/6578 (END)

But then, when I execute the boot and I check the output of journal or the status of service I have some errors on docx or xlsx files:

[mru@Pine64Pro ~]$ systemctl --user status rclone@GDrive
* rclone@GDrive.service - RClone Service
     Loaded: loaded (/etc/xdg/systemd/user/rclone@.service; disabled; vendor preset: enabled)
     Active: active (running) since Wed 2020-10-14 22:24:12 CEST; 28s ago
   Main PID: 1312 (rclone)
     CGroup: /user.slice/user-1000.slice/user@1000.service/rclone.slice/rclone@GDrive.service
             `-1312 /usr/bin/rclone mount GDrive: /home/mru/GDrive --allow-other --dir-cache-time 1000h

Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 3/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 4/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 5/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 6/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 7/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 8/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 9/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: low level retry 10/10: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Read error: partial downloads are not supported while exporting Google Documents
Oct 14 22:24:40 Pine64Pro rclone[1312]: 2020/10/14 22:24:40 ERROR : Lavoro/Riepilogo offerte di lavoro.xlsx: ReadFileHandle.Release error: file already closed

I will avoid to paste the output from journal since is longer (and just contains a list of more files).

I will try to search a way for fix it, in the meantime I have a question: would not be better enable also the option

-vfs-cache-mode

To write? Or for beginners is not recommended?

And why you suggest a so long dir-cache-time? (1000h)

Thanks for the help!

Another small issue, I cannot stop the service:

ct 14 23:07:30 Pine64Pro systemd[1025]: Stopping RClone Service...
-- Subject: A stop job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has begun execution.
-- 
-- The job identifier is 119.
Oct 14 23:07:30 Pine64Pro fusermount[11593]: /bin/fusermount: entry for /home/mru/Gdrive not found in /etc/mtab
Oct 14 23:07:30 Pine64Pro systemd[1025]: rclone@GDrive.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStop= process belonging to unit UNIT has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Oct 14 23:07:30 Pine64Pro systemd[1025]: rclone@GDrive.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Oct 14 23:07:30 Pine64Pro systemd[1025]: rclone@GDrive.service: Unit process 1312 (rclone) remains running after unit stopped.
Oct 14 23:07:30 Pine64Pro systemd[1025]: Stopped RClone Service.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 119 and the job result is done.
Oct 14 23:07:37 Pine64Pro kdeinit5[9547]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:38 Pine64Pro kdeinit5[11617]: Qt: Session management error: networkIdsList argument is NULL
Oct 14 23:07:38 Pine64Pro kdeinit5[11616]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:38 Pine64Pro kdeinit5[11616]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:38 Pine64Pro kwin_x11[1118]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6187, resource id: 48234507, major code: 18 (ChangeProperty), minor code: 0
Oct 14 23:07:39 Pine64Pro kdeinit5[9547]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:39 Pine64Pro kdeinit5[11642]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:39 Pine64Pro kdeinit5[9547]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:39 Pine64Pro kdeinit5[11616]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:40 Pine64Pro kdeinit5[9547]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:40 Pine64Pro kdeinit5[11642]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:40 Pine64Pro kdeinit5[11616]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:41 Pine64Pro kdeinit5[9547]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_file" KIO slave
Oct 14 23:07:41 Pine64Pro kdeinit5[11658]: Qt: Session management error: networkIdsList argument is NULL
lines 1656-1711/1711 (EN

Then in using

fusermount -uz /home/mru/GDrive/

Everything goes fine:

Oct 14 23:11:02 Pine64Pro systemd[1025]: home-mru-GDrive.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--  
-- The unit UNIT has successfully entered the 'dead' state.