[mythtv-users] protocol version mismatch, what's the best solution?

[Duncan Brown]

Axel Thimm wrote:
> On Wed, Oct 04, 2006 at 10:17:30AM -0700, Yeechang Lee wrote:
>   
>> Kevin Kuphal <kuphal at dls.net> says:
>>     
>>> 1) Didn't have the same version on both machines
>>> 2) Didn't restart one or both of the machines after upgrading
>>>       
>> I only have one machine that serves as both frontend and backend. The
>> first three things I did after running into the protocol issue were a)
>> restarting mythfrontend, b) (again) restarting mythbackend, and c)
>> making sure both the mythtv-frontend and mythtv-backend packages were
>> indeed updated.
>>
>>     
>>> There is *no way* that the same revision of Myth will result in a 
>>> protocol incompatibility
>>>       
>> Believe me, I couldn't understand it either. That's why the next step
>> was d) return to the -138 packages. However, that doesn't solve the
>> mystery. Both you and Axel say your responsibilities didn't cause
>> it. However, I, and an unusually-large number of others, seem to have
>> run into it this time around. Why? I suppose that, as with the
>> question of how many licks does it take to the middle of a Tootsie
>> Pop, "no one will ever know."
>>     
>
> If it's the same machine and you made sure you restarted everything
> (e.g. simply rebooted) I bet my *** that you have selective/partial
> upgrading or have otherwise broken you upgrade.
>
> Just step away from technicalities and rely on simple reasoning. The
> new mythtv packages only know something about protocol 31. If
> something on your system says protocol 30 it is either on disk,
> e.g. you haven't properly upgraded your system, or is still im memory,
> e.g. no service restart.
>   
>   
Hey

Just to add my story to the mix..

I did a normal smart upgrade, and hit this issue. Rebooting multiple 
times didnt fix it..

However simply restarting the backend service did

go figure..


Dunc