Mailing List Archive: MythTV: Users

MythTV backend crashing constantly

Index | Next | Previous | View Threaded

joe at netmusician

Oct 18, 2007, 9:40 PM

Post #1 of 18 (2689 views)
Permalink

MythTV backend crashing constantly

Hello,

What sorts of troubleshooting techniques can I employ to figure out why
my Myth backend is crashing all the time? It happens so randomly that I
can't really get a strace in, and nothing terribly obvious is being
outputted to the logs:

2007-10-19 00:33:55.342 AFD: Opened codec 0x743600, id(MPEG2VIDEO)
type(Video)
2007-10-19 00:33:55.431 Scheduled 13 items in 11.1 = 10.98 match + 0.13
place
2007-10-19 00:33:55.432 AFD: Opened codec 0x7439d0, id(MP2) type(Audio)
2007-10-19 00:33:55.442 Seem to be woken up by USER
2007-10-19 00:37:44.448 Event socket closed. No connection to the backend.

What are some of the most common causes for random backend crashes while
idle, and what can I try to fix them? I recently disabled ACPI in my
kernel as this was causing machine instability, I don't know if this has
anything to do with my problem?

--
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe [at] netmusician
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steveskarda at gmail

Oct 18, 2007, 10:44 PM

Post #2 of 18 (2611 views)
Permalink

Re: MythTV backend crashing constantly [In reply to]

On 10/19/07, Joe Auty <joe [at] netmusician> wrote:
>
> Hello,
>
> What sorts of troubleshooting techniques can I employ to figure out why
> my Myth backend is crashing all the time? It happens so randomly that I
> can't really get a strace in, and nothing terribly obvious is being
> outputted to the logs:

I have had similar problems with my backend crashing ever since I upgraded
from Dapper to Feisty while at the same time upgrading to 0.20.2

I followed the directions for debugging with gdb:

http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2

I start the backend now with

while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done;

Wouldn't you know it runs now without problems. So now I just always run
it that way. I have been watching the list closely hoping that someone else
may have a key. Either that or I am hoping 0.21 won't have the same issue
for me.

My guess is that it might have something to do with EIT scanning. There
have been some threads that suggested that could cause some problems. I
turned it on during the upgrade when I setup schedules direct. I have since
turned if off, completely wiped out my cards and set everything up from
scratch but I still have the problems though.

joe at netmusician

Oct 21, 2007, 10:14 PM

Post #3 of 18 (2595 views)
Permalink

Re: MythTV backend crashing constantly [In reply to]

Steve Skarda wrote:
> On 10/19/07, *Joe Auty* <joe [at] netmusician
> <mailto:joe [at] netmusician>> wrote:
>
> Hello,
>
> What sorts of troubleshooting techniques can I employ to figure out why
> my Myth backend is crashing all the time? It happens so randomly that I
> can't really get a strace in, and nothing terribly obvious is being
> outputted to the logs:
>
>
> I have had similar problems with my backend crashing ever since I
> upgraded from Dapper to Feisty while at the same time upgrading to 0.20.2
>
> I followed the directions for debugging with gdb:
>
> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2
>
> I start the backend now with
>
> while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done;
>
>
> Wouldn't you know it runs now without problems. So now I just always
> run it that way. I have been watching the list closely hoping that
> someone else may have a key. Either that or I am hoping 0.21 won't have
> the same issue for me.
>

Thanks Steve!

I've held off on trying this since I was hoping that Ubuntu 7.10 would
solve this issue for me (irrationally, I know, more like basic
procrastination), but it hasn't..

I'm running the backend with screen now, and will report any interesting
error messages to this list. I am seeing a fair number of:

(no debugging symbols found)

I'm assuming this is because the apt-get version of mythtv did not
include the --debug option? I did a:

apt-get source mythtv-backend

and then a:

./configure

and I'm getting:

You must have the Lame MP3 encoding library installed to compile Myth.
exit: 2355: Illegal number: -1

Should I bother to track this down, or will I get some useful feedback
without the --debug option? Just out of curiosity since I'm new to
Ubuntu, is there a way to determine what configure options were used to
generate the .deb files that make up the apt-get repository?

Thanks for all your help!

> My guess is that it might have something to do with EIT scanning.
> There have been some threads that suggested that could cause some
> problems. I turned it on during the upgrade when I setup schedules
> direct. I have since turned if off, completely wiped out my cards and
> set everything up from scratch but I still have the problems though.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

--
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe [at] netmusician
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mario.mailing at gmail

Oct 22, 2007, 12:57 AM

Post #4 of 18 (2584 views)
Permalink

