[mythtv-users] Second Backend disabling primary backend tuners

[Josh White]

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?

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080211/06bb4b88/attachment.htm