TV-Servers crashes every night (1 Viewer)

[mm1352000]

And again a crash. EPG (while idle) disabled, no plugin enabled.



I think it was just after a recording started.

...and if you look at the TsWriter log file:
[collapse]01-05-2013 16:20:14.758 Recorder: RECORD set filename:Z:\Recordings\RTL Passion\Die Chaosfamilie\Die Chaosfamilie - 2013-05-01_5.ts
01-05-2013 16:20:14.758 Recorder: RECORD Received from TvService: pmt pid:0x63 serviceId: 0x1d pmtlength:117
01-05-2013 16:20:14.758 Recorder: RECORD Old pids cleared
01-05-2013 16:20:14.758 Recorder: RECORD got pmt - tableid: 0x2 section_length: 114 sid: 0x1d
01-05-2013 16:20:14.758 Recorder: RECORD PMT parsed - Pid 0x63 ServiceId 0x1d stream count: 3
01-05-2013 16:20:14.773 Recorder: RECORD pcr pid:0xff
01-05-2013 16:20:14.773 Recorder: RECORD SetPcrPid clear old PIDs
01-05-2013 16:20:14.773 Recorder: RECORD add teletext stream pid: 0x20 fake pid: 0x64 stream type: 0x6 logical type: 0x56 descriptor length: 10
01-05-2013 16:20:14.773 Recorder: RECORD add video stream pid: 0xff fake pid: 0x30 stream type: 0x2 logical type: 0x2 descriptor length: 3
01-05-2013 16:20:14.773 Recorder: RECORD add audio stream pid: 0x100 fake pid: 0x40 stream type: 0x3 logical type: 0x3 descriptor length: 9
01-05-2013 16:20:14.773 Recorder: RECORD SetVideoAudioObserver observer ok
01-05-2013 16:20:14.773 Recorder: RECORD Start 'Z:\Recordings\RTL Passion\Die Chaosfamilie\Die Chaosfamilie - 2013-05-01_5.ts'
01-05-2013 16:20:14.789 Recorder: RECORD start of video detected
01-05-2013 16:20:14.789 Recorder: RECORD clear TS packet queue
01-05-2013 16:20:14.789 CDiskRecorder::WriteToRecording() - Reset write buffer throttle
01-05-2013 16:20:14.804 Recorder: RECORD Info : Next broadcaster program clock reference rollover : 0 days 04:27:25 0
01-05-2013 16:20:14.867 Recorder: RECORD start of audio detected
01-05-2013 16:20:14.898 epg: set callback
01-05-2013 16:20:14.898 EpgScanner::GrabEPG
01-05-2013 16:20:14.898 epg:GrabEPG
01-05-2013 16:20:14.914 epg:ResetEPG()
01-05-2013 16:20:14.914 epg:GrabEPG()
01-05-2013 16:20:14.914 EpgScanner::GrabMHW
01-05-2013 16:20:14.914 mhw grab
01-05-2013 16:20:14.914 mhw reset
01-05-2013 16:20:14.914 mhw grabber started decoders:2
01-05-2013 16:20:16.101 *** epgecodeExtendedEvent check 1[/collapse]
Clearly the timeshifting EPG grabber is still enabled, and it is still the EPG grabber causing this crash.

And again. This time the EPG grabber finished long before the TV server crashed.

The same can be seen in these logs too:

