vorta icon indicating copy to clipboard operation
vorta copied to clipboard

Can't add existing repository - Vorta exception

Open prometheusAmb opened this issue 2 months ago • 1 comments

Description

I am trying to reconnect my backups after a fresh installation of the OS on my computer. I tried to add two existing backup sets. I was told to unlink and relink my repository. When I try to do that Vorta gives me a long message on a fatal exception:

Uncaught exception, please file a report with this text at
https://github.com/borgbase/vorta/issues/new
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/peewee.py", line 6970, in get
    return clone.execute(database)[0]
           ~~~~~~~~~~~~~~~~~~~~~~~^^^
  File "/usr/lib/python3/dist-packages/peewee.py", line 4339, 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 "/usr/lib/python3/dist-packages/vorta/application.py", line 219, in react_to_log
    profile = BackupProfileModel.get(name=context['profile_name'])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/peewee.py", line 6522, in get
    return sq.get()
           ^^^^^^^^
  File "/usr/lib/python3/dist-packages/peewee.py", line 6973, 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]

Reproduction

  • [x] I tried to reproduce the issue.
  • [x] I was able to reproduce the issue.

OS

Debian Linux Version 12, KDE Plasma 5.27.5

Version of Vorta

0.8.10

What did you install Vorta with?

Distribution package

Version of Borg

1.2.4

Logs


prometheusAmb avatar Oct 27 '25 07:10 prometheusAmb

@prometheusAmb
vorta.store.models.BackupProfileModelDoesNotExist: <Model: BackupProfileModel> instance matching query does not exist:

From the logs: Vorta fails to access information about your BackupProfileModel in your setting db.

You wrote that you did a fresh installation of your OS: Did you remove your old Vorta setting before reinstalling Vorta? (e.g. wipe out your old user data and configs) Or did you transfer/ reuse your old Vorta configs? When installing the fresh OS, did you also update Vorta to a newer version?

You use a very old (beta?) version of Vorta (from Nov 2021). Could you check if the same issue appears, if you use a recent version of Vorta (e.g. installed via pip or via flatpak)?

goebbe avatar Nov 07 '25 08:11 goebbe