Replies: 5 comments
|
Similar request here #282 but I don't see any output from borg being written into |
|
Try running Vorta from the command line to get the exception, exceptions not being logged will be fixed by #628 . Errors in borg should not crash vorta, so its more likely a vorta problem |
|
@samuel-w Thanks, I will try that. It would still be useful to be able to configure borg verbosity and have the logs written out. I tried adding |
|
To read out the logs, we would have to print the entire json output. For something like |
|
It would be good to at least have the option. Large log files should not surprise the user if the user chooses to explicitly turn on debug. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Please consider adding a feature to save the output of
borgcommands to log files, with--debugturned on.I'm trying to debug why Vorta suddenly closed during a backup. I suspect the problem is in Vorta, not in borg. If I had a log of what each
borgcommand was doing, I could confirm whether the command finished successfully or not. The last line ofvorta.logjust says that the borg command was issued:vorta.borg.borg_thread - INFO - Creating archive atDescribe the solution you'd like
Add option to save the output of
borgcommands to log files with verbosity. Perhaps this can be added to the Misc panel?e.g. if feature is turned on, the command that would be issued would be:
vorta.borg.borg_thread - INFO - Running command /usr/bin/borg create --debug ...saving the stdout and stderr to `/home/user/.cache/Vorta/log/timestampXXX_borg.log", for example.
Describe alternatives you've considered
I tried to find where --log-json is writing to, but I think it is being written to stdout and intercepted by Vorta...so I can't independently tail the borg log...?
Thanks.
All reactions