mirror of
https://github.com/tubearchivist/tubearchivist-jf-plugin.git
synced 2026-03-23 20:37:14 +00:00
[GH-ISSUE #11] [Bug]: SQLite Error 5: 'database is locked'. #10
Labels
No labels
bug
enhancement
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tubearchivist/archived-tubearchivist-jf-plugin#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HarryFreeMyLand on GitHub (May 15, 2024).
Original GitHub issue: https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/11
I've read the documentation
Operating System
Linux (TrueNAS k3s)
Your Bug Report
Describe the bug
I can't seem to get the 1.3.0.0 version of this plug working with Jellyfin 10.9.1
I've created a new instance of Jellyfin, new database (my old one got corrupted during the migration to 10.9.1, so can't test that), installed the plugin, verified that it is able to connect to my Tube Archivist instance. but when trying to scan for metadata I get errors related to SQLite not being able to process a transaction.
Steps To Reproduce
create new instance of 10.9.1, install plugin 1.3.0.0, set parameters, create library, scan.
Expected behavior
Relevant Jellyfin log output
Anything else?
No response
@dscurrey commented on GitHub (May 19, 2024):
I'm also seeing this problem.
@DarkFighterLuke commented on GitHub (May 27, 2024):
Hi, I was trying to reproduce the problem, but I don't get these errors on my instance logs.
Does the problem persist?
@HarryFreeMyLand commented on GitHub (May 29, 2024):
yes, just re-installed to verify that it still happens but... I still get the same thing on a fresh 10.9.3 and 1.3.0.0 combo.
@DarkFighterLuke commented on GitHub (May 29, 2024):
Maybe it's something with TrueNAS, I don't have one so I can't test it, but I am pretty sure that is not related to the plugin, you should try on Jellyfin issues...
@HarryFreeMyLand commented on GitHub (Jun 2, 2024):
Sorry about this, it was a permissions issue where the Jellyfin config directory for whatever reason needed 770 and not 750 permissions as were created by default.