bug(sqlite): database locks under load #122
Labels
bug
Something isn't working
Comments
|
I tested to nuke everything (aka data folder) and still get error on new created db by the app. I use the sqllite version and not sure as it sometimes work and sometimes not so if its related to the arrs or autopulse (autoscan used to work tho) |
|
Could you share your docker config? Seems like this is a permissions issue possibly |
4 tasks
|
@EsmailELBoBDev2 feel free to try |
dan-online
changed the title
|
I used it and still noticed 2 errors about it but not same as last time so not sure if its related or no |
|
I think the database pool is both getting cloned somewhere it shouldn't coupled with a notify issue, so I'll look at this further and do some more testing |
If it helps I will stop notify one and test again (will post results) |
|
@EsmailELBoBDev2 I think I found the main source of the issue, and hopefully solved it with |
|
Hello, it's still erroring out :/ I'm now testing without whisparr/inotify and will tell you if i still face same issue |
Ah, I think I'll need to add this as a migration... if you remove the existing db then it should work |
|
oh yeah sure no problem, I deleted whole |
|
Seems working 🥳 but off topic issue is: even tho my config seems fine and it indeed send some notifications fine |
|
Yep that would be linked to #105, I'll change the PR to auto-migrate the database then merge which will close this |
|
Alright, good luck and thank you so much for the help! |
|
Hello @dan-online, I found some entries but thats after longer run and I'm using inotify but removed the db as you recommended before |
|
Hmmm, that's odd, I write/del 20 files/s for 15mins and I didn't see any database locking on Edit: corrected pr number |
|
uhh i was on 125 still 😅 -- for 105 I get |
|
Whoops I mean 125, but since it pushes a new image to the same tag you may be on an old version |
|
oh yes I made sure to pull it before I reply above and pulling now does not yield any new updates |
|
and for me it took over some hours to notice the error so first 15m were fine indeed |
|
Hm, okay interesting, I'll link diesel-rs/diesel#2365 to keep track |
|
if you want me to test anything please let me know and to be fair I don't get it as often as used to |
|
I've pushed |
|
okay i pulled it too and gonna test and let you know later! (PS I have so much files so yeah... 😂 ) |
not great start but hopefully its one time thing |
|
Huh, when it's the first boot on a new database- it seems to fail setting the pragmas (probably because it runs on each connection which is set to 16 for now) so yea should be okay past there |
|
welp, im running it now and testing so i will let you know later! and thank you |
|
|
|
I pulled it and gonna gonna let you know |
|
Hello, I think this fixes it! 🥳 I got no more issues about db or even discord. I get some errors about jellyfin itself but i will assume it's something related to my setup |
|
Awesome! Merged to latest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
I noticed it appeared lately and not sure why, I changed nothing in my config.
Steps To Reproduce
Additional Information
I use debian testing with docker compose
logs:
config:
The text was updated successfully, but these errors were encountered: