Feature Request: Determine Content of Log File

Hi All,

Currently --log-file content can be determined using --log-file-log-level e.g. ‘Warning’.
Still this options provides too much information. One single warning produces a huge amount of text. Example:

2025-07-07 15:51:42 +02 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: C:\Users\abcde\OneDrive\Documenten\DATA\Nog Goed Opslaan\Microsoft-account primair over te zetten naar ander emailadres.pptx
System.IO.IOException: The process cannot access the file ‘\?\C:\Users\abcde\OneDrive\Documenten\DATA\Nog Goed Opslaan\Microsoft-account primair over te zetten naar ander emailadres.pptx’ because it is being used by another process.
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)
at Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.<>c__DisplayClass1_0.<b__0>d.MoveNext()

I suggest to create an option to change the Log File text by individual user OR to have a very short standard version: using the example above I would suggest something like:

2025-07-07 15:51:42 +02 – Warning: Failed to process path: C:\Users\stefh\OneDrive\Documenten\DATA\Nog Goed Opslaan\Microsoft-account primair over te zetten naar ander emailadres.pptx. The process cannot access the file because it is being used by another process.

If more detail would be needed, user can rerun the backup using full text instead of limited text.

Kind regards,
Stef

Hi @Stef, welcome to the forum :waving_hand:

I think a safe version would be to remove information about the call stack. Those warnings originate from a specific place, and the debug information here is not really important.

I have created an issue for tracking this.

Not sure whether I fully understand/comprehend your response, if it does what I asked I’m fully supportive :smiley::clap::+1:

1 Like