Generate debug log for support

In some cases it may be necessary to generate a debug log to assist further with analysing what is occurring. Before generating a debug log, if you are running the OneDrive init.d or systemd service, you must stop this service first before generating the debug log.

To generate the debug log, use one of the following commands:

Standalone mode

onedrive --sync --verbose --verbose --resync --resync-auth > debug_output.log 2>&1

Monitor mode

To generate the https debug log in monitor mode, use one of the following command:

First, add the following to your 'config' file:

monitor_max_loop = "3"

This will terminate the monitor process after 3 full syncs of your data, allowing you time to replicate the issue when in --monitor mode.

onedrive --monitor --verbose --verbose --resync --resync-auth > debug_output.log 2>&1

Post generating the debug log, ensure you remove 'monitor_max_loop' from your configuration file.

Docker container example

docker container run -e ONEDRIVE_DEBUG=1 -e ONEDRIVE_RESYNC=1 -v onedrive_conf:/onedrive/conf -v "${onedriveDir}:/onedrive/data" driveone/onedrive:latest

Sending the Debug Log to support

Once complete, please archive and email debug_output.log or applicable debug log from Docker container to [email protected]

If the resulting log archive file is >20Mb please can you provide a link to download the archive file.