My Duplicati instance is crashing at least weekly. I have no idea where I can find the log files to investigate the cause of the crash and/or log a bug about it.
I’ve checked Windows Event Viewer, and I’ve also tried using the “log-file” advanced option but it doesn’t include anything about application crashes.
Thanks. The most recent crash that I can find when filtering by .NET Runtime is on the 8th of Feb. I’ve had at least 6 crashes since then, including one between 1pm yesterday and 2pm today when I got notified my daily task hadn’t run.
By crash I mean the application is no longer running. It’s not visible in the taskbar, and not running in task manager.
The pull request (should this be in the manual?) says “next to the database” (guessing server).
If this is a Windows service as SYSTEM, you’re two levels high, but maybe you searched it all.
Were there any events just before the .NET Runtime ones that had other Duplicati complaints?
Your stack trace looks like two reports on Storj on Linux, so I’ll ask what destination type this is.
Or maybe it’s just a coincidence. Regardless, you probably need input from the lead developer.
My instance of Duplicati is running as the logged in user (it’s a headless mini PC that I RDP into), and my destinations are all Backblaze or Google Drive
Filtering my application log for just errors and warnings, I do see quite a few of these: Scoping unsuccessful for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy25 with error 0x80070057. which I’m not sure is related?
Would really like to just have a simple way to find the crash logs - why not expose them in the web GUI somewhere or something? This would be simplest and cover all OS configurations nicely. Guess I’ll log an issue
Then view Database screen for the job database path (likely in %LOCALAPPDATA%\Duplicati) and the Duplicati-server.sqlite server database should be there – and possibly also the crashlog file.
I’m not an expert in crashes, but also keep in mind that Duplicati might not be able to write the log when it crashes unexpectedly. I think there’s a post around here somewhere from the lead dev on intentional have-.NET-crash in a situation that’s too tough to unwind to a nicer end. In that case, it might be alive enough to write something somewhere beforehand. Then make that easy to find…
EDIT:
Some commentary on the finer points of crash logging.
is what it used to be, and it looks like it still is, so Duplicati-crashlog.txt.
Probably just didn’t create one, perhaps due to the reasons that I mentioned.
You can check in Duplicati-server.sqlite and see if it has recorded any error messages, but if it is a hard crash, there will not be any messages. The absence of the Duplicati-crashlog.txt file indicates that this is a hard crash.
If so, there should be some event being logged in Windows Event Viewer?
For the missing notification, do you know if the backup started before issue?
Is this Duplicati.GUI.TrayIcon.exe? How is it started, and with what options?
You can start it from a Command Prompt (don’t close terminal) to watch for a message when things go wrong. You can also have it make a log file by using
--log-file: Output log information to the file given
--log-level: Determine the amount of information written in the log file
Information level should at least show backup starts, ends, warnings and errors.
There are other more extreme ways to watch, e.g. Sysinternals Process Monitor.