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

Unique Constraint Error #2700

Closed
pooley182 opened this issue Oct 7, 2024 · 4 comments
Closed

Unique Constraint Error #2700

pooley182 opened this issue Oct 7, 2024 · 4 comments

Comments

@pooley182
Copy link

pooley182 commented Oct 7, 2024

Describe the bug
I set up Bazarr for the first time last night, I've never used it before I don't have an existing config or DB. (which seems to be the cause of the issue described in #2384)
It is still in the process of importing all my media from Sonarr but I'm seeing the following types of error in the logs a lot.

BAZARR cannot insert episodes because of (sqlite3.IntegrityError) UNIQUE constraint failed: table_episodes.sonarrEpisodeId

To Reproduce
Steps to reproduce the behavior:

  1. Honestly, I don't know. I've not done anything except deploy a Bazarr docker container and link it to my existing Sonarr/Radarr instances.

Expected behavior
No errors.

Screenshots
image

Software (please complete the following information):

  • Bazarr: 1.4.5
  • Radarr version: 5.11.0.9244
  • Sonarr version: 4.0.9.2244
  • OS: Linux, Unraid, docker container

Additional context
I'm not sure if there's two sync threads running at the same time that are conflicting with each other. So this might go away once my initial library is imported.

If the container is restarted the logs remain quiet for a little while, but sure enough the errors reappear after some time.

My Sonarr library is pretty large with over 35k episodes, it has been trying to do it's first sync with Sonarr since I started Bazarr about 15 hours ago

@pooley182
Copy link
Author

Debug log, in case it's useful.
bazarr.log

@morpheus65535
Copy link
Owner

Should be fixed in upcoming beta. Can you confirm please?

@rich-r
Copy link

rich-r commented Oct 14, 2024

Should be fixed in upcoming beta. Can you confirm please?

1.4.6-beta.3 fixed the issue for me but required a new database.

Here's what I tried:
Recreated the issue on 1.4.5 on a new database
Upgraded to 1.4.6-beta.3, using the existing db and observed the issue
Ran 1.4.6-beta.3 on a new database, which resolved the issue

@morpheus65535
Copy link
Owner

Let me know if it happens again!

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

No branches or pull requests

3 participants