Database locked error

[gEd]

Greetings alibert

I just experienced a database lock error whilst scheduling a number of recordings one after the other in TV Listings.
Yes I am running a pre-release of NPBR but I don't think that this should be an issue and I have experienced a few locking problems in the past whilst on a public release.

I have attached the logs and would appreciate it if you could have a look when you have some time please.


[edit] let me know if you think I should post this in the NPVR forum instead.

[Graham]

Ditto ... my suspicion is that it has to do with the version of SQLite that is in the current distribution of NextPVR.

[alibert]

Hi,

I'm still on npvr 2.6, but there should be no changes in the plugin's behaviour when running against npvr 3. From the logs, it seems that some background activity continously updates the epg (probably due to a tuner collecting epg data from the stream on the fly). This leads to some further tasks putting extra read/write load on the database: the npvr scheduler that is checking for recurring recordings, and the tv listings plugin that reloads the updated data. This situation finally lead to the error you've seen. Maybe it's worth to look if you can deactivate those incremental on-the-fly epg updates, and let npvr update your guide over night only.

-alibert

[gEd]

tx alibert.

I have NPVR set to perform it's daily EPG update at 5am so it was not that) but the tuner may have been busy at the time.
I will try ticking/unticking "enable EPG during live TV" and see if I can reproduce the problem.
tx

[gEd]

ok, I reproduced the problem using Subs TV Guide so I will report it to him (It IS related the option to enable DVB EPG update during live TV that causes the problem.
cu