<div>I think I figured out the remote system problem. I wasn't aware that you don't need to run a database on the remote system. Once I turned that off, and re set everything up between the master and slave boxes, the delete problem, and the inability to jump forward and back cleared up.
</div>
<div> </div>
<div>Now, I have a different problem, though. The tuner on the slave backend shows as 'not available' in system status. </div>
<div> </div>
<div>Any ideas there? both master and slave backends are running. nothing is recording, it's just 'not available'<br><br> </div>
<div><span class="gmail_quote">On 12/8/05, <b class="gmail_sendername">Kirk Davis</b> <<a href="mailto:Kirk.Davis@epsb.ca">Kirk.Davis@epsb.ca</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>> -----Original Message-----<br>> On Tue, 2005-12-06 at 16:49 -0500, Mike Frisch wrote:<br>> > On Mon, Dec 05, 2005 at 11:26:44PM -0800, Jeff Clemens wrote:
<br>> > > So occasionally, my master backend gets into a strange<br>> state. I have a<br>> > > frontend and a backend running on each of 2 boxes.<br>> The master backend<br>> > > occasionally gets into a state where the frontend will
<br>> report that the<br>> > > backend is down when trying some things (like deleting<br>> a recording for<br>> > > instance), but other menu items that use the backend<br>> work fine. When it's
<br>> > > in this state, neither frontend works correctly.<br>> > > /sbin/service mythbackend restart fixes the problem<br>> temporarily.<br>> ><br>> > I cannot offer much other than to say the same thing
<br>> happens regularly<br>> > to me. I cannot predict when it will happen but it happens somewhat<br>> > frequently. It is as if the frontend loses track of the backend.<br>><br>> I think this is what has happened to me on a few occasions,
<br>> the backend<br>> has stopped recording, the status page works still works but the<br>> frontend won't play but lists all the shows etc.<br>><br>> Again a rcmythbackend restart fixed but I didn't discover
<br>> exactly why it<br>> happened.<br><br> My system is also having the same problem. It seems to loose the<br>connection with the backend when I try to delete a recording. The<br>frontend will eventualy time out but I have to restart the backend.
<br><br> Here is some more information about my system that might help some<br>one track this problem down.<br> Running on FC4 (2.6.14-1.1644_FC4smp) on a P4 3Gig with 1 Gig of<br>RAM.<br> Myth 18.1 from atrpms about 2 weeks ago.
<br> Two capture devices. A PVR-150 and a firewire connection to a<br>DCT-6200 cable box.<br> The system is setup right off of Jarod's How-to from<br><a href="http://www.wilsonet.com/mythtv/fcmyth.php">http://www.wilsonet.com/mythtv/fcmyth.php
</a><br> I'm using JFS for the filesystem that stores the recordings.<br> Here are the ivtv packages that I am using:<br> ivtv.i386 1:<a href="http://0.4.0-98.rhfc4.at">0.4.0-98.rhfc4.at
</a><br>installed<br> ivtv-firmware-audio.i386 <a href="http://0.0.1-1.at">0.0.1-1.at</a><br>installed<br> ivtv-firmware-dec.i386 <a href="http://2.02.023-4.at">2.02.023-4.at</a>
<br>installed<br> ivtv-firmware-enc.i386 <a href="http://2.04.024-4.at">2.04.024-4.at</a><br>installed<br> ivtv-kmdl-2.6.14-1.1644_FC4smp.i686 1:<a href="http://0.4.0-98.rhfc4.at">0.4.0-98.rhfc4.at
</a><br>installed<br><br> I hope this information helps. I just built up this new system. The<br>old system was working without a hitch for almost 2 years.<br><br>---- Kirk<br><br><br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br><br><br></blockquote></div><br>