[mythtv] [mythtv-commits] Ticket #4129: mythtv trakes very long... (or recorded list is empty)

Dave C megadave at gmail.com
Thu Nov 8 16:37:18 UTC 2007


FWIW, when I looked this morning, the BE was in its 'nonresponsive'
state. The machine itself was otherwise normal. The BE did seem to be
using a huge amount of ram *BUT* I noticed it used just about the same
amount after a fresh start, so I don't think it is leak-related. There
was still a reasonable amount of free ram as well as swap. The BE was
still there, it just wouldn't respond to anything.

For grins, I did a full reboot of the machine to give everything a
fresh start. I'll see how long that lasts. My next check will be to
update the sources to the current trunk and see what that
fixes/breaks. I'm hoping to get this stabilized because I want to
build a box for (non-techy) family members, and I can't use the last
release because I need the 'network recorder' that is in the trunk for
my provider's setup.

On 11/7/07, Dave C <megadave at gmail.com> wrote:
> I'll check, but I'm pretty certain its not a memory/swap issue. I had
> a script running to check that URL periodically, and when it did this
> last night, when I looked this morning the wget never completed. (This
> was over like 6 hours)
>
> When I see this again I will check both memory use as well as see if I
> can get any response, even delayed, on the http port.
>
> On 11/7/07, Stuart Auchterlonie <stuarta at squashedfrog.net> wrote:
> >
> >
> > MythTV wrote:
> > > #4129: mythtv trakes very long... (or recorded list is empty)
> > > --------------------+-------------------------------------------------------
> > >  Reporter:  markus  |        Owner:  ijr
> > >      Type:  defect  |       Status:  new
> > >  Priority:  minor   |    Milestone:  unknown
> > > Component:  mythtv  |      Version:  unknown
> > >  Severity:  medium  |   Resolution:
> > >   Mlocked:  0       |
> > > --------------------+-------------------------------------------------------
> > >
> > > Comment(by megadave at gmail.com):
> > >
> > >  I can confirm this at least, as it is happening to me as well. The
> > >  backend, while not crashing, seems to stop responding to the frontend. If
> > >  I start the backend with -v all,  and then go look at the logfile once the
> > >  be has gone into this state, there appears to still be some recurring
> > >  activity (mostly auto-expire checking), but until the BE is restarted it
> > >  will not talk to the FE. Trying http://localhost:6544/ directly gets a
> > >  connection, but no response either.
> > >
> >
> > There are still a few memory leaks in the backend, so it's probably
> > getting further and further into swap, and thus it responds much more
> > slowly than normal.
> >
> > Next time does this try connecting to http://localhost:6544/ and see if
> > it does eventually come up...
> >
> >
> > Stuart
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> >
>


More information about the mythtv-dev mailing list