[mythtv-users] Second Backend disabling primary backend tuners

[Jon]

On Feb 11, 2008, at 8:48 AM, Josh White wrote:

> Is there ever a reason not to input a backend server's IP address,  
> instead of "localhost" or "127.0.0.1" or anything else?  I guess if  
> your backend is connected via DHCP or something it would make sense  
> (assuming a dynamic IP on a server makes sense somehow).  I only  
> have one backend server, and I made sure to input the address  
> anyway, becuase I couldn't think of anything I would lose.  Am I  
> wrong?

You are correct. Using the loopback address works fine for a single  
tuner system, but isn't recommended, because when you add a slave,  
you lose all your frontend settings (because when you add the slave,  
you have to change that IP, and since the IP is tied to localhost,  
and the computer's real IP is tied to a different hostname  
(generally) the database will think this is a new frontend)

The problem comes when you add a slave system. In setup, you have to  
tell EVERY backend what IP belongs to IT and what IP belongs to the  
master. This is imperative. Otherwise the master will try to connect  
to the slave at 127.0.0.1 and will fail to find a slave there (gee,  
wonder why?)

Another issue that I have noticed when I set up my slave backend was  
that mythtv-setup does NOT like it when you try and add cards to your  
slave while the master is running. IE, even though the slave backend  
is not running, when you run mythtv-setup on the slave, and add the  
capture card and tuner, the master backend often ignores the changes.  
If the master is not running when you run setup (on the slave) it  
seems to take everything without complaint.

I don't know if this is a known issue, or just a bug in my system.




> On Feb 11, 2008 11:35 AM, Ronald Frazier <ron at ronfrazier.net> wrote:
> > Sounds alot like you don't have your master/slave relationship  
> set up right.
>
> I was thinking the same thing. I vaguely recall making the same
> mistake and having some similar sort of problems. In each backend you
> have 2 configuration IP's...one for the local backend and one for the
> master backend. When you are configuring the master backend, you can't
> just tell it to use 127.0.0.1 or localhost for the local backend. You
> have to explicitly tell it its own IP address. If you don't do this,
> then you get problems with things not showing up in the frontend like
> they should. I suspect what happens is something like:
> 1) The slave connects to the master correctly
> 2) The master gives it a url to connect to to retrieve stuff
> 3) The slave connect to the url to retrieve the data. However, because
> the master was configured wrong, the url was wrong and the slave ends
> up connecting to itself to retrieve the data (which, of course,
> doesn't exist).
>
> --
> Ron
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080212/2eb507ab/attachment.htm