Logs

[jcjefferies]

My NPVR computer will no longer sleep so I looked at the NPVR logs for clues. Looking at an old NPVR.log which started at 1900 and filled up in 4 hours with entries like the one below:-

2011-02-26 07:56:56.203 [DEBUG][1] PlaybackPositionHelper.GetLastPlaybackDate(D:\The Simpsons\The Simpsons_20110225_18001830.ts)

Every 2 minutes it was printing out over 100 items which is about the number of recordings I have. Around 20:45 it reduced the number to 19 recordings and continued at that rate until I put it into standby manually this morning. It later woke to do a recording but did not sleep afterwards and its still adding 19 items to the log every 2 mins.

I noticed that the overnight NPVR.log contained just these entries and not recordings and the EPG update. I then noticed that the NRecord logs which I have not seen used before were full. The two oldest logs filled up in 15-20 minutes and contained Client Reads from when I watched a programme via the client. In later logs are two recordings and the EPG update which took place in the middle of a recording so the EPG update details were shorter and different to the usual update. Previously recordings and EPG updates have appeared in the NPVR.log.

Chris
Chris

[sub]

Do you member which screen you were in at the time you getting these PlaybackPositionHelper.GetLastPlaybackDate() messages? It doesnt generate these messages when you browsing the recording screen and the video library, since it uses the playback position to determine if it should display the 'already watched' indicator. These messages shouldnt recur without someone browsing these screens though.

[sub]

I noticed that the overnight NPVR.log contained just these entries and not recordings and the EPG update. I then noticed that the NRecord logs which I have not seen used before were full. The two oldest logs filled up in 15-20 minutes and contained Client Reads from when I watched a programme via the client. In later logs are two recordings and the EPG update which took place in the middle of a recording so the EPG update details were shorter and different to the usual update. Previously recordings and EPG updates have appeared in the NPVR.log.

npvr.log is the front end user interface. nrecord.log is the recording service, also used for automated epg updates, client/server stuff etc.

[jcjefferies]

I can confirm that it does this if you leave the menu in "Recordings" but what it outputs is dependant on which area you are in. If you are under "Whats New" it will output the 20 recordings listed. If I leave it in "Ready Recordings" it outputs a full list recordings in my case about 100 items every 2 minutes. Under "Pending Recordings it just seems to print what is currently being recorded. So it looks as if the answer is to exit to the main menu when not in use to avoid filling up the logs.

I dont yet know if this output to the logs was preventing it going into standby mode but I can now monitor the situation. I always display the "Logs" directory in date order to see which has had recent output and previously the NPVR.log "seemed" to be the only one producing anything more than a few startup lines but I must be mistaken.

Thanks Sub, this has helped me understand better what is going on.

Chris

[sub]

I can confirm that it does this if you leave the menu in "Recordings" but what it outputs is dependant on which area you are in. If you are under "Whats New" it will output the 20 recordings listed. If I leave it in "Ready Recordings" it outputs a full list recordings in my case about 100 items every 2 minutes. Under "Pending Recordings it just seems to print what is currently being recorded. So it looks as if the answer is to exit to the main menu when not in use to avoid filling up the logs.

I dont yet know if this output to the logs was preventing it going into standby mode but I can now monitor the situation. I always display the "Logs" directory in date order to see which has had recent output and previously the NPVR.log "seemed" to be the only one producing anything more than a few startup lines but I must be mistaken.

Thanks Sub, this has helped me understand better what is going on.

Chris

This is now fixed in the next release. I've added logic to make sure it doesnt recheck the playback position every 2 minutes.