[mythtv-users] Mythtv 29 (aka 0.29) released

[Ian Campbell]

On Thu, 2017-08-03 at 12:06 +0200, Stephan Seitz wrote:
> On Do, Aug 03, 2017 at 10:41:27 +0100, Ian Campbell wrote:
> > On Thu, 2017-08-03 at 11:14 +0200, Stephan Seitz wrote:
> > > 1. DB Upgrade failed
> > 
> > I didn't think I'd hit this one, since I saw no apparent
> > misbehaviour,
> > but checking my logs I have indeed seen this.
> 
> Interesting. After all the backend refuses to start if the DB
> upgrade fails.

My backend is starting. I have DBSchemaVer = 1348 now, from the logs it
looks like I restarted the backend (I don't remember) and it seemed to
have continued with the upgrade:

    $ grep -iE 'schemawizard|dbcheck|schema' /var/log/mythtv/mythbackend.log 
    Aug  1 08:49:38 iranon mythbackend: mythbackend[15357]: I CoreContext schemawizard.cpp:120 (Compare) Current MythTV Schema Version (DBSchemaVer): 1344
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: I CoreContext schemawizard.cpp:273 (PromptForUpgrade) Console is non-interactive, can't prompt user...
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: C CoreContext schemawizard.cpp:298 (PromptForUpgrade) Upgrading.
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: C CoreContext dbcheck.cpp:437 (performActualUpdate) Upgrading to MythTV schema version 1345
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: C CoreContext dbcheck.cpp:437 (performActualUpdate) Upgrading to MythTV schema version 1346
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: C CoreContext dbcheck.cpp:437 (performActualUpdate) Upgrading to MythTV schema version 1347
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: E CoreContext dbcheck.cpp:411 (performUpdateSeries) DB Error (Performing database upgrade): #012Query was: i #012Error was: Driver error was [2/1064]:#012QMYSQL: Unable to execute query#012Database error was:#012You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'i' at line 1
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: E CoreContext dbcheck.cpp:519 (UpgradeTVDatabaseSchema) Database schema upgrade failed.
    Aug  1 08:51:00 iranon mythbackend: mythbackend[15357]: E CoreContext main_helpers.cpp:571 (run_backend) Couldn't upgrade database to new schema
    Aug  1 08:54:58 iranon mythbackend: mythbackend[2614]: I CoreContext schemawizard.cpp:120 (Compare) Current MythTV Schema Version (DBSchemaVer): 1346
    Aug  1 08:56:34 iranon mythbackend: mythbackend[2614]: I CoreContext schemawizard.cpp:273 (PromptForUpgrade) Console is non-interactive, can't prompt user...
    Aug  1 08:56:34 iranon mythbackend: mythbackend[2614]: C CoreContext schemawizard.cpp:298 (PromptForUpgrade) Upgrading.
    Aug  1 08:56:34 iranon mythbackend: mythbackend[2614]: C CoreContext dbcheck.cpp:437 (performActualUpdate) Upgrading to MythTV schema version 1347
    Aug  1 08:56:34 iranon mythbackend: mythbackend[2614]: C CoreContext dbcheck.cpp:437 (performActualUpdate) Upgrading to MythTV schema version 1348
    Aug  1 08:56:34 iranon mythbackend: mythbackend[2614]: I CoreContext dbcheck.cpp:523 (UpgradeTVDatabaseSchema) Database schema upgrade complete.
    Aug  1 09:00:15 iranon mythbackend: mythbackend[2612]: I CoreContext schemawizard.cpp:120 (Compare) Current MythTV Schema Version (DBSchemaVer): 1348
    Aug  1 09:13:36 iranon mythbackend: mythbackend[3971]: I CoreContext schemawizard.cpp:120 (Compare) Current MythTV Schema Version (DBSchemaVer): 1348

> > > 

> > When it hangs there are some log messages about VDPAU as the last
> > things in mythfrontend log. Which is odd because I'm using VAAPI
> > with
> 
> Yes, but the old frontend had VDPAU errors as well.

My logs from the 0.28 era seem to have reotated away (already, I need
to look into that since it's only been a few days).

>  I have a notebook 
> with a Core i7 and integrated Intel.

Mines a Core 2 Duo CPU E8200 with an integrated i915.

> Do you have to change some video configuration in the frontend?

I haven't made a change to the video configuration. I did at one point
go into the video settings and reselect the VAAPI option and switch
to/from the VPDAU settings before putting it back to the original VAAPI
setting.

The failure is intermittent and I've not had a chance to investigate
fully yet, so I don't have a solution.

Ian.