Owin SQLite error (5): database is locked

Help & Support
#1

Owin SQLite error (5): database is locked

getting these errors in the log alot since upgrading to 2.0.0.3082

Also
SQLite error (17): statement aborts at 40: [INSERT INTO [Commands] ([Name],[Body],[Priority],[Status],[QueuedAt],[StartedAt],[EndedAt],[Duration],[Exception],[Trigger]) VALUES (@Name,@Body,@Priority,@Status,@QueuedAt,@StartedAt,

And

SQLite error (17): statement aborts at 14: [SELECT [t0].[TypeName],[t0].[Interval],[t0].[LastExecution],[t0].[Id] FROM [ScheduledTasks] [t0] ] database schema has changed

#2

Also getting alot of these since the update to 2.0.0.3082 on Win8.1 today,

#3

Same here on windows 7 , does not really show anything up in the trace log though apart from what davlaw has in his post.

#4

seems to happen more during an RSS update…

Some logs with trace enabled…

http://pastebin.com/tCjGy1Yr

http://pastebin.com/Rdg0aBhv

#5

Same error in my logs also since moving to 2.0.0.3082.

#6

Same errors here also (after update.)

#7

Same error here also,

SQLite error (5): database is locked

Version: 2.0.0.3082
Mono Version: 3.10.0 (tarball Wed Nov 5 12:50:04 UTC 2014)

#8

Started seeing this now as well. There is nothing extra in the trace logs its just mirroring this message.

SQLite error (261): database is locked

#9

Any update?

#10

This still happens… not sure why and I don’t see any constant pattern that would help narrow it down… I do see a empty line after each of the Owin sqlite errors though… in my latest log file it happened 3 times:

15-5-11 09:11:30.4|Debug|Parser|Quality parsed: SDTV v1
15-5-11 09:11:30.4|Debug|Parser|Release Group parsed: lol
15-5-11 09:11:30.5|Debug|AcceptableSizeSpecification|Beginning size check for: once.upon.a.time.411.hdtv-lol
15-5-11 09:11:30.5|Trace|Owin|SQLite error (5): database is locked

15-5-11 09:11:30.6|Debug|AcceptableSizeSpecification|Item: once.upon.a.time.411.hdtv-lol, meets size constraints.
15-5-11 09:11:30.6|Debug|CutoffSpecification|Comparing file quality with report. Existing file is HDTV-720p v1
15-5-11 09:11:30.6|Debug|QualityUpgradableSpecification|Existing item meets cut-off. skipping.

next time:

15-5-11 09:11:30.8|Debug|DelaySpecification|Profile does not require a waiting period before download for Usenet.
15-5-11 09:11:30.8|Debug|HistorySpecification|Performing history status check on report
15-5-11 09:11:30.8|Debug|HistorySpecification|Checking current status of episode [14091] in history
15-5-11 09:11:30.8|Trace|Owin|SQLite error (5): database is locked

15-5-11 09:11:30.9|Debug|UpgradeDiskSpecification|Comparing file quality with report. Existing file is HDTV-720p v1
15-5-11 09:11:30.9|Debug|QualityUpgradableSpecification|existing item has better or equal quality. skipping
15-5-11 09:11:30.9|Debug|DownloadDecisionMaker|Release rejected for the following reasons: [Permanent] Existing file meets cutoff: HDTV-720p, [Permanent] SDTV is not wanted in profile, [Permanent] Quality for existing file on disk is of equal or higher preference: HDTV-720p v1

and then

15-5-11 09:11:32.2|Debug|NzbDrone.Core.Parser.QualityParser|Trying to parse quality for Breaking.Borders.S01E09.HDTV.x264-YesTV
15-5-11 09:11:32.2|Debug|Parser|Quality parsed: SDTV v1
15-5-11 09:11:32.2|Debug|Parser|Release Group parsed: YesTV
15-5-11 09:11:32.2|Trace|Owin|SQLite error (5): database is locked

15-5-11 09:11:32.2|Debug|ParsingService|No matching series breakingborders
15-5-11 09:11:32.2|Debug|DownloadDecisionMaker|Release rejected for the following reasons: [Permanent] Unknown Series
15-5-11 09:11:32.2|Trace|DownloadDecisionMaker|Processing release 203/600
#11

This error is benign, its not actually an error that causes anything to fail, it just means SQLite is busy and the request needs to be made again: https://www.sqlite.org/rescode.html#busy

Any failing due to these errors has been because the error was triggering logging in a loop and often ended up with too many requests to handle.

1 Like
#12