[mythtv-users] help with v0.28->v29 on Ubuntu 16.04
Vincent McIntyre
vincent.mcintyre at gmail.com
Sun Nov 11 02:48:51 UTC 2018
On Sun, Nov 11, 2018 at 02:58:13PM +1300, Stephen Worthington wrote:
>
> 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
After upgrading I did a status check of mythtv and mythtv-backend;
mysql was still running (had not been restarted) but the backend
had started a few seconds before I checked. So it seems that in
my case the startup did get invoked ok.
But mythtv-setup had not been run at this point.
When I went over to the TV the frontend was complaining about
protocol mismatch; I did not make a note of whether it was
the backend or frontend that was the old version. What I did
was immediately exit and wait for the frontend to autorestart;
that cleaned up the protocol error so I assume it was the frontend
that had the old version. At this point I was in the startup status
page with the four options at the bottom. I tried to run 'setup'
from there but never got it to work.
In all versions of myth on ubuntu that I have used to date,
I could never get the backend to stop via the GUI prompts
before running mythtv-setup proper.
I have always stopped the backend in another terminal window,
do the -setup razzle dazzle and then manually start the backend again
in the other terminal window. I did not do that in this instance,
because as soon as you touch anything the frontend tries to contact
the backend. Instead I went old-school as described in the [fixed]
email I sent a little while ago.
Thanks
Vince
More information about the mythtv-users
mailing list