[mythtv-users] mythtv v31 slave backend help needed

James Abernathy jfabernathy at gmail.com
Sun Jul 19 17:12:14 UTC 2020

On Sun, Jul 19, 2020 at 4:05 AM John <jksjdevelop at gmail.com> wrote:

> On 18/07/2020 23:36, Jim Abernathy wrote:
> > I have a remote v31 backend with a PCIe tuner card running on Ubuntu
> > 18.04 with mariadb-server.
> >
> > I'd like to add a v31 slave backend running on a RPi4 using a HDHR
> > quatro tuner.
> >
> > Is there a guide on how to set this up? I know how to setup the RPi4
> > as a v31 remote backend, just not sure as to how to make it a slave
> > off of my master. I see one setting in mythtv-setup -> General that
> > has a check box for master or slave. There has to be more than that?
> >
> > 1. Will the slave use the maradb on the Master?
> >
> > 2. Will all frontends see the recordings/ EPG on both the master and
> > slave?
> >
> > Any help would be appreciated. I didn't find much using google and
> > what I did was many versions old.
> >
> > Jim A
> >
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://lists.mythtv.org/mailman/listinfo/mythtv-users
> > http://wiki.mythtv.org/Mailing_List_etiquette
> > MythTV Forums: https://forum.mythtv.org
> I was really surprised how easy it was to set up a slave backend.
> Make sure the new master is accessible remotely over your network ie a
> remote frontend works fine.
> Then starting from a stand alone combined front & backend.
> Uninstalled the database as a slave uses the one on the machine to be
> used as master.
> Altered the config.xml for the slave with the host name pointing to the
> new master.
> Changed the master slave  setting in mythtv-setup .
> When running setup on the slave it should now see the masters database.
> You set up the tuners on the slave locally.
> If you have sources defined on the master the slave can see them so you
> don't need to do channel scan.
> The storage directories on the slave should all be blank in which case
> the system uses those defined on the master.
> The slave should be setup so that it sees the file system on the master
> at the same address.
> I shared the recording folder from the master using samba - works fine
> on a Pi 3B.
> Recordings are then seamlessly accessible on the master .

I seem to have this working.  In my case I want the RPi4 Slave Backend to
use it's HDHR tuners and record it's recordings on the SSD connected to the
Here's what I did to get this working:


   Fresh install or Raspberry Pi OS on RPi4 4GB

   Setup repository and install mythty light per:

   Install pi-utils per: https://github.com/MikeB2013/pi-utils.git

   Modify pi-mythbackend-helper.sh to run just part of the functions:






   Run my modified pi-mythbackend-helper.sh and reboot

   Run mythtv-setup, but expect it to not find the database. Select the
   manual setup button and point it to the Master backend IP address and
   database password.

   Mythtv-setup will then come up as normal and you can setup the options.
   I added the HDHR tuners.

   The Video Source will already have the source from the Master backend.

   I setup the Input Connections as I would on a regular backend setup and
   only scan the first tuner.

   I didn’t setup the Storage Groups on the slave backend.

   I copied the config.xml from “/home/pi/.mythtv/” to “/etc/mythtv/” and

   The hard part for me was to understand the Storage Groups setup for the
   slave backend since you don’t do that when you run mythtv-setup on the
   slave. On my Master Backend for the Storage Group → Default, I have 2
   directories defined:



      This is because I have 2 sets of RAID mirrors for the recordings.

   So to make this work on the slave backend I had to create a directory
   “/mnt/md0/recordings-tv1” on the slave backend owned by mythtv:mythtv with
   permissions 2775.

   At this point I used my Shield TV Android mythtv-frontend and I could
   see all the tuners on both backends and I started recording 8 programs. The
   recordings worked and were spread out over both backends. And as I wanted
   the RPI4’s recordings were in “/mnt/md0/recordings-tv1” on it’s SSD.

Jim A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200719/0eca5122/attachment.htm>

More information about the mythtv-users mailing list