a Celeron 1.8 and a half gig
of RAM... should be here sometime next week and I can do a motherboardectomy :)
-Original Message-
From: [EMAIL PROTECTED] on behalf of Lucas Meijer
Sent: Wed 5/18/2005 6:05 PM
To: Discussion about mythtv
Cc:
Subject:Re: [mythtv-users] Dying
: [EMAIL PROTECTED] on behalf of Lucas Meijer
Sent: Wed 5/18/2005 6:05 PM
To: Discussion about mythtv
Cc:
Subject:Re: [mythtv-users] Dying Backend
Have any of the people who are having this problem tried running
mythbackend in gdb, or running mythbackend with -v all option?
I'm very
Just out of curiosity -- what kind of chipset do you have on your
motherboard? I had a hell of time keeping mythbackend running when I had
a via board running Fedora. I actually wrote a perl script to monitor my
backend ever 10 seconds and start it up when it hung or died. Turned out a
new board
To: Discussion about mythtv
Cc: mythtv-users@mythtv.org
Subject: Re: [mythtv-users] Dying Backend
Just out of curiosity -- what kind of chipset do you have on your
motherboard? I had a hell of time keeping mythbackend running when I had
a via board running Fedora. I actually wrote
Have any of the people who are having this problem tried running
mythbackend in gdb, or running mythbackend with -v all option?
I'm very interesting in your results. If I run mythbackend in gdb, at
the moment of the crash it says Cannot find handle 12345: invalid
thread handle. the -v all
I know, these always seem to be a problem. My problem seems to be that anytime
a job is run that requires write access to the database (specifically when
scheduling shows or when deleting a previous recording) quite often the
mythbackend will simply up and die. I've checked the logs and nothing
since I use binary packages is there a way I can
up the verbosity of these logs to see if anything weird is going on?
you can edit /etc/init.d/mythbackend
go to the start) section
find the line that calls mythbackend
add -v all
or just run mythbackend manually in a shell
log in remotely or
Another time the backend dies is if I've been using Mythweb, that seems to
cause more crashes than it's sometimes worth (though I do prefer using
Mythweb to locate shows that I want to record).
does mythweb make the backend die for you
only on the recorded_programs screen or on other screens as
the crash). Could this be a mysql
bug we're fighting? Version perhaps?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Risto Treksler
Sent: Tuesday, May 17, 2005 3:04 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] Dying Backend
since I use binary
