[mythtv-users] Two MythTV systems on same subnet - am I asking for trouble?
Michael A Weber
mweberjunk01 at gmail.com
Mon Jun 24 23:55:25 UTC 2019
I’m a MythTV on CentOS user, and I’ve always taken a different approach.
Since you’re having redundant hardware, and since you have two machines, I’m also guessing you have separate frontend and backend machines. Since your goal is to minimize downtime (as there is no way to completely eliminate downtime), you can build your new CentOS box, make sure everything works at the OS level first, then grab the source and dependencies for MythTV and compile it for your build. It’s really not that difficult, the instructions in the wiki are dead on, and updating is really the same beast. Then, once you get it built and installed, here comes the transfer (which will actually take you less time than your previous idea of “moving everything over later.” Shutdown mythbackend, backup the database, move it to the new box, and restore it there. Fire up mythbackend, which will update the database, make any mythtv-setup changes you need to make, and if it works, you’re golden. If it does not, simply shut it down and fire up the old box and resume TV watching until you can determine the fix for your problem and move onward. I’m also assuming since you mentioned the issues with your NAS, your NAS is where all your recordings, videos, music, etc is stored. So, no need to move stuff there.
If you indeed do have separate front ends, and if by chance they are diskless network boot devices (which I love), updating is a matter of putting the right boot file in place on your TFTP server, changing any needed config files, and rebooting the frontend. Don’t like it? Change the config files back, reboot, and you’re done. However, seeing as you’re on 0.25, I don’t believe this all is the case and you probably have disk machines.
I hope this helps!
> On Jun 24, 2019, at 11:50 AM, ajp at cantabrian.co.nz wrote:
>>> On 6/23/19 3:16 AM, Mark Perkins wrote:
>>> On 23 June 2019 5:34:24 pm <ajp at cantabrian.co.nz> wrote:
>>>>> My current Myth frontend and backend are both 0.25. So long over
>>>> for upgrade but don’t fancy iterative upgrade and anyways Fedora 18 is so out of support it’s not funny.
>>>> Plan is setup a 0.29 server, get it working, iron out the kinks and
>>>> move the recordings from the old system to the new. I think that is a reasonable plan.
>>>>> I am getting a bunch of problems having separate masters on the
>>>> subnet LAN, mostly around uPnP I suspect. Rapidly reaching the
>>>> conclusion I am asking for trouble and may have to try a different approach, such as putting them on different subnets until it’s done. Don’t really want to do that, because firstly it’s a >pain, but secondly my NAS is on the LAN and it will make things quite difficult without it.
>>>> I have tried Googling about this but again not much out there for this strategy.
>>>>> So, am I simply asking for trouble or should I be turning of uPnP
>>>> somehow ? If the answer is yes, you are asking for trouble, then I
>>>> will make other plans, hope not, but rather know now 😊
>>>> Any thoughts appreciated.
>>> Definitely do-able just clear pin in mythtv-setup some more info
>> Not a big deal, but one of the Services API endpoints needs a PIN. This will fail.
> Thanks everyone for your answers that is great
> I would like to move to v30 but I am doing this on CentOS and currently using RPMFusion and as far as I can tell the latest there is v29.1. At the moment I am in the POC stage so if I can I will definitely move to v30
> mythtv-users mailing list
> mythtv-users at mythtv.org
> MythTV Forums: https://forum.mythtv.org
More information about the mythtv-users