I noticed the same for a long time. It seems this indication is a prompt for you to browse all the available locations where Duplicati keeps their log files. Notably in the (quite unintuitive) location under “About > Logfiles” - and not where one would expect them (under General or Remote).
When I looked at the log messages in “About” they didn’t give me a clue as it consists of tons of single line messages. I find it more useful to use the options “log-file” and “log-file-log-level” on step 5 of the configuration, under advanced options. Then you can mull over the messages at least in a normal log file.
This does get annoying… I’m not sure how much is historical. The CLI came first. CLI can’t get to errors saved in About → Show log → Stored because those errors are in the GUI server’s DB, not the per-job.
Per-job DB log has results statistics of the operation, but if job fails before a good end, there are no stats.
Single line errors in the GUI frequently expand with details when clicked on.
Log files work well, and reporting options do too in the sense that you get a good look at errors that occur.
You can use reporting to feed third-party monitors such asDuplicati Monitoring and dupReport if you wish.
<backup> --> Show log --> Remote has no error messages. It’s just low-level remote operations.
You can’t see the details behind things like upload failures, so it’s not very useful even for experts.
<backup> --> Show log --> General gives non-expandable one-liners but usually needs more info.
That’s when you try to reproduce the problem under About --> Show log --> Live (or set a log file).
Thank you everyone for the answers.
I found the “system” (not job related) logs.
I think, that current system behavior can be considered as a bug.
we can see popup saying “Error happened” and button with label “SHOW”
but when i click it - error doesn’t show at all - instead we can see backup log with no entry for today.