Sonarr error: Database is locked about spksrc HOT 11 CLOSED

Hi @geotibi, I've identified the primary issue as a database lock error. According to Sonarr/Sonarr#5402, "the database being locked on it's own isn't an error". Did you encounter this problem prior to the automatic update to v4.0.3.1413? Regardless, the developers at the upstream repository need a trace log to effectively troubleshoot. You can find instructions on enabling this feature here: https://wiki.servarr.com/sonarr/troubleshooting. Let me know if you need any further assistance.

from spksrc.

Hello,
The installed version is 4.0.3.1413, synology package version 20240114-4. I observed since last 2-3 weeks than one Series is not updating and I've started looking in the logs and I saw that database locked error and I don't know how to fix it.
sonarr traces.txt
I've attahced also the traces

from spksrc.

@geotibi, as this may be an upstream issue I've logged an upstream ticket on your behalf. Will update here on the findings.

from spksrc.

@geotibi, the upstream team closed the issue I opened with the following note:

the database being locked is not an issue.
Episode information not being updated is a result of an ongoing issue with the TVDB API not returning all the information is should - see this issue for reference: thetvdb/v4-api#323

from spksrc.

Database locks are generally never bugs and are always due to under powered systems that are unable to keep up with the IOps required

BTFS filesystems also weren't playing nice but believe this was fixed downstream and pulled back to sonarr

from spksrc.

hi @bakerboy448, while it is true that databases can be affected by underpowered systems, I don't believe there is evidence to support that in this instance.

I run a DS916+ system which has an Intel Pentium N3710 CPU. The benchmarks for this show an average CPU mark of 1386. I also have my drives configured with btrfs and with my setup I've not seen database locking issues on my rig. I do acknowledge that I used to see issues with Radarr which were acknowledged as a bug under Radarr/Radarr#9173 but this was subsequently resolved.

As for this user, they run a newer DS920+ which has an Intel Celeron J4125 CPU. The benchmarks show a much faster performance than my own with an average CPU mark of 2961. Additionally, given that this issue only started for them about 2-3 weeks ago and not before I don't support the view that there is evidence that the database is being CPU limited.

As such, I believe the issue cited upstream regarding the TVdb API is a much more likely candidate as a root cause.

hey @geotibi, out of curiosity, is it only one series that has issues updating or do all your series have issues updating?

from spksrc.

It'd be drive constrained for IOWait more than CPU

but yes agree upstream poor data on TVDb is likely the root cause as sonarr team said

from spksrc.

Hello @mreid-tt I observed indeed that this is happening to one series because almost each week new episodes are added in TVdb for that one, but I'm not 100% sure because I do not have any other Series which is ongoing and updated weekly on TVdb.

from spksrc.

Yesterday, after around 3 weeks the series got updated suddenly. As I mentioned, the issue with database locked is happenig very often but when this is not locked, the update is working smoothly.

from spksrc.

Today I did an update on TVdb 1 hours and a half ago, I did a series update now and everything was updated in Sonarr without any issue, no database lock message. It seems that it started to work without any fix from my side.

from spksrc.

@geotibi okay, thanks for the update. As this doesn't appear to have reoccurred I'll go ahead and close the issue.

from spksrc.