Skip to content
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

Unhandled IndexError #1541

Closed
2 tasks done
Kuchenmampfer opened this issue Jan 12, 2023 · 2 comments
Closed
2 tasks done

Unhandled IndexError #1541

Kuchenmampfer opened this issue Jan 12, 2023 · 2 comments

Comments

@Kuchenmampfer
Copy link

Description

I just tried to connect to a repository which was written to from my vps at the same time and encountered the following error:

Unbehandelter Fehler, bitte melde dies mit diesem Text auf
https://github.com/borgbase/vorta/issues/new
Traceback (most recent call last):
  File "/app/lib/python3.9/site-packages/peewee.py", line 7072, in get
    return clone.execute(database)[0]
  File "/app/lib/python3.9/site-packages/peewee.py", line 4436, 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.9/site-packages/vorta/application.py", line 219, in react_to_log
    profile = BackupProfileModel.get(name=context['profile_name'])
  File "/app/lib/python3.9/site-packages/peewee.py", line 6624, in get
    return sq.get()
  File "/app/lib/python3.9/site-packages/peewee.py", line 7075, 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

  • I tried to reproduce the issue.
  • I was able to reproduce the issue.

OS

crystal linux latest and kde plasma 5.26.5

Version of Vorta

0.8.9

What did you install Vorta with?

Flatpak

Version of Borg

1.2.0

Logs

Unbehandelter Fehler, bitte melde dies mit diesem Text auf
https://github.com/borgbase/vorta/issues/new
Traceback (most recent call last):
  File "/app/lib/python3.9/site-packages/peewee.py", line 7072, in get
    return clone.execute(database)[0]
  File "/app/lib/python3.9/site-packages/peewee.py", line 4436, 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.9/site-packages/vorta/application.py", line 219, in react_to_log
    profile = BackupProfileModel.get(name=context['profile_name'])
  File "/app/lib/python3.9/site-packages/peewee.py", line 6624, in get
    return sq.get()
  File "/app/lib/python3.9/site-packages/peewee.py", line 7075, 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]
2023-01-12 19:41:23,412 - vorta.borg.borg_job - ERROR - Failed to create/acquire the lock /home/backups/ostern/lock.exclusive (timeout).
@Kuchenmampfer
Copy link
Author

After my vps finished accessing the repo, this did not occur again. Plus, after the repo was known to vorta, simultaneous access resulted in a nice warning. So maybe it would be good to also have such a warning here when connecting to the repo for the first time.

@Kuchenmampfer
Copy link
Author

Kuchenmampfer commented Jan 12, 2023

Hmmm, looks like this is duplicate from #1449 and a few others. Vorta told me to report it, maybe you can take the new info that this also happens in my specific circumstances. But I can probably close it I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant