Mythbackend crashing, problems with Myth program guide

Torfinn Ingolfsen torfinn.ingolfsen at
Thu Mar 15 07:29:45 UTC 2007

On Wed, 14 Mar 2007 20:44:41 -0400
Joe Auty <joe at> wrote:

> 2007-03-14 20:41:15.436 MythSocket(81de580:-1): writeData: Error,
> socket went unconnected
> 2007-03-14 20:41:15.438 MythSocket(8261e00:-1): writeStringList:
> Error, called with unconnected socket.

Are you using the latest opdate of the MythTV port?
Or at least the one with the Feb 24th update, which fixes frontend /
backend communication.

FWIW, the program guide works (at least so far, my Mythbackend has only
been running for an evening and a night) for me, both from the menu and
from pressing 'm' and selecting it from the menu whuile watching LiveTV.
I'm using the latest update of the MythTV port.

> Would you recommend trying to recreate my Myth database, or doing a
> repair of particular tables or something? Any suggestions which ones
> to focus on?

In general, it is almost always better to find out what the error is,
and whats causing it, than trying a lot of things more or less at
random to see if one of those things fixes the ptoblem at hand.
But I guess you know that already. :-)

To find the error, you will have to look at logfiles. Both mythbackend
and mythfrontend has command line parameters, start out with '--help'.
You could for example, run mythbackend with
'--logfile /var/log/mythbackend.log' to have a backend log.
The frontend alo produces logging output to the terminal (shell) it was
started from.

Torfinn Ingolfsen,

More information about the freebsd-multimedia mailing list