Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1104679" data-attributes="member: 82144">Hello again CamI very much doubt it would help.Like I said: it looks like the start of the problems was TV Server losing contact with your tuners. It is basically impossible for me to determine why that might have happened from TV Server logs. The TV Server could be at fault; the tuner could be at fault; something else could be at fault. I simply don't know.The only thing that would help to investigate a problem like this would be a Wireshark dump from the time of the problem (Wireshark is an application that captures network traffic). Since we can't go back in time and get that dump, there's nothing further that I can do to help with that specific error event.Looking forward...If this problem is happening on a regular basis then I would recommend to install Wireshark and start capturing to catch the next error event. Note that unless configured to do otherwise, Wireshark will capture all network traffic... which means if it takes a long time (more than a minute or two) for the problem to occur again you could end up with a huge capture file which would be impractical for me to analyse. I'm limited to a 10 GB per month internet cap, and I'm also limited in time. So, we'd need to find a way to produce a small/concise capture/dump file.Regards,mm</blockquote>

[QUOTE="mm1352000, post: 1104679, member: 82144"] Hello again Cam I very much doubt it would help. Like I said: it looks like the start of the problems was TV Server losing contact with your tuners. It is basically impossible for me to determine why that might have happened from TV Server logs. The TV Server could be at fault; the tuner could be at fault; something else could be at fault. I simply don't know. The only thing that would help to investigate a problem like this would be a Wireshark dump from the time of the problem (Wireshark is an application that captures network traffic). Since we can't go back in time and get that dump, there's nothing further that I can do to help with that specific error event. Looking forward... If this problem is happening on a regular basis then I would recommend to install Wireshark and start capturing to catch the next error event. Note that unless configured to do otherwise, Wireshark will capture all network traffic... which means if it takes a long time (more than a minute or two) for the problem to occur again you could end up with a [I]huge[/I] capture file which would be impractical for me to analyse. I'm limited to a 10 GB [I]per month[/I] internet cap, and I'm also limited in time. So, we'd need to find a way to produce a small/concise capture/dump file. Regards, mm [/QUOTE]

Verification