I fixed the problem by editing the data base using mysql-query-browser<br><br>I removed old system in the setting record.<br><br>-Oz<br><br><div class="gmail_quote">On Sat, Mar 27, 2010 at 8:51 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"><div class="im">
On 03/27/2010 11:02 AM, Oz Dror wrote:<br>
<span style="white-space: pre;">>> On 3/27/2010 03:13, Oz wrote:<br>
>>> 2010-03-26 23:09:20.551 Protocol version mismatch <br>
>>> (frontend=56,backend=50)<br>
>> <br>
>> That has nothing to do with the database. You have a 0.23rc<br>
>> frontend trying to connect to a 0.22 backend. You cannot do
that.<br>
>> All machines connected to that backend must be running the same<br>
>> version of mythtv.<br>
></span><br>
<span style="white-space: pre;">> It is a new install the frontend
and the backend are 0.23rc<br>
> <br>
> only the DB is 0.22. Using mythtv-setup does not fix it. It just<br>
> freezes after backing up the old DB</span><br>
<br></div>
No, you /are/ running a MythTV 0.23rc1 or 0.23-fixes frontend against a
MythTV 0.22-fixes backend.<br>
<br>
You may have installed MythTV 0.23rc1 or 0.23-fixes mythbackend, but
it's not what's currently running.<br>
<br>
I highly recommend a reboot. If that doesn't fix it, then you likely
have 2 versions of MythTV installed (i.e. one in /usr, installed by
packages, and one in /usr/local, installed from source).<br>
<br>
Mike<br>
<br>
</div>
</blockquote></div><br>