[mythtv-users] Making mythtbackend.log files useable

Steve MacLaren scram69 at gmail.com
Tue Aug 28 17:26:50 UTC 2007

On 8/28/07, Paul Harrison <mythtv at dsl.pipex.com> wrote:
> Sockets are what mythbackend and mythfrontend use to communicate with
> each other so they both use them. They use the network protocol stack so
> it allows a frontend to be local on the same machine as the backend or a
> remote frontend across a network to both talk to the BE in the same way.
> It's a difficult problem to diagnose because it involves so many
> different things that have to work together and the problem could be
> with anyone of them.  There's the software for the backend/frontend ,
> the QT classes, the kernel and if using a split frontend/backend there's
> the physical connection between them (the network card/hardware, the
> driver for the network hardware, the network hub/switch/router, the
> network cables etc).
> Is this on a combined FE/BE or remote FE?
> Do you have other network problems like not being able to connect to the
> internet or slow flaky connections etc.
> Paul H.

 The backend machine is a combined FE/BE.  I also use a remote FE.  The
remote FE is connected through a linksys 8 port router.  However, from the
timestamps in the log (and my monit.log) I see many crashes occurring in the
middle of the night, when the remote FE is off and the local FE is not in

I don't recall any network slowness/flakyness, but I don't have any data to
back that up.  Is there a quick or easy way to check for this that you
recommend?  Would something like ethereal be useful to diagnose this-

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070828/edcc3fa7/attachment.htm 

More information about the mythtv-users mailing list