[mythtv-users] mythweb serving up recordings - protocol mixmatch

Kevin Kuphal kuphal at dls.net
Wed Apr 20 22:47:44 UTC 2005

Don Brown wrote:

>I compiled Myth version 16 from CVS.  Then, when I moved to .17, I simply used
>Axels RPM packages.
>Seaching the archives, the usual case for protocol mismatch on a single FE/BE
>machine is issues with different versions in /usr/bin and /usr/local/bin (and
>likewise with /usr/lib).
>Based on the dates of the files, I determined that /usr/bin was the atrpms
>version (.17) and the /usr/local/bin was the default for the old 16 CVS version.
>Okay.  So I renamed all the /usr/local/bin/myth* to /usr/local/bin/myth*16 
>and renamed /usr/local/lib/myth to be /usr/local/lib/myth16.
>I rebooted to ensure I was loading all the correct modules and running the new
>executables.  All is fine.  I have full access to all myth features.
>MythWeb even works almost perfectly.
>However when I click on a recording, (myth://
>I get, on the windows client, a network error, and on the mythbackend.log, the
>following error:
>MainServer::HandleVersion - Client speaks protocol version 13 but we speak 14!
>"we" in that message appears to be mythbackend, (obvious I know, but hang on).
> So that means that something in mythweb seems to be running an old version.
>Now, in mythweb, the includes/mythbackend.php has PROTO set to 14, so that
>seems right.
Sounds like your windows client is still speaking version 13...


More information about the mythtv-users mailing list