MythTV v29.0 upgrade

Da_Coynul · 2017-08-13 12:56:51

After an upgrade from 0.28.1 to v29.0, my frontend box was unable to connect to the backend. Commandline output from mythfrontend showed:

Start up failure. host 192.168.1.223, status beAwakeFail

On startup, mythbackend commandline output showed:

Running as a slave backend

...strange because this backend had always been a master backend, never a slave.

Searches here, mythtv.org and the mythtv mailing lists turned up no reference to this issue. I took a look at the mysql database, saw no obvious problems and decided to re-run mythtv-setup on the backend. I saw that 'This server is the Master Backend' was checked but I unchecked and rechecked it, then exited saving changes. That did the trick. On restart, mythbackend came up as master and my frontend connected right away!

I did not see anything in the MythTV documentation about needing to re-run mythtv-setup after an upgrade, so I don't know if this is a mythtv bug or just a quirk with my particular setup. Anyway, I hope this helps someone else who comes across this problem

Last edited by Da_Coynul (2017-08-13 13:19:40)

farmerdave · 2017-08-20 06:53:54

Thanks Da_Coynul, I upgraded to the same version and was having the exact same issue. Your post saved me a lot of trouble!

sultanoswing · 2017-08-25 06:04:16

As you've both discovered, you do indeed have to (re)run mythtv-setup once so that it can upgrade the backend database.

I also had the same issue, and this led me to discover that it is documented somewhere, can't recall where though.

Da_Coynul · 2017-08-25 10:57:40

sultanoswing wrote:

As you've both discovered, you do indeed have to (re)run mythtv-setup once so that it can upgrade the backend database.
I also had the same issue, and this led me to discover that it is documented somewhere, can't recall where though.

FWIW the database is updated by running mythbackend for the first time after the upgrade. So updating the database - at least by that method alone - does not solve the problem.

Last edited by Da_Coynul (2017-08-25 22:03:26)

sultanoswing · 2017-08-29 06:27:04

Da_Coynul wrote:

sultanoswing wrote:
As you've both discovered, you do indeed have to (re)run mythtv-setup once so that it can upgrade the backend database.
I also had the same issue, and this led me to discover that it is documented somewhere, can't recall where though.
FWIW the database is updated by running mythbackend for the first time after the upgrade. So updating the database - at least by that method alone - does not solve the problem.

It seemed to for me, but I guess as they say, YMMV (and I didn't look into this in any detail).

Last edited by sultanoswing (2017-08-29 06:27:17)

Arch Linux

#1 2017-08-13 12:56:51

MythTV v29.0 upgrade

#2 2017-08-20 06:53:54

Re: MythTV v29.0 upgrade

#3 2017-08-25 06:04:16

Re: MythTV v29.0 upgrade

#4 2017-08-25 10:57:40

Re: MythTV v29.0 upgrade

#5 2017-08-29 06:27:04

Re: MythTV v29.0 upgrade

Board footer