New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Daily Vorta errors - local exception after client_loop: send disconnect: Broken pipe #1773
Comments
Looks like everything works, but the network breaks in the middle. Is the laptop going to sleep maybe or disconnecting Wifi?
|
Highly likely if Vorta doesn’t prevent a sleep when a backup is in progress. It shouldn’t throw tons of errors like this just because your laptop goes to sleep should it? |
I aggree that all three points are issues. Point 1 should be tracked in a seperate issue and needs #1522 to be completed. For 2 we are already planning to add a log viewer to Vorta that should include such a feature. For 3 there is #1444 and #1420. |
This happened to me too while doing an initial backup to BorgBase. It occurred numerous times while I was actively using my computer so I don't think it's just from sleep or inactivity on the client side. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as gave up on using Vorta |
Description
Every day I get tens of notifications from Vorta that there's an error during backup creation.
Three things I found:
Clicking on the notification does not show any errors or direct you to the logs.
Looking at the logs - they seem to be running at DEBUG level, I can't see where to change this to WARN or ERROR so that the signal to noise ratio is more usable?
I can see through the logs when Vorta thinks there is an interruption in the network rather than retrying or starting another stream the application throws an ERROR and dumps a trace (see logs below).
I have tried Borg and Vorta from homebrew and from pip and the behaviour is the same (although the homebrew version was quite laggy in general I'm assuming due to being an intel only binary).
^
Reproduction
OS
macOS, 13.5, 2021 Macbook Pro M1 Pro
Version of Vorta
0.9.0
What did you install Vorta with?
Pip
Version of Borg
1.2.4
Logs
Looking through macOS's system configd logs for the network interfaces, there's the normal route refresh that happens that's around the time that vorta crashes:
The text was updated successfully, but these errors were encountered: