-
Notifications
You must be signed in to change notification settings - Fork 133
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
scheduled backup fails with uncaught exception: sqlite3.OperationalError: database is locked #1765
Comments
Is the DB opened in another application? |
I cannot think of an application that would access this DB apart from vorta itself. |
Out of curiosity, did you recently restore your full home directory from a vorta backup? |
No home directory restore in recent history or ever. The home directory on this computer is not part of the backups as it is mostly empty and holds no file of importance. Could it be that vorta locked the database when it tried and failed to gather information about the network connections and remained locked while waiting for a timeout as a scheduled backup tried to launch ? |
sysdbugfactory ***@***.***> writes:
No home directory restore in recent history or ever.
The home directory on this computer is not part of the backups as it is mostly empty and holds no file of importance.
If you mean that the $HOME of the user who runs Vorta is not part of the
dataset that is backed up, then this refutes my hypothesis.
Could it be that vorta locked the database when it tried and failed to gather information about the network connections and remained locked while waiting for a timeout as a scheduled backup tried to launch ?
Good question, I think you might be on to something! :)
|
that's what I meant. $HOME is not part of the dataset. This network_manager WARNING is a recurring occurence that shows up quite a number of times in the logs, so it could be an unlucky coincidence that both this and the scheduled backup happened at the same time.
|
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. |
sysdbugfactory ***@***.***> writes:
that's what I meant. $HOME is not part of the dataset.
Ok, that rules that out :)
This network_manager WARNING is a recurring occurence that shows up quite a number of times in the logs, so it could be an unlucky coincidence that both this and the scheduled backup happened at the same time.
`grep "vorta.network_status.network_manager - WARNING" * | wc -l` gives 343 occurences over the last 6 days.
@sysdbugfactory Have things improved in the months since you wrote this? I seem to
remember that there may have been some some network-manager changes in
the Vorta 0.9.x series.
|
We can tone down those logs, if there are too many. |
Description
This issue happened on a Manjaro linux computer where borg and vorta have been up and running since 2021 with 3 differents backups profiles. Everything is up to date. The computer was rebooted less than 48h ago.
After being AFK for a little while I came back to my computer screen to find a large error window that did not fit the screen and did not allow to copy its content. I was able to find the error in the log file which I pasted below.
Initiating a backup manually on all 3 profiles worked and did not raise this error again.
I was not able to replicate this random database lock that happened unattended.
I'm still filing a report as instructed to document the issue.
Environment
Logs
The text was updated successfully, but these errors were encountered: