[mythtv-commits] Ticket #5250: 21-fixes mythtv-setup doesn't upgrade/install database
MythTV
mythtv at cvs.mythtv.org
Fri Apr 25 18:49:41 UTC 2008
#5250: 21-fixes mythtv-setup doesn't upgrade/install database
------------------------------+---------------------------------------------
Reporter: udovdh at xs4all.nl | Owner: ijr
Type: defect | Status: new
Priority: major | Milestone: 0.21.1
Component: mythtv | Version: 0.21-fixes
Severity: medium | Resolution:
Mlocked: 0 |
------------------------------+---------------------------------------------
Comment(by sphery <mtdean at thirdcontact.com>):
I just spent about 3 hours testing the creation of the DB schema in an
empty database (as created with mc.sql). The only way I could get a
failure like the above (i.e. where the only output is, "Couldn't upgrade
database to new schema," was by selecting, "Exit," rather than, "Upgrade,"
when prompted for permission to upgrade the DB. (I ran at least 10
different tests trying everything I could think of short of modifying the
MySQL privileges for the mythtv user--since mc.sql, when executed
properly, sets them.)
Note, also, that all of the DB Errors shown above are expected on a new
install (i.e. from trying to set settings before the schema is created).
The only real error is, "Couldn't upgrade database to new schema."
Although the database backup failed with, "DBUtil Error: Error backing up
database: mysqldump ... (512)," where the specified status code is
typically due to improper MySQL permissions (probably MySQL GRANTs since
mythtv-setup was able to connect to a database), such a failure is
possible for the built-in backup even on a properly-configured system, so
this is not proof of an issue.
In discussion with the reporter ( http://mythtv.org/pipermail/mythtv-
users/2008-April/221030.html and http://mythtv.org/pipermail/mythtv-
users/2008-April/221033.html ), the reporter said he selected, "Upgrade,"
not, "Exit." He also complained of segfaults while setting up (
http://mythtv.org/pipermail/mythtv-users/2008-April/221027.html ), then
said, "After some tinkering setup ran. (all of a sudden)", but didn't
provide details about what "tinkering" occurred.
This definitely worksforme. Without more information, I cannot think of
any way to duplicate it. This log does not look like the log that would
occur with an actual failure to upgrade the schema. It's missing some
information, such as the errors that should be logged for
MYTH_SCHEMA_ERROR and the "Newest Schema Version" line, which should
always be output in the event that "Upgrade" is selected at the prompt--
meaning it didn't even get to doUpgradeTVDatabaseSchema()).
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5250#comment:1>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list