[mythtv-users] mythbackend fails on initial config

Bruce Markey bjm at lvcm.com
Fri Dec 2 01:34:31 EST 2005

Scott Fones wrote:
> I can't seem to start mythbackend.  I have mysql version 4.1.15 and
> the mc.sql database inserted.  I have qt version 3.3.4 and mythtv
> version .18.1.  Heres what I get when I try to run mythbackend
> mythbackend
> 2005-12-01 19:25:38.261 New DB connection, total: 1
> 2005-12-01 19:25:38.267 Setting Lock for Database Schema upgrade. If
> you see a long pause here it means the Schema is already locked and is
> being upgraded by another Myth process.
> 2005-12-01 19:25:38.268 New DB connection, total: 2
> 2005-12-01 19:25:38.269 Told to create a NEW database schema, but the database
> already has 16 tables.
> If you are sure this is a good mythtv database, verify
> that the settings table has the DBSchemaVer variable.
> 2005-12-01 19:25:38.269 Database Schema upgrade FAILED, unlocking.
> 2005-12-01 19:25:38.269 Couldn't upgrade database to new schema

Well, it can't find a database schema version number which it
writes at the end of any update including the initial update.
There should be about 40 tables but you only have 16. Without
a DBSchemaVer it thinks it should install a fresh database but
you already have about 1/3 of the stuff there. There's the rub.

Whether or not you remember (or would admit to it ;-) the process
died or was killed the first time you ran a myth process.

$ mysql -u mythtv -pmythtv mythconverg
mysql> drop database mythconverg;
mysql> create database mythconverg;
mysql> quit

This will give you a clean, empty DB. Start mythtv-setup by itself
before running any other myth programs. Wait for it to finish
loading the database, uninterrupted, even if this takes a minute
or two.

--  bjm

More information about the mythtv-users mailing list