<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>
Thanks, I will look try do a little logging to see if the issue is reported. <br><br>--Daniel<br><br><blockquote><hr>Date: Wed, 11 Jul 2007 12:58:12 -0700<br>From: trgreer@gmail.com<br>To: mythtv-users@mythtv.org<br>Subject: Re: [mythtv-users] MythTV Frontend: frequent disconnections<br><br>On 7/11/07, <b class="EC_gmail_sendername">Charles Waddell</b> <<a href="mailto:daniel_waddell01@hotmail.com">daniel_waddell01@hotmail.com</a>> wrote:<div><span class="EC_gmail_quote"></span><blockquote class="EC_gmail_quote" style="padding-left: 1ex;">
<div>
I am running a mythtv backend server on Fedora Core 6, installed using the RPM at version 0.20.1-157 and setting on my network's DMZ. One of my frontends is running on an XBOX (Xebian) with the frontend package version at
0.20-0.3.<br><br>The problem that I am experiencing is with frequent disconnects. I can start mythfrontend fine, I can navigate to live tv, or to a recorded program without issue. I can also watch either category. However, if I set idle for around 20 minutes (rough estimate), I lose connection with the backend. If I am watching a show, the program continues to run without issue, but when I go to a menu or navigate to recordings the system hangs. In order to reestablish a connection, I have to kill the frontend application, and restart it (which is incredibly slow on an XBOX). I know that I have disconnected because the last line of the console states that I disconnected from the server (I will try to post the exact output when I get off of work). Do you think this is a versioning problem, or is there something wrong with my configuration, or is it maybe a networking issue? Thanks for your help.
<br><br>-- Daniel<br></div></blockquote></div><br>The only way to troubleshoot this is to start inspecting your log files. <br><br>If this is a MythTV problem, then your mythbackend log should give you a clue. You may need to run mythfrontend from a command line (or specify a logfile) to see what error messages it is generating.
<br><br>If not, then start looking in the other log files (typically in the /var/log/ directory) on both the front and back ends. Once you can find the underlying error(s), then Google can provide solutions.<br><br>Tom<br>
</blockquote><br /><hr />Local listings, incredible imagery, and driving directions - all in one place! <a href='http://maps.live.com/?wip=69&FORM=MGAC01' target='_new'>Find it!</a></body>
</html>