Re: [mythtv-users] Re: Strange MythBackend troubles

2005-12-09 Thread Jeff Clemens
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.


Now, I have a different problem, though. The tuner on the slave backend shows as 'not available' in system status. 

Any ideas there? both master and slave backends are running. nothing is recording, it's just 'not available'
On 12/8/05, Kirk Davis [EMAIL PROTECTED] wrote:
 -Original Message- On Tue, 2005-12-06 at 16:49 -0500, Mike Frisch wrote:  On Mon, Dec 05, 2005 at 11:26:44PM -0800, Jeff Clemens wrote:
  So occasionally, my master backend gets into a strange state. I have a  frontend and a backend running on each of 2 boxes. The master backend  occasionally gets into a state where the frontend will
 report that the  backend is down when trying some things (like deleting a recording for  instance), but other menu items that use the backend work fine.When it's
  in this state, neither frontend works correctly.  /sbin/service mythbackend restart fixes the problem temporarily.   I cannot offer much other than to say the same thing
 happens regularly  to me.I cannot predict when it will happen but it happens somewhat  frequently.It is as if the frontend loses track of the backend. I think this is what has happened to me on a few occasions,
 the backend has stopped recording, the status page works still works but the frontend won't play but lists all the shows etc. Again a rcmythbackend restart fixed but I didn't discover
 exactly why it happened. My system is also having the same problem.It seems to loose theconnection with the backend when I try to delete a recording. Thefrontend will eventualy time out but I have to restart the backend.
 Here is some more information about my system that might help someone track this problem down. Running on FC4 (2.6.14-1.1644_FC4smp) on a P4 3Gig with 1 Gig ofRAM. Myth 18.1from atrpms about 2 weeks ago.
 Two capture devices.A PVR-150 and a firewire connection to aDCT-6200 cable box. The system is setup right off of Jarod's How-to fromhttp://www.wilsonet.com/mythtv/fcmyth.php
 I'm using JFS for the filesystem that stores the recordings. Here are the ivtv packages that I am using: ivtv.i3861:0.4.0-98.rhfc4.at
installed ivtv-firmware-audio.i386 0.0.1-1.atinstalled ivtv-firmware-dec.i386 2.02.023-4.at
installed ivtv-firmware-enc.i386 2.04.024-4.atinstalled ivtv-kmdl-2.6.14-1.1644_FC4smp.i6861:0.4.0-98.rhfc4.at
installed I hope this information helps. I just built up this new system.Theold system was working without a hitch for almost 2 years. Kirk___
mythtv-users mailing listmythtv-users@mythtv.orghttp://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] Re: Strange MythBackend troubles

2005-12-09 Thread f-myth-users
Date: Fri, 9 Dec 2005 16:58:53 -0800
From: Jeff Clemens [EMAIL PROTECTED]

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.

So in other words, mysql is no longer running on your slave backend
at all?  (My SBE [which is also my FE] has mysql still running; it
hadn't occurred to me that this is a problem, and in fact I thought
that certain SBE/FE settings were stored locally.  Where -is- this
info stored?  Should I disable mysql on my SBE/FE, too?  I should
point out that I have no problems deleting things...)

Now, I have a different problem, though.  The tuner on the slave backend
shows as 'not available' in system status.

Any ideas there?  both master and slave backends are running.  nothing is
recording, it's just 'not available'

If I boot my MBE, my SBE/FE always claims that its tuner is
not available unless I boot the SBE.  I bug-reported this
dependency a few weeks ago on this list but it generated no
response (except, well, just restart mythbackend on the SBE
instead of any idea of whether this was even viewed as a bug
at all).  This means I have to be careful to boot my SBE only
after my MBE is actually up, which complicates recovery from
power failures (of which I just had one today, actually), and
especially unattended recovery.

[And after booting the MBE without rebooting the SBE, certain UI
operations work, but some complain that the backend has gone away;
if I just okay that popup and continue, the SBE/FE recovers and
notices that the MBE is there.  But the SBE's tuner is permanently
unavailable unless the SBE is restarted.]

So have you tried rebooting your SBE and/or restarting mythfrontend?
Does this help?

