VERBOSE [3] VOL: 45875 (range: 0 - 65535)

[alpax]

Last night my GBPVR became quite slow without any noticeable reason. I tried to close it and start again. It was starting incredibly slowly - the UI showed in about a minute, then another minute or two it was frozen and did not react to any button presses.
I checked the log and found a lot of messages like in the subject. I left it running overnight and in the morning 8MB of log files were filled with this message:

Code:

...
20/11/2006 9:03:08 AM.031    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)
20/11/2006 9:03:08 AM.234    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)
20/11/2006 9:03:08 AM.437    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)
20/11/2006 9:03:08 AM.640    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)
20/11/2006 9:03:08 AM.843    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)
20/11/2006 9:03:09 AM.046    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)
20/11/2006 9:03:09 AM.234    VERBOSE    [3]    VOL: 45875     (range: 0 - 65535)

What is this and how can I fix it?

I'm attaching the first log file, which has some other info before all these lines - maybe it will help.

Forgot to mention - I'm running GB-PVR v0.98.13, and using the following plugins: TV Listings, XRecord, MyVideos, MyMusic, Weather, and CommunitySkin. And this setup has been working pretty well for about a month.

[sub]

Its annoying log message, removed for the next release, but I'm pretty sure it wont be the cause of your problem. From memory, you can get rid of the messages by setting the volume setting to 'local volume' in the config app.

The logs dont grow infinitely, they just grow to a configurable size, then roll over to a new file - deleting the oldest of three backups.

[alpax]

Thank you for the response, sub.
I'm not worried about the log size - I see that it doesn't take more than four 2MB files.
But there is still something wrong with my installation. Don't you see anything suspicious in the log attached?
There are some errors "Unable to find node", and "The database file is locked". The latter is probably not the main problem though - I guess it's caused by something else, some process, which locks the database, and that one is probably the real issue.

[sub]

I just looked now. There does seem to be a database lock error:

20/11/2006 4:07:27 AM.531 ERROR [1] Unexpected error rendering panel: The database file is locked
database is locked
20/11/2006 4:07:27 AM.531 ERROR [1] at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteDataReader.NextResult()
at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
at System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.ExecuteReader()
at GBPVR.Backend.Common.x396614b3dae3b1da.x005239145b965dc1()
at GBPVR.Panels.x18f56f732cd3e8b1.panelNeedsRendering()
at GBPVR.x86396f56243de9fb.xb1cbc922a07ef39b()

I'm guessing this relates to post number #7 of the stick 'v0.98.13 survival guide' thread? http://forums.nextpvr.com/showthread.php?t=19525. If not, zip and attach a complete set of logs and I'll take a look.

[alpax]

Just an update on this.
The issue with slowdown had gone all by itself. That wasn't related to auto convert to another format as mentioned in the referenced thread (I don't use that feature), but probably something else with the database. We just watched then deleted some recordings, and apparently it fixed the problem.

The message about volume was still there though (it changed to "VOL: 65535" - I guess I actually changed the volume some time), but it also stopped spamming the log last evening for some reason.

I'll be watching it - will provide more info if it will happen again.