How to generate log file for rclone?

I have mounted my google drive and I want to get a log file to get help with something but I don't know how to generate it. I don't know much about command line so if anyone could share command with me?

Thanks.

This is all in the docs (rclone.org) but since I'm so nice I will handhold you a little :wink:

--log-file=mylogfile.txt
(I think you can also just write that as --log-file mylogfile.txt if you prefer)
--log-level INFO

from least verbose to most: ERROR or NOTICE or INFO or DEBUG (default, NOTICE, is usually sufficient)
see documentaion for more info : https://rclone.org/docs/#log-level-level

2 Likes

Hi, mylogfile.txt worked and when i enter the second one as

rclone --log-level INFO

i get following error

Usage:
rclone [flags]
rclone [command]

Available Commands:
about Get quota information from the remote.
authorize Remote authorization.
cachestats Print cache stats for a remote
cat Concatenates any files and sends them to stdout.
check Checks the files in the source and destination match.
cleanup Clean up the remote if possible
config Enter an interactive configuration session.
copy Copy files from source to dest, skipping already copied
copyto Copy files from source to dest, skipping already copied
copyurl Copy url content to dest.
cryptcheck Cryptcheck checks the integrity of a crypted remote.
cryptdecode Cryptdecode returns unencrypted file names.
dbhashsum Produces a Dropbox hash file for all the objects in the path.
dedupe Interactively find duplicate files and delete/rename them.
delete Remove the contents of path.
deletefile Remove a single file from remote.
genautocomplete Output completion script for a given shell.
gendocs Output markdown docs for rclone to the directory supplied.
hashsum Produces an hashsum file for all the objects in the path.
help Show help for rclone commands, flags and backends.
link Generate public link to file/folder.
listremotes List all the remotes in the config file.
ls List the objects in the path with size and path.
lsd List all directories/containers/buckets in the path.
lsf List directories and objects in remote:path formatted for parsing
lsjson List directories and objects in the path in JSON format.
lsl List the objects in path with modification time, size and path.
md5sum Produces an md5sum file for all the objects in the path.
mkdir Make the path if it doesn't already exist.
mount Mount the remote as file system on a mountpoint.
move Move files from source to dest.
moveto Move file or directory from source to dest.
ncdu Explore a remote with a text based user interface.
obscure Obscure password for use in the rclone.conf
purge Remove the path and all of its contents.
rc Run a command against a running rclone.
rcat Copies standard input to file on remote.
rcd Run rclone listening to remote control commands only.
rmdir Remove the path if empty.
rmdirs Remove empty directories under the path.
serve Serve a remote over a protocol.
settier Changes storage class/tier of objects in remote.
sha1sum Produces an sha1sum file for all the objects in the path.
size Prints the total size and number of objects in remote:path.
sync Make source and dest identical, modifying destination only.
touch Create new file or change file modification time.
tree List the contents of the remote in a tree like fashion.
version Show the version number.

Use "rclone [command] --help" for more information about a command.
Use "rclone help flags" for to see the global flags.
Use "rclone help backends" for a list of supported services.

and this above report has been saved in mylogfile.txt file as well.

You have to do something with rclone, ie. connect to backend and list directory, copy files, etc. – not just specify a log file.

So in your case add the logfile option to the mounting command.

Right... The idea is you just add this flag to the others you already use in your mount command.
rclone is confused by the fact that you only gave it options and no actual commands - thus it gave you a list of all the commands in return. It's a bit like going into the restaurant and ordering a "well done" and an "extra sweet" for desert :wink:

Oh, and i believe Animosity asked for a DEBUG log. Notice is just the default and what is typically ok for daily logs.

yes he asked for a debug file so is that different from log file? i tried running some commands yesterday but it didn't work.

By "debug file" he just means a log-file - but using --log-level DEBUG
You can get debug-output by using nothing more than -vv
but then all the info will get dumped to your screen, and debug-logs are far too spammy for that to be practical in most cases, so it is best to dump that info to a file. Do note that when you enable a log-file then you do no longer get info on your screen. That is normal - all that info goes into the file instead.

here is a concrete example of usage:
Let's say I have a google drive I mount like this:
rclone mount MyGoogleDrive: X:
I want to enable DEBUG-level logging to it, so I add these two flags to the command:
rclone mount MyGoogleDrive: X: --log-file=C:\logs\rclonemount.txt --log-level DEBUG

This is example is based on windows folder structure. If you are on Linux your paths will be slightly different, like for example /mnt/gdrive and maybe /home/rclone/mountlog.txt .

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