[mythtv-users] Backend quits functioning

[Michael T. Dean]

On 05/29/2006 06:38 PM, William Powers wrote:
> On the other hand, with a total of two backends and four frontends, I'm 
> familiar with the problems of upgrading you mention and I've pretty much 
> got it down to a science.  For me, the key to making upgrading easy is 
> the ability to quickly go back to the previous (working) version if 
> something goes wrong during the upgrade.  After trying several methods, 
> it finally turned out to be easiest for me to install Myth from source.  
> First, I use apt or yum or smart or source or whatever it takes to 
> configure all the boxes so I can compile Myth on it.
>
> Then I use ssh to log in to each box remotely and compile ('make') the 
> new version but I don't do a 'make install'.  Once I have the new 
> version compiled on all the boxes, I then find a free hour or so when no 
> one is watching TV or recording anything when I can perform the 
> upgrade.  7:00 am Sunday morning always seems to be available... :)
>
> To perform the actual upgrade, first I save the database per the 
> instructions in the docs.  Downgrading is easy with a copy of the 
> previous database but it's darn near impossible without it.  Next I ssh 
> to each box and stop all the backends.  Finally, I go back to the new 
> version source directory each box and do the 'make install'.  Then I 
> restart the backends, master first, and then the frontends.

Note, however, that mythtv and mythplugins must be the exact same 
version/revision (otherwise, you're playing with fire).  You can't make 
mythplugins until you've done a make install of mythtv, so it's not an 
instantaneous upgrade--it will take at least as long as compiling 
mythplugins.

Mike