P.S.  This is all in 0.18.1, not SVN.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Re: Strange MythBackend troubles

2005-12-09 Thread Greg Estabrooks
 hadn't occurred to me that this is a problem, and in fact I thought
 that certain SBE/FE settings were stored locally.  Where -is- this
 info stored?  Should I disable mysql on my SBE/FE, too?  I should

 Everything for all frontends/backends is stored in the single database
pointed to by your mysql.txt

 at all).  This means I have to be careful to boot my SBE only
 after my MBE is actually up, which complicates recovery from

 Can't speak for 0.18 but I regularly shutdown the master backend
and my slave reconnects happily once the master is backup.


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Re: Strange MythBackend troubles

2005-12-09 Thread Sasha Z
Are you sure you guys aren't experiencing the same problems as I am in
this thread?

http://www.gossamer-threads.com/lists/mythtv/users/164194

What do your backend logs say?

On 12/9/05, Greg Estabrooks [EMAIL PROTECTED] wrote:
  hadn't occurred to me that this is a problem, and in fact I thought
  that certain SBE/FE settings were stored locally.  Where -is- this
  info stored?  Should I disable mysql on my SBE/FE, too?  I should

  Everything for all frontends/backends is stored in the single database
 pointed to by your mysql.txt

  at all).  This means I have to be careful to boot my SBE only
  after my MBE is actually up, which complicates recovery from

  Can't speak for 0.18 but I regularly shutdown the master backend
 and my slave reconnects happily once the master is backup.




 ___
 mythtv-users mailing list
 mythtv-users@mythtv.org
 http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] Re: Strange MythBackend troubles

2005-12-09 Thread f-myth-users
Date: Fri, 9 Dec 2005 21:39:47 -0500
From: Sasha Z [EMAIL PROTECTED]

Are you sure you guys aren't experiencing the same problems as I am in
this thread?

http://www.gossamer-threads.com/lists/mythtv/users/164194

Well, I don't think -I- am.  The only time I've noticed that the
SBE/FE can't talk to the MBE is after I've rebooted the MBE, and that
situation clears up for the FE as soon as I've acknowledged the popup
that there's a problem.  (That popup can come at irritating times,
though---like -after- I've already entered all the information for a
manual schedule, whereupon it drops all that info on the floor as soon
as I've cleared the condition and leaves me with the default page again.)

OTOH, the SBE's tuner is permanently unavailable until I reboot the SBE.

So this doesn't seem to be the same randomly goes away problem that
you're reporting.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


RE: [mythtv-users] Re: Strange MythBackend troubles

2005-12-08 Thread Kirk Davis
 

 -Original Message-
 On Tue, 2005-12-06 at 16:49 -0500, Mike Frisch wrote:
  On Mon, Dec 05, 2005 at 11:26:44PM -0800, Jeff Clemens wrote:
  So occasionally, my master backend gets into a strange 
 state.   I have a
  frontend and a backend running on each of 2 boxes.  
 The master backend
  occasionally gets into a state where the frontend will 
 report that the
  backend is down when trying some things (like deleting 
 a recording for
  instance), but other menu items that use the backend 
 work fine.  When it's
  in this state, neither frontend works correctly.
  /sbin/service mythbackend restart fixes the problem 
 temporarily.
  
  I cannot offer much other than to say the same thing 
 happens regularly
  to me.  I cannot predict when it will happen but it happens somewhat
  frequently.  It is as if the frontend loses track of the backend.
 
 I think this is what has happened to me on a few occasions, 
 the backend
 has stopped recording, the status page works still works but the
 frontend won't play but lists all the shows etc.
 
 Again a rcmythbackend restart fixed but I didn't discover 
 exactly why it
 happened.

My system is also having the same problem.  It seems to loose the
connection with the backend when I try to delete a recording. The
frontend will eventualy time out but I have to restart the backend. 

