SQLite Error 5: 'database is locked'

[mvallevand]

It might be a red herring but the logs with fails seem to have have these lines near the No ParallelProcessing batch message the one that work

2019-10-10 20:43:48.388 [DEBUG][20] found match
2019-10-10 20:43:49.652 [DEBUG][35] Done fanart.tv lookup
2019-10-10 20:43:49.711 [DEBUG][36] got season info

It is not clear why it is even searching for art on some of these.

Martin

[BrettB]

I took the day off from work (for my birthday) today, so thought I'd try a little more testing. It appears that the problem is somehow specifically related to recordings using the HDHR Prime tuner(s).

I did a fresh start of the server, launched knewc on the RPi, went into the guide and started 4 quick records of shows from channels on the HDHR Quatro tuners. I left knewc running (displaying the guide). As I scheduled each show to record, the entry on the guide turned red. All recordings ran successfully including the comskip processing in PostProcessing after the recordings ended. Absolutely no database locked errors anywhere in the log.
  logs-20191011-1142.zip (Size: 723.08 KB / Downloads: 0)

It's strange because both the Quatro and the Prime are using the NextPVR HDHR devices. So I wouldn't think that there would be a difference in what it is doing, but obviously something isn't right!

[BrettB]

Is it possible that this problem is somehow related to the fact that my database currently has 2 sets of all my cable card channels with the same numbers (1 set on the 1st Prime's 3 tuners and a 2nd set on the 2nd Prime's 3 tuners)? As I posted before the AutoMerge won't merge them because NextPVR pulled them in with different names.

More testing, and I think that may be the key problem.

I created a brand new npvr.db3 database. Initially I just configured tuners one of the Primes. I did a couple of test recordings and they seemed to work fine. So then I configured 1 tuner on the other Prime--but I didn't copy of the configuration from the first Prime (to duplicate what I had to do with my real server database since the copy was trying to copy from the Quatro rather than the other Prime). The result was again 2 sets of all the channels with the same channel numbers (i.e. 2 channel 804 WCCODTs with different channel IDs). Now when I try to do a recording, I get the database locked errors.
  logs-NewDB2PrimeDevicesDupChannels.zip (Size: 852.7 KB / Downloads: 1)

[BrettB]

Is it possible that this problem is somehow related to the fact that my database currently has 2 sets of all my cable card channels with the same numbers (1 set on the 1st Prime's 3 tuners and a 2nd set on the 2nd Prime's 3 tuners)? As I posted before the AutoMerge won't merge them because NextPVR pulled them in with different names.

More testing, and I think that may be the key problem.

I created a brand new npvr.db3 database. Initially I just configured tuners one of the Primes. I did a couple of test recordings and they seemed to work fine. So then I configured 1 tuner on the other Prime--but I didn't copy of the configuration from the first Prime (to duplicate what I had to do with my real server database since the copy was trying to copy from the Quatro rather than the other Prime). The result was again 2 sets of all the channels with the same channel numbers (i.e. 2 channel 804 WCCODTs with different channel IDs). Now when I try to do a recording, I get the database locked errors.

To continue the test, I used the AutoMerge on this new, test database to merge all of the channels. (It works in this database because both sets of channels got the same names when they were configured.) At first after the merge things didn't work right, but once I did an update EPG and restart the server, then it seems to be all OK. I've got 3 test recordings running now.