Access to log files

[nealeydee]

I'm trying to find the Rclone-Manager log files. I am running headless on Debian 12.
What I'm trying to achieve is to get the job staus so I can use the mqtt client to publish a message.

Where on the file system can I find this logging info?

[Hakanbaban53]

Currently, the application does not support file logging. However, I have already implemented this feature in the upcoming v0.2.0 update.

I will ping you here once the new version is released!

[nealeydee]

Thanks - that was quick! I have also noticed that the rclone logging does not seem to work either. (Maybe you are aware ?):

I have enabled this in config - rclone - logging - but it does not seem like the --log-level option is added to the command line. I have selected INFO as the logging level I want, but I am confused by the label:

"WindowsEventLogLevel".

Is there an issue with the headless version that it thinks it's Windows ?

[Hakanbaban53]

I've looked into this further. The settings you see in the UI are fetched directly from the rclone rcd API. It appears that rclone itself does not filter these options based on the operating system, which is why you see all available flags (like WindowsEventLogLevel) regardless of the platform running.

I also verified that the application is correctly sending and applying these settings to the rclone instance. You can confirm that the settings are active by querying the options/get endpoint manually:

curl -X POST http://127.0.0.1:51900/options/get  #If you change the running port from settings also change the `51900` to your port.

If you scroll to the log section in the output, you will see that the values are indeed set:

    "log": {
        "File": "/home/hakan/log.txt",
        "MaxSize": -1,
        "MaxBackups": 0,
        "MaxAge": 0,
        "Compress": false,
        "Format": "date,time",
        "UseSyslog": false,
        "SyslogFacility": "DAEMON",
        "LogSystemdSupport": true,
        "WindowsEventLogLevel": "DEBUG"
    },

Since the API confirms the configuration is loaded (e.g., the File path is set), we can be sure the app is handling the configuration correctly. If the logs are still not appearing in the file or systemd, it is likely an internal issue with how rclone handles logging in daemon mode or a permissions issue, rather than a configuration failure in the manager.

[nealeydee]

Everything looks like it is loaded OK, but nothing gets written to the log file. Have checked permissions etc... Not sure that the API can reliably set the logging function reliably according to this:

https://forum.rclone.org/t/set-rclone-logging-level-via-rpc/42687/3

If I run a command from the command line like this:
/usr/bin/rclone sync --config=/home/rclone-manager/.config/rclone/rclone.conf -v --log-file /home/rclone-manager/rclone.log --create-empty-src-dirs "OneDriveND:Pictures/Camera Roll" /mnt/AndroidPhotos

I get the log file filled in.

2026/01/02 17:45:43 INFO : There was nothing to transfer 2026/01/02 17:45:43 INFO : Transferred: 0 B / 0 B, -, 0 B/s, ETA - Checks: 5879 / 5879, 100%, Listed 11758 Elapsed time: 35.0s

In any case, thanks for your help.

Teşekkür ederim

[Hakanbaban53]

I wanted to share a quick update: I have added support for Rclone logging to a file. The file input interface now looks like this:

It seems to be working correctly. The log levels also function as expected when configured through this configuration modal.

However, I am running into one odd issue: it does not seem to accept path changes via the rcd (Remote Control Daemon) like as before. Probably cause of the rclone itself.