Re: MythTV backend crashing constantly [In reply to]

Joe Auty wrote:
> Steve Skarda wrote:
>> On 10/19/07, *Joe Auty* <joe [at] netmusician
>> <mailto:joe [at] netmusician>> wrote:
>>
>> Hello,
>>
>> What sorts of troubleshooting techniques can I employ to figure out why
>> my Myth backend is crashing all the time? It happens so randomly that I
>> can't really get a strace in, and nothing terribly obvious is being
>> outputted to the logs:
>>
>>
>> I have had similar problems with my backend crashing ever since I
>> upgraded from Dapper to Feisty while at the same time upgrading to 0.20.2
>>
>> I followed the directions for debugging with gdb:
>>
>> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2
>>
>> I start the backend now with
>>
>> while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done;
>>
>>
>> Wouldn't you know it runs now without problems. So now I just always
>> run it that way. I have been watching the list closely hoping that
>> someone else may have a key. Either that or I am hoping 0.21 won't have
>> the same issue for me.
>>
>
> Thanks Steve!
>
> I've held off on trying this since I was hoping that Ubuntu 7.10 would
> solve this issue for me (irrationally, I know, more like basic
> procrastination), but it hasn't..
>
> I'm running the backend with screen now, and will report any interesting
> error messages to this list. I am seeing a fair number of:
>
> (no debugging symbols found)
>
> I'm assuming this is because the apt-get version of mythtv did not
> include the --debug option? I did a:
>
> apt-get source mythtv-backend
>
> and then a:
>
> ./configure
>
> and I'm getting:
>
> You must have the Lame MP3 encoding library installed to compile Myth.
> exit: 2355: Illegal number: -1
>
>
> Should I bother to track this down, or will I get some useful feedback
> without the --debug option? Just out of curiosity since I'm new to
> Ubuntu, is there a way to determine what configure options were used to
> generate the .deb files that make up the apt-get repository?
>
>
> Thanks for all your help!
>
>
>
>
>> My guess is that it might have something to do with EIT scanning.
>> There have been some threads that suggested that could cause some
>> problems. I turned it on during the upgrade when I setup schedules
>> direct. I have since turned if off, completely wiped out my cards and
>> set everything up from scratch but I still have the problems though.
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users [at] mythtv
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
Actually on Ubuntu, the apport service will catch these sorts of problems
typically without needing for you to manually run gdb.

Check if you have apport installed, and if not, install it. On a Gnome, KDE, or
Xfce (Mythbuntu) based system, you will get an icon in your system tray with a
crash report that can be submitted. On standalone (server) type installs, you
will have to manually run apport-gtk to make the crash report and submit it.

--
Mario Limonciello
mario.mailing [at] gmail

Attachments:

signature.asc (0.25 KB)

joe at netmusician

Oct 22, 2007, 10:12 PM

Post #5 of 18 (2567 views)
Permalink

Re: MythTV backend crashing constantly [In reply to]

Mario Limonciello wrote:
> Joe Auty wrote:
>> Steve Skarda wrote:
>>> On 10/19/07, *Joe Auty* <joe [at] netmusician
>>> <mailto:joe [at] netmusician>> wrote:
>>>
>>> Hello,
>>>
>>> What sorts of troubleshooting techniques can I employ to figure out why
>>> my Myth backend is crashing all the time? It happens so randomly that I
>>> can't really get a strace in, and nothing terribly obvious is being
>>> outputted to the logs:
>>>
>>>
>>> I have had similar problems with my backend crashing ever since I
>>> upgraded from Dapper to Feisty while at the same time upgrading to 0.20.2
>>>
>>> I followed the directions for debugging with gdb:
>>>
>>> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2
>>>
>>> I start the backend now with
>>>
>>> while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done;
>>>
>>>
>>> Wouldn't you know it runs now without problems. So now I just always
>>> run it that way. I have been watching the list closely hoping that
>>> someone else may have a key. Either that or I am hoping 0.21 won't have
>>> the same issue for me.
>>>
>> Thanks Steve!
>>
>> I've held off on trying this since I was hoping that Ubuntu 7.10 would
>> solve this issue for me (irrationally, I know, more like basic
>> procrastination), but it hasn't..
>>
>> I'm running the backend with screen now, and will report any interesting
>> error messages to this list. I am seeing a fair number of:
>>
>> (no debugging symbols found)
>>
>> I'm assuming this is because the apt-get version of mythtv did not
>> include the --debug option? I did a:
>>
>> apt-get source mythtv-backend
>>
>> and then a:
>>
>> ./configure
>>
>> and I'm getting:
>>
>> You must have the Lame MP3 encoding library installed to compile Myth.
>> exit: 2355: Illegal number: -1
>>
>>
>> Should I bother to track this down, or will I get some useful feedback
>> without the --debug option? Just out of curiosity since I'm new to
>> Ubuntu, is there a way to determine what configure options were used to
>> generate the .deb files that make up the apt-get repository?
>>
>>
>> Thanks for all your help!
>>
>>
>>
>>
>>> My guess is that it might have something to do with EIT scanning.
>>> There have been some threads that suggested that could cause some
>>> problems. I turned it on during the upgrade when I setup schedules
>>> direct. I have since turned if off, completely wiped out my cards and
>>> set everything up from scratch but I still have the problems though.
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users [at] mythtv
>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
> Actually on Ubuntu, the apport service will catch these sorts of problems
> typically without needing for you to manually run gdb.
>
> Check if you have apport installed, and if not, install it. On a Gnome, KDE, or
> Xfce (Mythbuntu) based system, you will get an icon in your system tray with a
> crash report that can be submitted. On standalone (server) type installs, you
> will have to manually run apport-gtk to make the crash report and submit it.
>

