Mvpmcx2 Dies Every Night after GBPvr 1.4.7

[tjb]

Not a huge problem, but ever since I upgraded my server to GBPvr version 1.4.7, mvpmcx2 dies every night. Not sure what time this happens. In the morning the PCH is back to the standard screen, and I simply have to restart the process. I thought it might have something to do with the epg update which originally ran at 2:00 AM, but I changed this to run at 7:00PM and it still stops running every night. I should mention that the PCH has a hard drive, so I installed mvpmcx2 using the CSI installer and have updated 1.4.7 with all patches using NMTInstall.

On a side note, and it may or may not be related. But I also have an HTPC client that is set to go into standby whenever it is not in use. The client was also updated to 1.4.7. Since the update, GBPvr seems to have more problems coming out of standby. It used to take only a couple seconds and the screen was refreshed. But now it takes much longer - I get a black screen with no display. Sometimes it takes so long that I just end up killing the pvrx2.exe process and restarting it (which always comes up immediately).

[mvallevand]

The GBPVR logs would show when this happens. I'm suspecting that your server is hibernating overnight because the EPG is no longer run and mvpmcx2 goes back to the main menu when it happens. If you have just moved to CSI and a hard disk install sometimes just having mvpmcx2 running from the share would have prevented hibernation too.

Martin

[tjb]

The server never hibernates or goes into standby. I actually tried to set this up at one time, but the server also has a MagicJack phone attached which prevents standby.

I looked at the event log and saw this:

1:47:56 AM The WinHTTP Web Proxy Auto-Discovery Service entered the stopped state.

and also

3:00:01 AM The GB-PVR Recording Service service was successfully sent a stop control.
3:00:02 AM The GB-PVR Recording Service service entered the stopped state.
3:00:04 AM The GB-PVR Recrding Service service was successfully sent a start control.


Now to find out why this is happening.

[tjb]

Martin,

Thanks for the tips. I found the problem, there was a scheduled task running every night that ended up restarting the Recording Service.

[mvallevand]

That would do it. One thing to note is going back to the main menu might be a good thing, less network activity and no logging on the server could allow some of the energy savings features to activate.

Martin

[tjb]

That would definitely be a good thing - my server is not exactly a "low-power" system. It's an old castoff HP ML150. Maybe once I replace my HTPC with another PCH I can rebuild the server from the old client. It was a much "greener" system.