[collapse]01-05-2013 18:35:07.588 Recorder: RECORD set filename:Z:\Recordings\RTL Passion\Die Chaosfamilie\Die Chaosfamilie - 2013-05-01_7.ts
01-05-2013 18:35:07.603 Recorder: RECORD Received from TvService: pmt pid:0x63 serviceId: 0x1d pmtlength:117
01-05-2013 18:35:07.603 Recorder: RECORD Old pids cleared
01-05-2013 18:35:07.603 Recorder: RECORD got pmt - tableid: 0x2 section_length: 114 sid: 0x1d
01-05-2013 18:35:07.603 Recorder: RECORD PMT parsed - Pid 0x63 ServiceId 0x1d stream count: 3
01-05-2013 18:35:07.619 Recorder: RECORD pcr pid:0xff
01-05-2013 18:35:07.619 Recorder: RECORD SetPcrPid clear old PIDs
01-05-2013 18:35:07.619 Recorder: RECORD add teletext stream pid: 0x20 fake pid: 0x62 stream type: 0x6 logical type: 0x56 descriptor length: 10
01-05-2013 18:35:07.619 Recorder: RECORD add video stream pid: 0xff fake pid: 0x30 stream type: 0x2 logical type: 0x2 descriptor length: 3
01-05-2013 18:35:07.619 Recorder: RECORD add audio stream pid: 0x100 fake pid: 0x40 stream type: 0x3 logical type: 0x3 descriptor length: 9
01-05-2013 18:35:07.619 Recorder: RECORD SetVideoAudioObserver observer ok
01-05-2013 18:35:07.619 Recorder: RECORD Start 'Z:\Recordings\RTL Passion\Die Chaosfamilie\Die Chaosfamilie - 2013-05-01_7.ts'
01-05-2013 18:35:07.635 Recorder: RECORD start of video detected
01-05-2013 18:35:07.666 Recorder: RECORD start of audio detected
01-05-2013 18:35:07.681 Recorder: RECORD clear TS packet queue
01-05-2013 18:35:07.681 CDiskRecorder::WriteToRecording() - Reset write buffer throttle
01-05-2013 18:35:07.681 Recorder: RECORD Info : Next broadcaster program clock reference rollover : 0 days 02:12:33 0
01-05-2013 18:35:07.681 epg: set callback
01-05-2013 18:35:07.681 EpgScanner::GrabEPG
01-05-2013 18:35:07.697 epg:GrabEPG
01-05-2013 18:35:07.697 epg:ResetEPG()
01-05-2013 18:35:07.697 epg:GrabEPG()
01-05-2013 18:35:07.697 EpgScanner::GrabMHW
01-05-2013 18:35:07.697 mhw grab
01-05-2013 18:35:07.697 mhw reset
01-05-2013 18:35:07.697 mhw grabber started decoders:2[/collapse]

Clearly the EPG grabber is causing the crashes... so disable it completely please.
Both the idle and timeshifting EPG grabber share the same code, so it makes sense that both would crash... and therefore both must be disabled if you want TV Server to be stable.

It seems the data that the EPG grabber thinks is EPG data is not actually EPG data, or it is in a format that is not supported.
Please supply a TS dump so that the stream content can be analysed:
http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/4_Development/Debugging/TS_Dumps

mm

 

[mckirk]

I disabled EPG while timeshifting so both EPG options are now off. I created a dump, it is currently uploading to the FTP server. The file is called "DE_SKY_12070MHz_S_scrambled.ts".

I just restarted the TV server after disabling the dump option and started a timeshift in order to check that no dump is generated. Right after clicking "Start TimeShift" in SetupTV.exe the server crashed again. I attached the log files.

Thanks for your help.

Edit: The file is uploaded now.

 

[mm1352000]

Hello again

I've found the reason why all the messages are present in your TsWriter log file.
It is because there is a certain stream with PID 768 (0x300) present on that transponder.
That PID is recognised as an EPG for Dish TV, which is a satellite TV provider in North America.
On your transponder that PID is carrying audio, not EPG data.

Attempting to decode audio as EPG is probably not going to work so well.
So the question is how to avoid treating that PID as EPG. Well, right now I'm not sure...

mm

 

[mckirk]

Great, at least there is an idea about the problem. Since this is Astra 19,2 there should be a bunch of users out there having the same issues.

I am pretty sure that there are several german channels having an audio stream with PID 768, one in nearly every transponder.

Just a long shot: shouldn't the EPG grabber robust enough not to crash even when wrong data is coming in?

 

[mm1352000]

Just a long shot: shouldn't the EPG grabber robust enough not to crash even when wrong data is coming in?

Yes. The problem would be: how to find the point where the crash is occurring?
I am based in NZ => no access to that satellite, makes it difficult to test.
Your logs don't show enough info either.
I guess I could build a debug version for you...

How long does it usually take for a crash to occur?
Would it be possible to connect to your computer using TeamViewer to run some tests?

 

[mckirk]

It usually crashes when a recording is running and no client is connected. As long as a client is streaming I am pretty sure there was no crash at all. Since most of the recordings are during the night the service is just not running when I check in the morning. I could try to manually tune to one of the critical transponders.

TeamViewer would be no problem. I am going to install it.[DOUBLEPOST=1367486497][/DOUBLEPOST]Skype: danielkbx

 

[mm1352000]

Just installing skype and creating debug TsWriter. Will contact shortly...

 

[Vasilich]

i am also in Germany, but have no problems with EPG. The only difference to @mckirk is that i don't have subscription for Sky.

 

[The_Stig]

Hrm, gotta check logs. I am here in good ol' Germany on DVB-S and Sky too. From time to time I have crashes too, but didnt have the time to check logs, so cannot say if its the same issue. What and where should I look for on next crash? Tswriter-Log for what exactly?

 

[mm1352000]

I think the TeamViewer session was really helpful. We proved that the EPG grabber seems to be pretty stable.
After checking the system application log, we could see that the cause of many/most of the TvService.exe crashes was A***D (used with M****).