[mythtv-users] ugraded to 0.29, cannot connect to backend

Greg Woods greg at gregandeva.net
Mon May 28 22:12:29 UTC 2018


On Mon, May 28, 2018 at 10:18 AM Bill Meek <keemllib at gmail.com> wrote:

> On 05/28/2018 09:21 AM, Greg Woods wrote:
> > It turns out that what finally worked was going into mythtv-setup and
> > UN-checking the "this is the master backend" box, saving, going in again,
> > RE-checking that box, and saving. Presumably this made some database
> > changes that fixed the issue.
>
> Would still appreciate full mythtv-setup and mythbackend logs in a pastebin
> if the initial failures are still available. I assume the start date is
> the same as the 1st post here: 2018-05-25.
>

I don't have any mythtv-setup logs. A sample mythbackend log can be found
at http:/www.gregandeva.net/mythbackend.20180525221030.14822.log.txt

The problem is illustrated by the first line containing "slave".

What I do have is some old database dumps, and it looks like Peter Bennett
hit the nail on the head. The old database does not have a MasterServerName
value in the settings table. The newer database, after unchecking and
rechecking the "This is the master  backend server" box, does have this. So
what hosed me up all along was that mythtv-setup was showing me that it was
running on the master backend server, when in fact this was not actually
set up correctly in the database. So whatever process upgrades the database
between 0.28 and 0.29 appears to have missed this.

--Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180528/5d1feeb7/attachment.html>


More information about the mythtv-users mailing list