error adding repository while lock file exists
When adding an existing repository, the following error appears.
This appears if a lock file exists in the repository under lock.exclusive/[email protected]
Workaround:
- delete the lockfile, then the repo can be added successfully.
Error:
Uncaught exception, please file a report with this text at
https://github.com/borgbase/vorta/issues/new
Traceback (most recent call last):
File "/app/lib/python3.11/site-packages/peewee.py", line 7285, in get
return clone.execute(database)[0]
~~~~~~~~~~~~~~~~~~~~~~~^^^
File "/app/lib/python3.11/site-packages/peewee.py", line 4581, in __getitem__
return self.row_cache[item]
~~~~~~~~~~~~~~^^^^^^
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/lib/python3.11/site-packages/vorta/application.py", line 227, in react_to_log
profile = BackupProfileModel.get(name=context['profile_name'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/lib/python3.11/site-packages/peewee.py", line 6833, in get
return sq.get()
^^^^^^^^
File "/app/lib/python3.11/site-packages/peewee.py", line 7288, in get
raise self.model.DoesNotExist('%s instance matching query does '
vorta.store.models.BackupProfileModelDoesNotExist: <Model: BackupProfileModel> instance matching query does not exist:
SQL: SELECT "t1"."id", "t1"."name", "t1"."added_at", "t1"."repo_id", "t1"."ssh_key", "t1"."compression", "t1"."exclude_patterns", "t1"."exclude_if_present", "t1"."schedule_mode", "t1"."schedule_interval_count", "t1"."schedule_interval_unit", "t1"."schedule_fixed_hour", "t1"."schedule_fixed_minute", "t1"."schedule_interval_hours", "t1"."schedule_interval_minutes", "t1"."schedule_make_up_missed", "t1"."validation_on", "t1"."validation_weeks", "t1"."prune_on", "t1"."prune_hour", "t1"."prune_day", "t1"."prune_week", "t1"."prune_month", "t1"."prune_year", "t1"."prune_keep_within", "t1"."new_archive_name", "t1"."prune_prefix", "t1"."pre_backup_cmd", "t1"."post_backup_cmd", "t1"."dont_run_on_metered_networks" FROM "backupprofilemodel" AS "t1" WHERE ("t1"."name" = ?) LIMIT ? OFFSET ?
Params: ['New Repo', 1, 0]
Solution: An error that's more user friendly, i.e. suggesting there is a lockfile in place, would be more helpful.
I believe I fixed this in the master branch, which is already released as 0.10.0-beta1: https://github.com/borgbase/vorta/releases/tag/v0.10.0-beta1
Collecting all duplicates of this type -> #2070
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.
This issue was closed because it has been stalled for 7 days with no activity.