<br><br><div><span class="gmail_quote">On 8/28/07, <b class="gmail_sendername">Paul Harrison</b> <<a href="mailto:mythtv@dsl.pipex.com">mythtv@dsl.pipex.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Sockets are what mythbackend and mythfrontend use to communicate with<br>each other so they both use them. They use the network protocol stack so<br>it allows a frontend to be local on the same machine as the backend or a
<br>remote frontend across a network to both talk to the BE in the same way.<br><br>It's a difficult problem to diagnose because it involves so many<br>different things that have to work together and the problem could be
<br>with anyone of them. There's the software for the backend/frontend ,<br>the QT classes, the kernel and if using a split frontend/backend there's<br>the physical connection between them (the network card/hardware, the
<br>driver for the network hardware, the network hub/switch/router, the<br>network cables etc).<br><br>Is this on a combined FE/BE or remote FE?<br><br>Do you have other network problems like not being able to connect to the
<br>internet or slow flaky connections etc.<br><br><br>Paul H.</blockquote><div><br> 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 use.<br><br>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-
<br><br>Thanks,<br>Steve<br></div><br></div><br><br clear="all"><br><br>