-
-
Notifications
You must be signed in to change notification settings - Fork 870
Generate https debug log for support
In some cases it may be necessary to generate a https 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 https debug log in standalone mode, use one of the following command:
onedrive --synchronize --verbose --verbose --resync --resync-auth --debug-https 2>&1 | grep -vi 'authorization: bearer' > debug_output.log
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-https 2>&1 | grep -vi 'authorization: bearer' > debug_output.log
Post generating the debug log, ensure you remove 'monitor_max_loop' from your configuration file.
docker container run -e ONEDRIVE_DEBUG=1 -e ONEDRIVE_RESYNC=1 -e ONEDRIVE_DEBUG_HTTPS=1 -v onedrive_conf:/onedrive/conf -v "${onedriveDir}:/onedrive/data" driveone/onedrive:latest
Once complete, please archive and email debug_output.log or applicable debug log from Docker container to support@mynas.com.au
If the resulting log archive file is >20Mb please can you provide a link to download the archive file.