2010-05-30, 09:28 PM
This problem has occurred twice in the last week, each time at the weekend
The recording service locks up. It seems to try to start a recording and never finishes. Result is that 24 hours later the status page says it is still recording the programme in question - when it finshed long ago - and all subsequent recording requests are ignored. The only way to get out of this is to either hard reset or stop the last GBPVR process through task manager, then do a software restart - if I don't stop all the GBPVR processes a software restart doesn't happen. The first time I thought it must be some hardware glitch, but now it looks like a GBPVR problem to me. One odd thing, I tried stopping GBPVR through the 'stop recording service' command which worked for everything but the iplayer process, which i had to stop through task manager. I don't use iplayer. it doesn't work (see my posts of six months ago), but I don't know how to get it out of the system. Maybe its this that is casuing the problem, though why it should have started now i don't know
Attached is a set of the logs. They were taken after the restart so the recordingserice -1 are the ones to look at
The recording service locks up. It seems to try to start a recording and never finishes. Result is that 24 hours later the status page says it is still recording the programme in question - when it finshed long ago - and all subsequent recording requests are ignored. The only way to get out of this is to either hard reset or stop the last GBPVR process through task manager, then do a software restart - if I don't stop all the GBPVR processes a software restart doesn't happen. The first time I thought it must be some hardware glitch, but now it looks like a GBPVR problem to me. One odd thing, I tried stopping GBPVR through the 'stop recording service' command which worked for everything but the iplayer process, which i had to stop through task manager. I don't use iplayer. it doesn't work (see my posts of six months ago), but I don't know how to get it out of the system. Maybe its this that is casuing the problem, though why it should have started now i don't know
Attached is a set of the logs. They were taken after the restart so the recordingserice -1 are the ones to look at