[mythtv-users] Two master backends on the same network?
Raymond Wagner
raymond at wagnerrp.com
Sat Feb 15 22:45:31 UTC 2014
On 2/15/2014 5:38 PM, Jon N wrote:
> Is it possible to have 2 master backends on the same network? Although
> the reason why is kind of a long story, I'm trying to do this
> temporarily. But when I start the backend on the new computer it says
> it's starting in slave mode. It also can not connect to the database,
> which makes sense because it uses a different password.
>
> I've gone into the settings and put in either 127.0.0.1 for the ip
> address for that computer, but it didn't help. Can mythtv find other
> instances of the backend over the network even without being told the
> ip address for it? Any way I can get this backend to run as a master
> even with the other one still present?
Each cluster has only one database, and that database defines one master
backend. If you intend to operate two master backends, they will need
separate databases and will operate separate clusters. The two will be
unable to share content between each other.
The only issue with running two clusters on one common network is in the
UPnP auto-detection. When no database is specified, frontends and
backends alike will attempt to find the master backend using UPnP. When
successful, they then query the master backend for the database
credentials it is using, and try to use that themselves. The PIN number
you can configure in mythtv-setup is intended to prevent
auto-configuration from hooking into the wrong cluster. A PIN of 0000
turns off protection, and allows anything to query those credentials.
An empty PIN disables auto-configuration entirely, and allows nothing to
query those credentials.
More information about the mythtv-users
mailing list