[mythtv-users] MythTV DB Upgrade Fails

Jay Foster jayf0ster at roadrunner.com
Sat Oct 25 22:31:49 UTC 2014


On 10/24/2014 07:31 PM, Stephen Worthington wrote:
> On Fri, 24 Oct 2014 18:43:34 -0700, you wrote:
>
>> I'm trying to do a DB upgrade using mythconverg_restore.pl,
>> mythtv-setup, and then running mythtvfrontend.  Things appear to work
>> fine, until I run mythtvfrontend.  It upgrades the music,video sections,
>> but then displays a popup dialog that states:
>>
>> The server uses network protocol version 40, but this client only
>> understands version 77.  Make sure you are running compatible versions
>> of the
>>
>> The message is cut off at that point.  There is only an OK box.
>> Selecting that causes mythtvfrontend to crash (exit code 135) and then
>> restart, which pops the same dialog up again.  Can I just ignore this?
>>
>> This is an upgrade from 0.21-fixes to 0.24? (mythbuntu 11.10) -> 0.27.?
>> (mythbuntu 14.04.1).  I get the same error going from 0.21 -> 0.24, only
>> it complains about the client only understanding network protocol 63 and
>> crashes with exit code 249.
>>
>> Why did it not upgrade the network protocol too?
>>
>> Jay
> I believe that 0.21 is too old for a direct upgrade to 0.27.  You have
> to upgrade to an older version first.  Fortunately, this was discussed
> recently - take a look at this thread:
>
>    http://www.gossamer-threads.com/lists/mythtv/users/575028
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
As stated, I am doing the upgrade in two steps (0.21 -> 0.24 -> 0.27).

I think I figured out the issue.  I was keeping the hostname the same, 
so I did not pay much attention to the changing hostname issues.  
Indeed, I confirmed that the hostname was set to localhost in mythtv 
frontend setup.  What I did not realize (remember) is that there are two 
other places where the host IP address (not hostname) exists; in the 
mythtv backend setup (mythtv-setup) for the local BE and master BE.

So when I ran mythtv-setup (backend setup) after the first upgrade step, 
I also changed the local BE and master BE IP address to 127.0.0.1.  
mythtv frontend then completed it's upgrade with no issues.  This is a 
combined fronted/backend so that works.  When I am all done, I can then 
change these two IP address back to the real interface address, so other 
frontends (I currently have none) can access the BE.

Jay



More information about the mythtv-users mailing list