[mythtv-users] slave/master interaction

[Scot L. Harris]

On Sun, 2005-09-25 at 21:42, Greg Woods wrote:
> How exactly do slave and master backends interact? Is it true that
> mythfrontend running on a slave backend still connects directly to the
> master backend? 
> 
> If that is so, does that mean that when the slave is using its own
> tuner, the traffic has to go from the slave backend to the master
> backend, then back across the net again to the frontend? 
> 
> If that is not so, then what is the process by which a slave will access
> it's own tuner?
> 
> The problem I am having now is that I cannot get my slave backend set up
> correctly. Mythbackend is running, but it acts like it's not. I use
> "netstat" to see that, when mythfrontend is running, it is only
> connected to the master backend, and it can only see the tuners from the
> master backend. I have redone the whole mythtv-setup process on both the
> master and the slave probably a dozen times today, and I still cannot
> figure out how to get the slave backend to use its own tuner. 
> 
> The install instructions for configuring a slave backend lack the detail
> I need to fix this.
> 
> I did check, and the ivtv drivers are loaded correctly and it recognizes
> the PVR-150. This also worked fine before I had to rebuild my database
> this morning. I'm sure there's some secret setting I need to make to get
> this to work, but I can't figure it out.
> 
> --Greg

Just went through this process of setting up a slave backend.  Others
will probably have better suggestions but here is what I know.

Check for multiple copies of mysql.txt files on both systems.  If you
find more than one on a system make sure it is consistent in all
copies.  

Make sure you restart mythbackend on each system after you make changes
using mythtv-setup.  I found that if you don't restart mythbackend on
both system that new tuners are not seen until that is done.


Not sure this was part of the problem I hit but make sure on the
masterbackend that you don't use localhost for the name/IP in the
mythtv-setup.  Use the actual IP or name of the system.  I believe this
defaults to localhost.

If you clear capture cards or channels in mythtv-setup on either the
master or slave you must go back to the other systems and reconfigure
capture cards on all systems.  If you forget to do this capture cards on
the other systems will not be available for use.

I think you need to run mythfilldatabase after configuring/reconfiguring
capture cards so the system will recalculate the schedule and which
capture cards to use.

In mythtv-setup you can specify a priority for each capture card.  In my
case I wanted the system to use the capture cards in the master backend
first before using the ones in the slave backend so I increased value
for those capture cards.  In my case that means that now when I use live
TV (which is not often) I will use a tuner from the slave backend.

Also the order you configure the capture cards appears to define the
number assigned to them that is displayed in mythweb.  I ended up with
the first slave capture card defined first then the two cards on the
master backend.  I added a fourth card to the slave backend and it is
now number 4 in the list.  

Hope that helps.