Hmmm.... I do have Apport installed, but I do not see it on my system
tray. I have never seen a crash report for MythTV like the screenshots here:

https://wiki.ubuntu.com/Apport

>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

--
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe [at] netmusician
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

joe at netmusician

Oct 22, 2007, 10:21 PM

Post #6 of 18 (2574 views)
Permalink

Re: MythTV backend crashing constantly (gdb seg fault output) [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

Using GDB I have captured some seg fault output which I have attached...

I hope that I have sent this output to the right place. I hope that
somebody will be able to make sense of this and put this info to good use!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHHYTLCgdfeCwsL5ERArf+AKCbQjUnrER6eG1DJA74Zf/LbaHW6ACeJuXN
ONTMaH7b4As0yDJo8mypf54=
=Ei3i
-----END PGP SIGNATURE-----

Attachments:

MythTVsegfault.txt (14.5 KB)

steveskarda at gmail

Oct 23, 2007, 11:59 AM

Post #7 of 18 (2561 views)
Permalink

Re: MythTV backend crashing constantly (gdb seg fault output) [In reply to]

On 10/23/07, Joe Auty <joe [at] netmusician> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> Using GDB I have captured some seg fault output which I have attached...
>
>
Joe-

I can't interpret your report but I do have a question. Did you create
this using gdb or apport mentioned in previous thread? I am just curious
since I have the same problem to troubleshoot that you do. I actually
compiled a version manually with debug built in and that is how I got gdb
working. Did you use the command:

while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done;

and still see the backend crash? When I use that method, my backend runs
OK.

Steve

joe at netmusician

Oct 29, 2007, 4:58 PM

Post #8 of 18 (2496 views)
Permalink

Re: MythTV backend crashing constantly (gdb seg fault output) [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here is another seg fault:

Joe Auty wrote:
> Hello,
>
> Using GDB I have captured some seg fault output which I have attached...
>
>
> I hope that I have sent this output to the right place. I hope that
> somebody will be able to make sense of this and put this info to good use!
>
>
>
>

- ------------------------------------------------------------------------

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

- --
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe [at] netmusician
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJnOyCgdfeCwsL5ERAvvbAJ0SJOBJDmzpEaDB6jV+8oV1jSDb7QCgieAm
sFCfYQBb7Pe9YQK7It0E1G8=
=bPJP
-----END PGP SIGNATURE-----

Attachments:

mythsegfault.txt (15.3 KB)

joe at netmusician

Oct 29, 2007, 5:38 PM

Post #9 of 18 (2490 views)
Permalink

Re: MythTV backend crashing constantly (gdb seg fault output) [In reply to]

Please let me know if more would be helpful, I'm getting them quite
frequently now, and it's becoming a real problem since every time it
happens I have to restart both backend and frontend.

Joe Auty wrote:
> Here is another seg fault:
>
>
>
>
>
>
> Joe Auty wrote:
>> Hello,
>
>> Using GDB I have captured some seg fault output which I have attached...
>
>
>> I hope that I have sent this output to the right place. I hope that
>> somebody will be able to make sense of this and put this info to good use!
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>

------------------------------------------------------------------------

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

--
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe [at] netmusician
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steveskarda at gmail

Oct 31, 2007, 5:19 PM

Post #10 of 18 (2456 views)
Permalink

Re: MythTV backend crashing constantly (gdb seg fault output) [In reply to]

I did a search for cpp:661 since that seemed to appear at each of my
crashes. Lo & behold, the only hit was someone that posted on the
developers list 10/6/07 with the subject "Backend crashes almost daily"
There was some discussion regarding EIT scanning. The only real answer
though was to update to SVN trunk.

I have been hesitant to try that since SVN was not terribly stable when I
have tried it in the past and my wife drove me crazy complaining about
having to restart the system. I might just leave it in looping mode until
the next stable release.

joe at netmusician

Nov 2, 2007, 11:29 PM

Post #11 of 18 (2442 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

Hey Guys,

I think I have solved this problem... At least, so far, so good.

It looks like the culprit was a piece of software called "MythGrowl"
for OS X was causing the backend to crash. The only other change I
made was to disable invoking mythfilldatabase automatically, I will
experiment with turning this back on and seeing what happens. However,
I have reason to believe that this wasn't the problem.

For the benefit of others that might be experiencing crashes for this
or any other reason, I'll keep you guys posted :)

-----------
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe [at] netmusician

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Nov 3, 2007, 9:32 PM

Post #12 of 18 (2397 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

On 11/03/2007 02:29 AM, Joe Auty wrote:
> I think I have solved this problem... At least, so far, so good.
>
> It looks like the culprit was a piece of software called "MythGrowl"
> for OS X was causing the backend to crash. The only other change I
> made was to disable invoking mythfilldatabase automatically, I will
> experiment with turning this back on and seeing what happens. However,
> I have reason to believe that this wasn't the problem.
>
> For the benefit of others that might be experiencing crashes for this
> or any other reason, I'll keep you guys posted :)

What does MythGrowl do? (I.e. any idea what the root cause is? Is it
just sending a lot of backend status queries (HTML/XML) or some other
"known" way of crashing the backend? If so, perhaps something like
myth_recent_recordings.pl (in SVN trunk) or a similar Growl-specific
script written to use the Perl bindings like myth_recent_recordings.pl
could be used instead.)

Mike

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steveskarda at gmail

Nov 5, 2007, 5:55 AM

Post #13 of 18 (2375 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

On 11/3/07, Michael T. Dean <mtdean [at] thirdcontact> wrote:
>
> On 11/03/2007 02:29 AM, Joe Auty wrote:
> > I think I have solved this problem... At least, so far, so good.
> >
> > It looks like the culprit was a piece of software called "MythGrowl"
> > for OS X was causing the backend to crash. The only other change I
> > made was to disable invoking mythfilldatabase automatically, I will
> > experiment with turning this back on and seeing what happens. However,
> > I have reason to believe that this wasn't the problem.
> >
> > For the benefit of others that might be experiencing crashes for this
> > or any other reason, I'll keep you guys posted :)
>
> What does MythGrowl do? (I.e. any idea what the root cause is? Is it
> just sending a lot of backend status queries (HTML/XML) or some other
> "known" way of crashing the backend? If so, perhaps something like
> myth_recent_recordings.pl (in SVN trunk) or a similar Growl-specific
> script written to use the Perl bindings like myth_recent_recordings.pl
> could be used instead.)
>
> Mike
>
> _______________________________________________

I have had a similar problem with backend crashing but I do not have
Mythgrowl installed. Nothing shows up in the logs and I haven't had
responses to the posting of some debug outputs. I upgraded from Fiesty to
latest Mythbuntu (based on Gutsy) last week. That didn't help. I upgraded
to the stable + fixes weekly build of Mythbuntu but that didn't help.
Yesterday, I upgraded to the development truck weekly build of Mythbuntu and
my problem has not resurfaced yet. It has been 24 hours with no crash which
is promising but I won't feel like it is really fixed until I see it run for
several days without a crash.

I think my problem may have something to do with having an EIT flag set
somewhere in the database (eitcache is empty and all channels have flag
turned off in mythconverg) because it started when I upgrade to schedules
direct and turned EIT on. There was a fix for bad EIT data in truck
version that may not have gotten put back into stable + fixes. See
developers list for more details.

http://www.gossamer-threads.com/lists/mythtv/dev/294460?search_string=backend%20crashing;#294460

steveskarda at gmail

Nov 5, 2007, 7:12 AM

Post #14 of 18 (2377 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

On 11/5/07, Steve Skarda <steveskarda [at] gmail> wrote:
>
> I upgraded to the development truck weekly build of Mythbuntu and my
> problem has not resurfaced yet. It has been 24 hours with no crash which is
> promising but I won't feel like it is really fixed until I see it run for
> several days without a crash.
>

Drats! Sending out this note jinxed me. I just got a monit notice stating
that my backend crashed. Certainly, this must be a problem with my system,
not Mythtv. Do I rebuild it up from scratch? Ugh.

beww at beww

Nov 5, 2007, 7:21 AM

Post #15 of 18 (2377 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

Steve Skarda wrote:
>
> On 11/5/07, *Steve Skarda* <steveskarda [at] gmail
> <mailto:steveskarda [at] gmail>> wrote:
>
> I upgraded to the development truck weekly build of Mythbuntu and
> my problem has not resurfaced yet. It has been 24 hours with no
> crash which is promising but I won't feel like it is really fixed
> until I see it run for several days without a crash.
>
>
> Drats! Sending out this note jinxed me. I just got a monit notice
> stating that my backend crashed. Certainly, this must be a problem with
> my system, not Mythtv. Do I rebuild it up from scratch? Ugh.

Check your logs to see if you can determine the cause of the crash. If
that doesn't show anything I'd start by making sure you do not have a
hardware problem - test the RAM, make sure cooling is adequate - all the
"usual suspects".

beww
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

steveskarda at gmail

Nov 5, 2007, 7:48 AM

Post #16 of 18 (2505 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

On 11/5/07, Brian Wood <beww [at] beww> wrote:
>
> Steve Skarda wrote:
> >
> > On 11/5/07, *Steve Skarda* <steveskarda [at] gmail
> > <mailto:steveskarda [at] gmail>> wrote:
> >
> > I upgraded to the development truck weekly build of Mythbuntu and
> > my problem has not resurfaced yet. It has been 24 hours with no
> > crash which is promising but I won't feel like it is really fixed
> > until I see it run for several days without a crash.
> >
> >
> > Drats! Sending out this note jinxed me. I just got a monit notice
> > stating that my backend crashed. Certainly, this must be a problem with
>
> > my system, not Mythtv. Do I rebuild it up from scratch? Ugh.
>
> Check your logs to see if you can determine the cause of the crash. If
> that doesn't show anything I'd start by making sure you do not have a
> hardware problem - test the RAM, make sure cooling is adequate - all the
> "usual suspects".
>
> beww
> _______________________________________________

Thanks for the reply! The last thing in the log is always:

Reschedule requested for id 0.

I have done the optimize and repair database steps and the database looks
OK.

Temperature of cpu is 45 degC
Temperature of board is 40 degC

I have tried blowing it out and even replacing the CPU cooler but it hasn't
helped.

Ran memtest all and came up with no errors.

I posted the debug output here. I have had trouble figuring out how to
interpret what it is telling me.

http://www.gossamer-threads.com/lists/mythtv/users/297060?search_string=backend%20crash;#297060

Any other usual aspects? Any way to test harddrive?

jharitos at yahoo

Nov 5, 2007, 10:27 AM

Post #17 of 18 (2370 views)
Permalink

Re: MythTV backend crashing constantly [In reply to]

I use to get frequent backend crashes and I solved
them by going into the recording profiles and
selecting LiveTV and I changed the audio from MP3 to
uncompressed I also changed the sampling rate to
48000. I haven't had a crash for over a month now.
It's a stab in the dark on your problem but I figured
I'd pass this on.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

joe at netmusician

Nov 5, 2007, 2:11 PM

Post #18 of 18 (2354 views)
Permalink

Re: MythTV backend crashing constantly (SOLVED) [In reply to]

On Nov 4, 2007, at 12:32 AM, Michael T. Dean wrote:

> On 11/03/2007 02:29 AM, Joe Auty wrote:
>> I think I have solved this problem... At least, so far, so good.
>>
>> It looks like the culprit was a piece of software called "MythGrowl"
>> for OS X was causing the backend to crash. The only other change I
>> made was to disable invoking mythfilldatabase automatically, I will
>> experiment with turning this back on and seeing what happens.
>> However,
>> I have reason to believe that this wasn't the problem.
>>
>> For the benefit of others that might be experiencing crashes for this
>> or any other reason, I'll keep you guys posted :)
>
> What does MythGrowl do? (I.e. any idea what the root cause is? Is it
> just sending a lot of backend status queries (HTML/XML) or some other
> "known" way of crashing the backend? If so, perhaps something like
> myth_recent_recordings.pl (in SVN trunk) or a similar Growl-specific
> script written to use the Perl bindings like myth_recent_recordings.pl
> could be used instead.)
>

MythGrowl runs on OS X and receives notifications from the mythbackend
over the Myth port about recordings stopping and starting. Mythbackend
and frontend are running under Ubuntu 7.10, if that makes any
difference.

> Mike
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads