[mythtv-users] Upgrade path to Ubuntu 16.04

[Mike Perkins]

On 07/01/17 11:57, Johan Van der Kolk wrote:
>
>> On 07 Jan 2017, at 12:13, Mike Perkins <mikep at randomtraveller.org.uk> wrote:
>>
>> On 07/01/17 08:10, Johan Van der Kolk wrote:
>>>
>>>> On 06 Jan 2017, at 01:17, Anthony Giggins <seven at seven.dorksville.net
>>>> <mailto:seven at seven.dorksville.net>> wrote:
>>>>
>>>>
>>>>
>>>> On 6 January 2017 at 10:07, Stephen Worthington <stephen_agent at jsw.gen.nz
>>>> <mailto:stephen_agent at jsw.gen.nz> <mailto:stephen_agent at jsw.gen.nz
>>>> <mailto:stephen_agent at jsw.gen.nz>>> wrote: On Thu, 5 Jan 2017 21:03:18 +0100, you wrote:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> while I am planning to move my backend to a new server, I stumbled across the fact that
>>>>> 0.27/fixes which I’m running now won’t run on Ubuntu 16.04. This due to a Qt version
>>>>> bump. And I need 0.28 to put on my new server if I want to move to 16.04.
>>>>>
>>>>> What is the best upgrade path, considering that I want my slave BE to stay on 14.04 for
>>>>> the time being?  (the DVB drivers are creating issues with every kernel upgrade, so I
>>>>> rather leave that system on 14.04 until I have certainty that the drivers work fine
>>>>> again)
>>>>>
>>>>> Johan
>>>>
>>>> You can upgrade to 0.28 and 0.28/fixes on 14.04, and it is best to do that before upgrading
>>>> to 16.04.  There should be no problem with mixing 14.04 and 16.04 systems as long as they
>>>> all use the same MythTV version.
>>>>
>>>> Yep I second this, my backend is still 14.04 but all my frontends are now 16.04 all running
>>>> 0.28/fixes.
>>>>
>>> Ended up with around 50 encoders with the MBE thinks are on the SBE, but when running setup
>>> on the SBE it just showed the normal old ones. Something went wrong here. Dunno what yet, but
>>> the SBE does not like them, and fails them all.
>>>
>> Is there a possibility that the two BEs are talking to different databases?
>>
>> Also, if you have "50 encoders" that implies that you haven't done a "Delete ALL tuners"
>> operation first (not "Delete all tuners on <host>). Do that and it should clear out the crud.
>>
>
> No, both talk to the same database. I’ve done a delete all tuners on both systems (which I should
> not do on an upgrade). Now trying to set up again. DVB-S with Diseqc setup is now a disaster.
> Used to be so easy, the way its done now is counterintuitive and when assigning inputs I can’t
> see which LNB is connected, since they’re all called DVBInput and the card name is the same. And
> I have 4 switches on 4 tuners, each connecting to three LNB’s. One card-one switch-one LNB is
> working now again. Seems best way is to create the new card with switch and LNB, then assign the
> input and go back to do it again. Otherwise I totally loose track (cards are named the same, even
> if the selected switch channel is different). Maybe a few more and I’ll get used to it.
>
Please don't top-post! It gets very confusing.

There may be a way to distinguish your inputs better using udev rules. I have identical tuners, 
DVB-T in my case, and it wasn't easy figuring out what was happening.

I added udev rules to make unique symlinks and then used the symlinks when assigning the cards in 
mythtv-setup. You might be able to do the same as that for your LNBs? I don't have DVB-S so I 
couldn't advise your specific situation.

As for "Deleting all tuners on both systems", you shouldn't need to do that. You only have one 
database so you only need to "Delete all tuners" /once/ and do that from the MBE. That will truncate 
the table and clear out all the junk from previous operations, restarting the numbering from 1.

Doing a "Delete all tuners" from /each/ host just removes (in theory) all information about that 
host. It won't clear away data from retired hosts nor reset the database counter.


-- 

Mike Perkins