Giving start request repeated too quickly

What is the problem you are having with rclone?

I am trying to create a service for mounting gdrive, but the script is failing wth start request repeated too quickly. Simply using

rclone mount ebooks: /mnt/Media/books

works fine

What is your rclone version (output from rclone version)


Which OS you are using and how many bits (eg Windows 7, 64 bit)


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)



ExecStart=/usr/bin/rclone mount ebooks: /mnt/Media/books \
--allow-other \
--cache-dir /data/rclone \
--vfs-cache-mode writes \
--dir-cache-time 96h \
--log-level INFO \
--log-file /opt/rclone/logs/rclone.log \
--timeout 1h \
--umask 002 \
ExecStop=/bin/fusermount -u /mnt/Media/books


The rclone config contents with secrets removed.

Paste config here

A log from the command with the -vv flag

Paste  log here

I would guess it's because you have restart on failure, but with no logs from systemd or rclone, it's tough to validate.

If you can share logs, I'm sure we can figure it out.

/opt/rclone/logs/rclone.log would probably tell you why rclone is failing

journalctl -u rclone -b

would probably tell what systemd thinks.

logs show that the folder does not exist,. and journalctl -u rclone -b shows no entries

I just realized I forgot to create the logs folder in the new server. since I copied it from my previous server. sry about that

No problem. I always find the best way to fix something tends to be explaining it and I usually find my own answer :slight_smile:

Happy you got it working!

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