starred/Prowlarr

Fork 0

mirror of https://github.com/Prowlarr/Prowlarr.git synced 2026-03-02 22:57:22 -05:00

Prowlarr (and Sonarr) fail to restart on Windows – index UC_Version already exists (SQLite migration loop) #1294

New issue

Open

opened 2026-02-20 10:09:23 -05:00 by deekerman · 10 comments

deekerman commented

2026-02-20 10:09:23 -05:00

Owner

Originally created by @Kalinka98 on GitHub (Feb 18, 2026).

I attest that there is not an existing issue for this?

I have searched the existing open and closed issues

I confirm this is not related to a Cardigann YML Indexer

Current Behavior

On a fresh install:

Application starts successfully.
Database is created automatically.
Web UI is accessible and everything works normally.

After closing the application and attempting to start it again, startup fails with a fatal error.

If the database file (e.g., prowlarr.db and logs.db) is deleted:

The application starts again successfully (fresh initialization).
On the next restart, the same error occurs again.
This results in a repeatable failure loop on every restart.
The same behavior occurs in Sonarr independently (separate install and database).

What Has Been Tested:

Verified apps are completely separated (no shared DB or folders).
Tried installing both as tray and service
Confirmed standard Windows Defender only (no third-party antivirus).
Manually inspected DB using DB Browser for SQLite.
Attempted deleting duplicate entries in VersionInfo table.
Attempted manually dropping conflicting entries (error then occurs on next object in sequence).
Deleted full DB file → works once → fails again on next restart.
Ran as administrator.
Confirmed no manual modifications to schema beyond troubleshooting attempts.

Deleting individual entries does not resolve the issue — the error simply shifts to the next migration/index step.

Expected Behavior

After the initial successful run, subsequent restarts should not attempt to recreate existing SQLite indexes or fail on migration steps that were already applied.

Steps To Reproduce

I am not sure how reproducable it is, since it is a fresh install with default settings

Environment

- OS: Windows 11 (latest updates)
- Prowlarr: Prowlarr 2.3.2.5245 and 2.3.0.5236
- Installation method: Official Windows installer (default settings)
- Install path: C:\ProgramData\ (default)
- Using Reverse Proxy: No

What branch are you running?

Master

Trace Logs?

Edit: Trace logs: https://gist.github.com/Kalinka98/e2db67b375a257037cec048dbb7cea6a

I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I attest that I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @Kalinka98 on GitHub (Feb 18, 2026). ### I attest that there is not an existing issue for this? - [x] I have searched the existing open and closed issues ### I attest this is not related to a Cardigann YML Indexer. - [x] I confirm this is not related to a Cardigann YML Indexer ### Current Behavior On a fresh install: - Application starts successfully. - Database is created automatically. - Web UI is accessible and everything works normally. After closing the application and attempting to start it again, startup fails with a fatal error. If the database file (e.g., prowlarr.db and logs.db) is deleted: - The application starts again successfully (fresh initialization). - On the next restart, the same error occurs again. - This results in a repeatable failure loop on every restart. - The same behavior occurs in Sonarr independently (separate install and database). What Has Been Tested: - Verified apps are completely separated (no shared DB or folders). - Tried installing both as tray and service - Confirmed standard Windows Defender only (no third-party antivirus). - Manually inspected DB using DB Browser for SQLite. - Attempted deleting duplicate entries in VersionInfo table. - Attempted manually dropping conflicting entries (error then occurs on next object in sequence). - Deleted full DB file → works once → fails again on next restart. - Ran as administrator. - Confirmed no manual modifications to schema beyond troubleshooting attempts. Deleting individual entries does not resolve the issue — the error simply shifts to the next migration/index step. ### Expected Behavior After the initial successful run, subsequent restarts should not attempt to recreate existing SQLite indexes or fail on migration steps that were already applied. ### Steps To Reproduce I am not sure how reproducable it is, since it is a fresh install with default settings ### Environment ```markdown - OS: Windows 11 (latest updates) - Prowlarr: Prowlarr 2.3.2.5245 and 2.3.0.5236 - Installation method: Official Windows installer (default settings) - Install path: C:\ProgramData\ (default) - Using Reverse Proxy: No ``` ### What branch are you running? Master ### Trace Logs? Edit: Trace logs: https://gist.github.com/Kalinka98/e2db67b375a257037cec048dbb7cea6a ### I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I attest that I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

Type: Bug

Status: Needs Triage

labels

2026-02-20 10:09:23 -05:00

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Feb 18, 2026):

Do you have the same issue with Radarr, Sonarr or Lidarr?

VersionUniqueMigration is a migration coming from FluentMigrator.

Prowlarr uses v3.3.2, same goes for Sonarr.
Radarr uses v6.2.0, same as Lidarr.

There are some changes upstream, but since this version is being used for years I'm inclined to say it might a possible corruption with your setup.

Could you run .schema VersionInfo in sqlite3 prowlarr.db or in DB Browser for SQLite, and share the output?

