[Solved!] Myth 0.20 & mysql error on new machine

[dspahn]

My myth box is "new"- I just set it up to be dedicated to Myth. I have not yet successfully run Mythtv yet. I have the correct settings to connect to the database, and I get a successful connection message. It's worth mentioning that the database is on a dedicated mysql server, seperate from the myth box. The first error I notice that looks like any form of malcontent says "Told to create a NEW database schema, but the database already has 2 tables. If you are sure that this is a good mythtv database, verify that the settings table has the DBSchemaVar variable." Then "Database Schema upgrade FAILED, unlocking. Couldn't upgrade to database to new schema, exiting.
No such file or directory
apps file failure"

Any ideas how to fix this database?

Thanks!

[Hobbes-X]

This usually happens when a database upgrade is interupted, or in your case, the initial database setup.

It's safe to delete all the tables in the mythconverg database, assuming that you haven't done anything important you want to keep settings wise since you've moved to the new sql server.

Importing mc.sql only creates the database and the initial permissions, mythbackend handles all of the table creation by checking the settings table for a schema version. If it's not there but you have tables, it pukes rather than wipe the database and loose potentialy desired info. You're starting from scratch, so a database wipe should be okay. Deleting the tables is preferable to re-importing mc.sql, since you've got your permissions set correctly.

If you've got some settings already configured on the first myth box you setup, it should be safe to copy the mythconverg database over to the new server too. If you don't, it's not a huge deal, you'll just be starting with the default settings again.

[dspahn]

I confess that I am a n00b at mySQL datbase manipulation. I went to the Myth website and ran the appropriate "drop" command, which I thought did that. After dropping the mythconverg database, I ran the command to feed mysql the myth db script (something like mc.sql?). What should I do to wipe it clean?
FWIW, I have no information that I care about, so I don't care what happens to the database.
Thanks for the help!

[Hobbes-X]

EDIT: Just ran into one other possible hangup- apparently a backend will automatically try and connect through the local mysql socket first, regardless of the mysql.txt settings? The myth docs say it's required to not run the mysql service on a backend machine that isn't also serving MySql.

It might be easiest to start from the beginning:

Make sure you're running on the standalone mysql server (since the command interpreter defaults to localhost, and you want to make sure it drops the database on the correct system), and then run:

[Hobbes-X]

One other note, while you're here...

All the other myth related programs pull from the mysql.txt, so if you run mythfilldatabase manually from the command line, make sure that you've got the correct settings in the current users' ~/.myth/mysql.txt too. Running mythfilldatabase on a machine that isn't local incurrs a performance hit too (It's faster on the local machine). It might be worth installing myth on the mysql server just to run mythfilldatabase.

[dspahn]

I may do that. I shied away from it before because first I needed to emerge Myth, then it wanted to pull in QT.... and so on. I ran most of the commands you posted right before I started getting that error, but your commands are subtly different... I'll let you know tonight after i have some results to post. As always, thanks for your help.

[Hobbes-X]

[dspahn]

From /var/log/mythtv/mythbackend.log:

[Hobbes-X]