[mythtv-users] help with v0.28->v29 on Ubuntu 16.04

[Stephen Worthington]

On Sun, 11 Nov 2018 12:01:43 +1100, you wrote:

>Hi
>
>I need a nudge in the right direction here.
>I upgraded to v29 today and cannot get the setup
>procedure to talk to the database.
>
>I started with a combined be/fe running 0.28 on Ubuntu 16.04.
>
>The database is configured to listen only to localhost
>(bind-address = 127.0.0.1)
>This host has always been the one and only backend so
>it is therefore also the master backend but I do not
>recall ever explicitly marking it as such.
>
>After I upgraded the frontend complained about different
>protocol versions between it and the database, as expected.
>
>I restarted the frontend and it came up in the
>'MythTV Startup Status' screen telling me it can't connect
>to the backend. Not exactly expected but not unexpected either.
>Check the settings in the 'setup' screen. All correct,
>identical to what is in /etc/mythtv/config.xml.
>The frontend user has exactly the same info in ~/.mythtv/config.xml.
>
>I can connect using the mysql commandline client and the credentials
>in that file, so the credentials it is trying to use are ok.
>
>In mysql.log, every time the startup status page tries to connect,
>I get this error, which shows something is amiss.
> $ tail -1 /var/log/mysql/error.log
> 2018-11-10T23:49:45.327034Z 705 [Note] Got an error reading communication packets
>I don't see this with the mysql commandline client.
>(The database backend is still mysql-5.7, not mariadb.)
>
>I also looked at mythweb which threw this error:
>  !!NoTrans: MasterServerIP or MasterServerPort not found! You may need to check your mythweb.conf file or re-run mythtv-setup!!
>
>which indicates something is misconfigured in mythtv.
>mythtweb did work pre-upgrade.
>
>
>I tried running mythtv-setup manually; stopping the backend and
>the frontend, ssh in as the frontend user and run mythtv-setup.
>The 'host address backend setup' has everything correct except
>the last field - 'master backend name' - which I do not appear
>to be able to change. It uses the actual hostname of the backend,
>rather than 'localhost' which is what I think it should be using.
>Maybe this should not matter but the error about 'MasterServerIP'
>makes me wonder.
>
>So that is where I am. I have not rebooted yet because I don't
>want something to get upgraded while I am not watching and
>making notes. But I guess I will try that eventually.
>
>Any ideas folks?
>Vince

Have you restarted mythbackend?  In 16.04+, the commands to shutdown
mythbackend that are in the database do not work properly, so you may
have upgraded mythbackend on disk, but the running copy will not
changed unless it gets shut down and restarted.  So try manually
shutting down mythbackend and then run mythtv-setup again, before
starting mythbackend.

sudo systemctl stop mythtv-backend

sudo systemctl start mythtv-backend