@mynameisbogdan commented on GitHub (Feb 18, 2026): Do you have the same issue with Radarr, Sonarr or Lidarr? `VersionUniqueMigration` is a migration coming from `FluentMigrator`. Prowlarr uses [v3.3.2](https://github.com/Prowlarr/Prowlarr/blob/c3a7fbdd861ef3205a476cffc3abc5cb0708f3bb/src/NzbDrone.Core/Prowlarr.Core.csproj#L16-L18), same goes for [Sonarr](https://github.com/Sonarr/Sonarr/blob/028d2414e7ca788c4a3bebcb7b1c159e764c5bdd/src/NzbDrone.Core/Sonarr.Core.csproj#L19-L21). Radarr uses [v6.2.0](https://github.com/Radarr/Radarr/blob/89110c2cc8ec671d718cf34acc845f66d475a427/src/NzbDrone.Core/Radarr.Core.csproj#L21-L23), same as [Lidarr](https://github.com/Lidarr/Lidarr/blob/f6a3e7370540cc25caf3aaf0f1c91e7c085585ac/src/NzbDrone.Core/Lidarr.Core.csproj#L18-L20). There are some changes upstream, but since this version is being used for years I'm inclined to say it might a possible corruption with your setup. Could you run `.schema VersionInfo` in `sqlite3 prowlarr.db` or in DB Browser for SQLite, and share the output?

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@Kalinka98 commented on GitHub (Feb 18, 2026):

Here is the output:
CREATE TABLE IF NOT EXISTS "VersionInfo" ("Version" INTEGER NOT NULL, "AppliedOn" DATETIME, "Description" TEXT);
CREATE UNIQUE INDEX "UC_Version" ON "VersionInfo" ("Version" ASC);

Also can confirm, Sonarr and Prowlarr are not working,
Radarr and Lidarr are working fine

@Kalinka98 commented on GitHub (Feb 18, 2026): Here is the output: CREATE TABLE IF NOT EXISTS "VersionInfo" ("Version" INTEGER NOT NULL, "AppliedOn" DATETIME, "Description" TEXT); CREATE UNIQUE INDEX "UC_Version" ON "VersionInfo" ("Version" ASC); Also can confirm, Sonarr and Prowlarr are **not** working, Radarr and Lidarr are working fine

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Feb 18, 2026):

I guess Prowlarr needs github.com/Sonarr/Sonarr@3796c9e30f, github.com/Sonarr/Sonarr@52d7f67627 and github.com/Sonarr/Sonarr@255f1c37c3 to be same version as Radarr and Lidarr.

Sonarr v4 is frozen, and v5-develop is already using latest version which is 8.0.1.

@mynameisbogdan commented on GitHub (Feb 18, 2026): I guess Prowlarr needs https://github.com/Sonarr/Sonarr/commit/3796c9e30f6d8dec28a7587fcbe9cf530ebb26d7, https://github.com/Sonarr/Sonarr/commit/52d7f676274df312db7120474119132928690766 and https://github.com/Sonarr/Sonarr/commit/255f1c37c3560fd13287e9def164c64c84e6fc3a to be same version as Radarr and Lidarr. Sonarr v4 is frozen, and v5-develop is already using latest version which is 8.0.1.

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@Kalinka98 commented on GitHub (Feb 18, 2026):

Yup, can confirm, switching Sonnar to v5-develop fixed the issue for it. Thanks! Waiting for Prowlarr

@Kalinka98 commented on GitHub (Feb 18, 2026): Yup, can confirm, switching Sonnar to v5-develop fixed the issue for it. Thanks! Waiting for Prowlarr

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Feb 18, 2026):

How did you switched Sonarr? There are no available builds yet.

@mynameisbogdan commented on GitHub (Feb 18, 2026): How did you switched Sonarr? There are no available builds yet.

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@Kalinka98 commented on GitHub (Feb 18, 2026):

I changed the branch in config.xml to v5-develop.
People in discord adviced me to not use it, I just wanted to test

@Kalinka98 commented on GitHub (Feb 18, 2026): I changed the branch in `config.xml` to v5-develop. People in discord adviced me to not use it, I just wanted to test

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Feb 18, 2026):

Go to system > status > about, what version is shown there?

@mynameisbogdan commented on GitHub (Feb 18, 2026): Go to system > status > about, what version is shown there?

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@Kalinka98 commented on GitHub (Feb 18, 2026):

4.0.16.2944. Nvm, I was too excited and forgot to fully close it before rebooting. Sorry, I am new to this...

@Kalinka98 commented on GitHub (Feb 18, 2026): 4.0.16.2944. Nvm, I was too excited and forgot to fully close it before rebooting. Sorry, I am new to this...

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Feb 18, 2026):

Like I said, there are no v5 builds anyway. Weird that it's working now. 😅

@mynameisbogdan commented on GitHub (Feb 18, 2026): Like I said, there are no v5 builds anyway. Weird that it's working now. 😅

deekerman commented

2026-02-20 10:09:24 -05:00

Author

Owner

@Kalinka98 commented on GitHub (Feb 18, 2026):

No, no, it's not. I deleted the *.db files and opened it up, but then when closing the browser window I forgot to exit it from the tray, hence me thinking that it was working when reopening it, but it was the same instance

@Kalinka98 commented on GitHub (Feb 18, 2026): No, no, it's not. I deleted the *.db files and opened it up, but then when closing the browser window I forgot to exit it from the tray, hence me thinking that it was working when reopening it, but it was the same instance