[mythtv-users] Setting up slave backend system

[Bruce Markey]

Isaac Richards wrote:
...
> Everything's stored in the same central database.  Cards don't show up on the 
> master because it requires local access to the card to probe the various 
> available settings & inputs.

This is the correct information for this part of the thread but
ironically, Scot's problem is that everything was not stored in
the same central database. I did a test this morning that may
shed some light on why Scot and many before him have gotten into
a confusing state.

Say there is a host "alpha" (192.168.0.1) running mysqld and MBE
and the user starts to set up a slave on "bravo" (192.168.0.2).

Either there was a mysqld installed on bravo in his distribution
or he thought he was supposed to run a mysqld on the slave. Next
he runs mythtv-setup that unwittingly connects to the local host
or thought he was supposed to connect to the mysqld on the local
machine. Either way, he fills in the IP address for "bravo" as
192.168.0.2 and sets "Master Server IP address:" 192.168.0.1(!).

Now when he start mythbackend, it will make a connections to a
mythbackend master server on it's port on alpha and report:

Running as a slave backend.
...
2005-09-20 11:10:05.795 Connecting to master server: 192.168.0.1:6543

However the mysqld on alpha will know nothing of this slave or
any of the configuration that was written to the mysqld on bravo.

This also suggests that if a frontend was run on bravo it may be
able to find the master and run live TV but the EPG is empty because
the program data is in alpha's DB and the frontend is connecting to
bravo's DB where the program table is empty.

--  bjm