Just figured it out.. mythlcdserver was still running. I guess it doesn't get killed upon mythfrontend exit. <br><br>Why is it not killed? Also, is it possible to have the error message be more specific about which client is using the bad protocol?<br>
<br>In any case.. hopefully this helps others!<br><br><div class="gmail_quote">On Thu, Nov 5, 2009 at 7:26 AM, Dave D <span dir="ltr"><<a href="mailto:dave726@gmail.com">dave726@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi everyone,<br><br>I recently upgraded to 0.22 r22740 (at least 0.22 RC2). I have a brand new database created on the first mythtv-setup run... updated all my capture card/schedules direct information there, ran mythfilldatabase... everything went smooth.<br>
<br>When I run mythbackend, however, I get the following output about every 10 seconds:<br><br>2009-11-05 07:10:52.819 MainServer::HandleVersion - Client speaks protocol version 40 but we speak 50!<br>2009-11-05 07:10:52.819 MainServer, Warning: Unknown socket closing MythSocket(0x826f728)<br>
<br>I don't have any mythfrontends running during this time.. I'm not sure what is meant by "client" in this context.<br><br><br>any help would be much appreciated. I had to watch <gulp>commercials</gulp> last night!! :-)<br>
<br><br>thanks,<br><font color="#888888"> - Dave<br>
</font></blockquote></div><br>