Trying to identify "database locked" problems.

[martint123]

It is beginning to happen quite often to me now - as follows.

Nearly all the problems are when using a client PC (streaming mode).
Trying to cancel an in-progress recording. After confirming the delete, the yes/no screen fades out but does not go altogether and sits there for a minute or two.
Back to the pending screen and it is still showing as recording.
Cancel it and yes, it cancels this time.

Problem is that the first cancel comes up with a database locked error in the recording service log and it restarts recording with a -2 filename. Come to delete it and it only deletes the -2 recording, leaving the first bit orphaned, only able to be deleted with explorer (if you happen to know it is there).

Would there be any value in me running something like filemon on gbpvr.db3 to try to see what is locking and not unlocking the database?
If so, does anyone know if it can be run for maybe days without collapsing?

[sub]

You can set <LogSQL>true</LogSQL> in config.xml, then look at the SQL in the .log files when the problem occurs. A lock will typically happen when some insert/update statement is executed, but not closed, leaving that table locked.

[martint123]

OK Thanks, I'll run with that set and see what/if I spot anything.

[martint123]

It has just happened this evening. and I have sql logging on.

It started recording 'escape to the country' at 2009-12-08 17:13
But the old dear was watching it live on TV anyway, so at 17:29 I cancelled it on a PC client, but after the delete confirmation, it faded, but not completely for a long time (and this is my indication that it has not worked).
After around 30 seconds, it drops back to the menu but shows it still recording in the pending screen.
I cancel it again and it works this time.
BUT the first cancel seesm to have stopped it, but it restarts again with a -2 mpeg file.
When the delete works the second time it only deletes the -2 files, leaving the original one orphaned on disk.
recording service and pvrx2 logs attached.

2009-12-08 17:13 recording starts.
17:29 1st manually cancel
17:30:07.953 it restarts its recording
17:31:12 second cancel.

Sadly my sql knowledge is nil, so my chances of spotting why it may have locked are zero.

Martin

[sub]

I've taken a look through that log. I cant see a definite cause. I can see a possible cause, and I've put a fix in for the next release. I cant be 100% sure it'll fix the problem, but hopefully...

[martint123]

Thanks for taking the time to look, fingers crossed the 'possible' is the cause.
The next release sounds like a biggie.