[mythtv-users] Backend dieing on 0.24

[Eloy Paris]

Hi Chris,

On Tue, Nov 23, 2010 at 01:37:42PM -0500, Christopher X. Candreva wrote:

> Since I upgraded to 0.24 2 days ago, my backend has unexpectedly died twice.
> 
> There isn't a lot in the logs from that time, nothing at least that stands 
> out to me as being a cause. I'll insert them below. Any idea on a next 
> step ?
> 
> 2010-11-23 08:00:00.750 TVRec(1): Changing from RecordingOnly to None
> 2010-11-23 08:00:00.864 Updating status for "The Wacky World of Tex Avery":"The Not-So-Great Train Robbery; Humpty Dumpty Had a Great Wall; Marital Blitz" on cardid 1 (Recording => Recorded)
> 2010-11-23 08:00:00.874 Finished recording The Wacky World of Tex Avery "The Not-So-Great Train Robbery; Humpty Dumpty Had a Great Wall; Marital Blitz": channel 1113
> 2010-11-23 08:00:00.949 scheduler: Finished recording: The Wacky World of Tex Avery "The Not-So-Great Train Robbery; Humpty Dumpty Had a Great Wall; Marital Blitz": channel 1113
> 2010-11-23 08:00:01.363 MainServer, Error: PREVIEW_SUCCESS but no receivers.
> pure virtual method called
> 2010-11-23 08:00:01.389 Finished recording The Wacky World of Tex Avery "The Not-So-Great Train Robbery; Humpty Dumpty Had a Great Wall; Marital Blitz": channel 1113
> terminate called without an active exception
> 2010-11-23 08:00:02.868 Event socket closed. No connection to the backend.

If the backend is segfaulting then the developers will need
a stack trace to see where exactly the crash is taking
place. Take a look at the "Debugging with GDB" section in
http://www.mythtv.org/docs/mythtv-HOWTO-22.html. Perhaps running the
backend with more debug verbosity might help too.

Do you see any segfault messages in the output from the "dmesg" command?

Cheers,

Eloy Paris.-