MediaPortal Version: 1.1.3
MediaPortal Skin: Blue3 Wide
Windows Version: Win 7 RC 32bit
CPU Type: Intel Core Duo E8200 2.66 Ghz
HDD: 2xWD 1Tb drives
Memory: Kingston 2x1 Gb
Motherboard: Gigabyte GA-73PVM-S2H GeForce 7100
Video Card: nVidia 9400GT silent
Video Card Driver:
Sound Card:
Sound Card AC3: Optical Out
Sound Card Driver:
1. TV Card: Hauppauge Wintv HVR4000
1. TV Card Type: DVB-S
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: Cyberlink/MPC/ffdshow
MPEG2 Audio Codec:
h.264 Video Codec: Cyberlink/MPC/ffdshow
Satelite/CableTV Provider: Astra 28E
HTPC Case: Antec Fusion
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection: HDMI
I have been having a very occasional problem with TV Server crashing and iI think I have finally identified a common thread. I have some series set up to record "every time on this channel" which is usually OK, but sometimes it seems that when waking up to record a repeat of one that I haven't yet watched (so it's already in the database) things go wrong.
I attach a log of one such failure that I just happened to see yesterday. I know the machine woke up in the afternoon - but I wasn't watching it at the time - then shut down later, as it should. I had another scheduled recording (different program) later that evening and noticed that the machine had not woken up on time. I switched on manually and discovered that TV Service had been lost. I really needed the new recording so did a system reboot (quickest solution) so couldn't totally recreate the situation for full logs.
I attach the TV.bak log from the previous afternoon. This shows that
2011-03-13 16:02:45.988000 [PowerScheduler Waiter(6)]: PowerScheduler: OnResume
it woke up to record, then until
2011-03-13 16:11:13.236000 [scheduler thread(10)]: Scheduler: Schedule 13/03/2011 16:10:00-The Spice Trail (Pepper & Cinnamon) has already been recorded (17/02/2011 20:53:09) - aborting...
it records that this program already exists, then a whole load of stuff I don't understand, ending in
2011-03-13 17:03:29.502000 [TvClient-TvHome: HeartBeat transmitter thread(21)]: RemoteControl - Disconnected st : at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at TvControl.RemoteControl.InvokeEvents()
at TvControl.RemoteControl.RefreshRemotingConnectionStatus()
at TvControl.RemoteControl.get_Instance()
at TvPlugin.TVHome.HeartBeatTransmitter()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
which would be around the time in the afternoon that I noticed the machine was no longer on. The next line
2011-03-13 19:57:21.292000 [TvClient-TvHome: HeartBeat transmitter thread(28)]: TCP connect took : 1000
is when I manually switched on in the evening, before I did the system restart because MP client couldn't see the TV Service.
I really hope someone can identify what is going on here because apart from this occasional fault 1.1.2 (and now 3) have been superbly reliable. This is a real problem because it appears that once this situation has arisen any scheduled wake ups just don't happen. Unfortunately I don't think this is consistent because I'm sure that there are other occasions when repeats are properly handled.
MediaPortal Skin: Blue3 Wide
Windows Version: Win 7 RC 32bit
CPU Type: Intel Core Duo E8200 2.66 Ghz
HDD: 2xWD 1Tb drives
Memory: Kingston 2x1 Gb
Motherboard: Gigabyte GA-73PVM-S2H GeForce 7100
Video Card: nVidia 9400GT silent
Video Card Driver:
Sound Card:
Sound Card AC3: Optical Out
Sound Card Driver:
1. TV Card: Hauppauge Wintv HVR4000
1. TV Card Type: DVB-S
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: Cyberlink/MPC/ffdshow
MPEG2 Audio Codec:
h.264 Video Codec: Cyberlink/MPC/ffdshow
Satelite/CableTV Provider: Astra 28E
HTPC Case: Antec Fusion
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection: HDMI
I have been having a very occasional problem with TV Server crashing and iI think I have finally identified a common thread. I have some series set up to record "every time on this channel" which is usually OK, but sometimes it seems that when waking up to record a repeat of one that I haven't yet watched (so it's already in the database) things go wrong.
I attach a log of one such failure that I just happened to see yesterday. I know the machine woke up in the afternoon - but I wasn't watching it at the time - then shut down later, as it should. I had another scheduled recording (different program) later that evening and noticed that the machine had not woken up on time. I switched on manually and discovered that TV Service had been lost. I really needed the new recording so did a system reboot (quickest solution) so couldn't totally recreate the situation for full logs.
I attach the TV.bak log from the previous afternoon. This shows that
2011-03-13 16:02:45.988000 [PowerScheduler Waiter(6)]: PowerScheduler: OnResume
it woke up to record, then until
2011-03-13 16:11:13.236000 [scheduler thread(10)]: Scheduler: Schedule 13/03/2011 16:10:00-The Spice Trail (Pepper & Cinnamon) has already been recorded (17/02/2011 20:53:09) - aborting...
it records that this program already exists, then a whole load of stuff I don't understand, ending in
2011-03-13 17:03:29.502000 [TvClient-TvHome: HeartBeat transmitter thread(21)]: RemoteControl - Disconnected st : at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at TvControl.RemoteControl.InvokeEvents()
at TvControl.RemoteControl.RefreshRemotingConnectionStatus()
at TvControl.RemoteControl.get_Instance()
at TvPlugin.TVHome.HeartBeatTransmitter()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
which would be around the time in the afternoon that I noticed the machine was no longer on. The next line
2011-03-13 19:57:21.292000 [TvClient-TvHome: HeartBeat transmitter thread(28)]: TCP connect took : 1000
is when I manually switched on in the evening, before I did the system restart because MP client couldn't see the TV Service.
I really hope someone can identify what is going on here because apart from this occasional fault 1.1.2 (and now 3) have been superbly reliable. This is a real problem because it appears that once this situation has arisen any scheduled wake ups just don't happen. Unfortunately I don't think this is consistent because I'm sure that there are other occasions when repeats are properly handled.