If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post. I'd recommend not using a Yahoo or Verizon email account - the registration emails often disappear into a black hole. To start viewing messages,
select the forum that you want to visit from the selection below.

If you don't get your account activation email, check your spam folder. If it's not there, send a PM to the user account 'sub' and he'll help you out.

IGL database lock error

So, I occasionally end up with a run of IGL where there is an error at the end of "database is locked". The files get renamed, but the database doesn't get updated for the new name. It doesn't really bother me that the database doesn't get updated, since I don't watch the recordings made through NPVR, but I make use of the new name that is returned to do some other post-processing.

So, how do I avoid this, or how should I proceed when this happens? I just experimented and tried running it again, but I guess since the files were already renamed, nothing happened and it doesn't return the name.

So, I occasionally end up with a run of IGL where there is an error at the end of "database is locked". The files get renamed, but the database doesn't get updated for the new name. It doesn't really bother me that the database doesn't get updated, since I don't watch the recordings made through NPVR, but I make use of the new name that is returned to do some other post-processing.

So, how do I avoid this, or how should I proceed when this happens? I just experimented and tried running it again, but I guess since the files were already renamed, nothing happened and it doesn't return the name.

I've attached the IGL log for one such lock situation. Thanks.

I'd like to see all the NextPVR logs, the lock would likely come from elsewhere. Before I start the renaming operations I do start a database transaction which should lock the database too. Going from the time 22:08 I see you run some longish jobs before iGL maybe CPU is being hogged slowing down the rename operation.

To fix it manually rename just the .ts file back to original show in the log or NRecord, This Is Us_20170314_21002201.ts and rerun the same command shown in the log --oid 201124 --rename --zap2it --nfo --extra