Here is some more information about my system that might help some
one track this problem down.
Running on FC4 (2.6.14-1.1644_FC4smp) on a P4 3Gig with 1 Gig of
RAM.
Myth 18.1  from atrpms about 2 weeks ago.
Two capture devices.  A PVR-150 and a firewire connection to a
DCT-6200 cable box.  
The system is setup right off of Jarod's How-to from
http://www.wilsonet.com/mythtv/fcmyth.php
I'm using JFS for the filesystem that stores the recordings.
Here are the ivtv packages that I am using:
ivtv.i3861:0.4.0-98.rhfc4.at
installed   
ivtv-firmware-audio.i386 0.0.1-1.at
installed   
ivtv-firmware-dec.i386   2.02.023-4.at
installed   
ivtv-firmware-enc.i386   2.04.024-4.at
installed   
ivtv-kmdl-2.6.14-1.1644_FC4smp.i686  1:0.4.0-98.rhfc4.at
installed   

I hope this information helps. I just built up this new system.  The
old system was working without a hitch for almost 2 years.

 Kirk
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] Re: Strange MythBackend troubles

2005-12-06 Thread Mike Frisch
On Mon, Dec 05, 2005 at 11:26:44PM -0800, Jeff Clemens wrote:
So occasionally, my master backend gets into a strange state.   I have a
frontend and a backend running on each of 2 boxes.  The master backend
occasionally gets into a state where the frontend will report that the
backend is down when trying some things (like deleting a recording for
instance), but other menu items that use the backend work fine.  When it's
in this state, neither frontend works correctly.
/sbin/service mythbackend restart fixes the problem temporarily.

I cannot offer much other than to say the same thing happens regularly
to me.  I cannot predict when it will happen but it happens somewhat
frequently.  It is as if the frontend loses track of the backend.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Re: Strange MythBackend troubles

2005-12-06 Thread Druid
On Tue, 2005-12-06 at 16:49 -0500, Mike Frisch wrote:
 On Mon, Dec 05, 2005 at 11:26:44PM -0800, Jeff Clemens wrote:
 So occasionally, my master backend gets into a strange state.   I have a
 frontend and a backend running on each of 2 boxes.  The master backend
 occasionally gets into a state where the frontend will report that the
 backend is down when trying some things (like deleting a recording for
 instance), but other menu items that use the backend work fine.  When 
  it's
 in this state, neither frontend works correctly.
 /sbin/service mythbackend restart fixes the problem temporarily.
 
 I cannot offer much other than to say the same thing happens regularly
 to me.  I cannot predict when it will happen but it happens somewhat
 frequently.  It is as if the frontend loses track of the backend.

I think this is what has happened to me on a few occasions, the backend
has stopped recording, the status page works still works but the
frontend won't play but lists all the shows etc.

Again a rcmythbackend restart fixed but I didn't discover exactly why it
happened.

Druid

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Re: Strange MythBackend troubles

2005-12-06 Thread Josh Tallen
On 12/6/05, Druid [EMAIL PROTECTED] wrote:
On Tue, 2005-12-06 at 16:49 -0500, Mike Frisch wrote: On Mon, Dec 05, 2005 at 11:26:44PM -0800, Jeff Clemens wrote: So occasionally, my master backend gets into a strange state. I have a frontend and a backend running on each of 2 boxes.The master backend
 occasionally gets into a state where the frontend will report that the backend is down when trying some things (like deleting a recording for instance), but other menu items that use the backend work fine.When it's
 in this state, neither frontend works correctly. /sbin/service mythbackend restart fixes the problem temporarily. I cannot offer much other than to say the same thing happens regularly
 to me.I cannot predict when it will happen but it happens somewhat frequently.It is as if the frontend loses track of the backend.I think this is what has happened to me on a few occasions, the backend
has stopped recording, the status page works still works but thefrontend won't play but lists all the shows etc.I think I am experiencing a similar problem. Occaisionally a program will stop recording partway through. It's not always obvious that this has happened, because the frontend appears to work fine. I can still watch recorded programs, including the one that failed, up to the point where it stopped. Everything appears to work, but it will not attempt to record any other programs. What really sends it into a tailspin is trying to delete a program after this has happened. The frontend completely freezes and must be killed along with a restart of the backend to get things back to normal. This problem started about two months ago, but I haven't changed anything that I can think of since I installed 
0.18.1 (other than the possible upgrade of the ivtv drivers). Nothing seems to be logged about this in any log that I can find, and I'm completely stumped. --Josh
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users