TV-Server Version: 1.0 RC3
MediaPortal Version: 1.0 RC3
MediaPortal Skin: BlueTwo3
Windows Version: Vista SP1
CPU Type: AMD Athlon 64 5200X2 2.6GHz
HDD: WD 640GB
Memory: 2GB DDR2
Motherboard: ASUS M2N-MX SE
Video Card: NVidia 6100
Video Card Driver: 15.24
Sound Card: Integrated Realtek
Sound Card AC3: no AC3
Sound Card Driver: With motherboard
1. TV Card: Hauppauge Nova T 500
1. TV Card Type: dual DVB-T
1. TV Card Driver: 2.7.25229
2. TV Card: Hauppauge PVR-150
2. TV Card Type: Analog
2. TV Card Driver: 2.7.25229
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: MPV
MPEG2 Audio Codec: MPV
h.264 Video Codec: CoreAVC
Satelite/CableTV Provider:
HTPC Case: Handmade wooden case
Cooling: Standard CPU fan, 1x 120mm, 1x80mm
Power Supply: XPower 400W
Remote: Microsoft MCE USB2
TV: Toshiba 20" LCD
TV - HTPC Connection: Sub-D
So my HTPC failed to record anything last night so I had a look in the logs, and found this:
which continued throughout the error log until the final message at 2008-11-01 00:55:58.93621. 'mchammer' is the name of the machine. In this middle of the error log there is a long message relating to SQL, see attached log for details.
I tried this morning and the machine worked properly, it looks like it fixed itself. However I would like to know what might have caused this to try and stop it happening again. I have had a google, and looked at other support threads and some of the bug reports and don't see anything similar. I have attached complete logs, there are other errors in the _tv and _TSWriter files that may or may not be related.
Does anyone know what could have caused this? Should I be fileing a bug report or is this something with my machine? It is worth noting, although it may not be related, that this machine has difficulty maintaining a steady network connection, which was again broken when I woke up this morning (the recording was from last night in NZ time). However this hasd never affected recording before and I don't see why it should.
MediaPortal Version: 1.0 RC3
MediaPortal Skin: BlueTwo3
Windows Version: Vista SP1
CPU Type: AMD Athlon 64 5200X2 2.6GHz
HDD: WD 640GB
Memory: 2GB DDR2
Motherboard: ASUS M2N-MX SE
Video Card: NVidia 6100
Video Card Driver: 15.24
Sound Card: Integrated Realtek
Sound Card AC3: no AC3
Sound Card Driver: With motherboard
1. TV Card: Hauppauge Nova T 500
1. TV Card Type: dual DVB-T
1. TV Card Driver: 2.7.25229
2. TV Card: Hauppauge PVR-150
2. TV Card Type: Analog
2. TV Card Driver: 2.7.25229
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: MPV
MPEG2 Audio Codec: MPV
h.264 Video Codec: CoreAVC
Satelite/CableTV Provider:
HTPC Case: Handmade wooden case
Cooling: Standard CPU fan, 1x 120mm, 1x80mm
Power Supply: XPower 400W
Remote: Microsoft MCE USB2
TV: Toshiba 20" LCD
TV - HTPC Connection: Sub-D
So my HTPC failed to record anything last night so I had a look in the logs, and found this:
Code:
2008-10-31 18:50:59.774210 [18]: card: unable to connect to slave controller at:mchammer
2008-10-31 18:51:01.087210 [10]: card: unable to connect to slave controller at:mchammer
2008-10-31 18:55:59.280210 [10]: card: unable to connect to slave controller at:mchammer
2008-10-31 18:56:01.471210 [18]: card: unable to connect to slave controller at:mchammer
2008-10-31 19:21:00.130210 [9]: card: unable to connect to slave controller at:mchammer
which continued throughout the error log until the final message at 2008-11-01 00:55:58.93621. 'mchammer' is the name of the machine. In this middle of the error log there is a long message relating to SQL, see attached log for details.
I tried this morning and the machine worked properly, it looks like it fixed itself. However I would like to know what might have caused this to try and stop it happening again. I have had a google, and looked at other support threads and some of the bug reports and don't see anything similar. I have attached complete logs, there are other errors in the _tv and _TSWriter files that may or may not be related.
Does anyone know what could have caused this? Should I be fileing a bug report or is this something with my machine? It is worth noting, although it may not be related, that this machine has difficulty maintaining a steady network connection, which was again broken when I woke up this morning (the recording was from last night in NZ time). However this hasd never affected recording before and I don't see why it should.