[mythtv-users] [mythtv-commits] Ticket #9742: Mythtv-setup fails to create the initial database
Michael T. Dean
mtdean at thirdcontact.com
Wed Apr 20 18:46:51 UTC 2011
On 04/20/2011 01:32 PM, Frank Phillips wrote:
> On Wed, Apr 20, 2011 at 10:55 AM, Michael T. Dean wrote:
>> On 04/19/2011 03:12 PM, Michael T. Dean wrote:
>>> On 04/19/2011 02:58 PM, MythTV wrote:
>>>> #9742: Mythtv-setup fails to create the initial database
>>>>
>>>> I have installed mythtv, and mysql. After creating the initialdatabase,
>>>> mythtv-setup can not find the tables it needs.
>>> We /think/ this is an issue with MySQL 5.5 (but don't know what's
>>> causing it, yet). I'll try to install MySQL 5.5 and do some testing
>>> soon.
>> OK, it's definitely not a MySQL 5.5 issue. I upgraded to MySQL 5.5 and
>> was able to create an initial database using mythtv-setup from
>> 0.24-fixes and unstable. I even tried 0.24-fixes from before the MySQL
>> 5.5 fixes (which went in on Apr 16), but still using MySQL 5.5, and it
>> was still able to create the initial DB. (Regardless, any user who has
>> MySQL 5.5 /must/ install a version of MythTV that has MySQL 5.5
>> support--0.24-fixes or unstable from Apr 17 or later.)
>>
>> Therefore, it must be some problem caused by the configuration. I'd
>> like to see a MySQL my.cnf (usually, /etc/my.cnf or /etc/mysql/my.cnf)
>> from a system that had this issue.
> I believe all the reporters were running 0.24 proper rather than 0.24-fixes.
> The packager for ArchLinux has stuck to 0.24. I will poke him and point him
> here as a reason to move to 0.24-fixes. I don't believe there is a
> configuration issue, unless you have seen reports of the
> "mythconverg.settings doesn't exist" variety that are running 0.24-fixes?
>
> cedric (5.5.9/5.5.11& exported-0.24)
> http://www.mythtvtalk.com/fresh-ach-linux-install-cannot-create-initial-database-mythconverg-14687/
> http://www.mythtvtalk.com/table-mythconverg-settings-doesnt-exist-14526/
> http://code.mythtv.org/trac/ticket/9742
>
> eratosthenes (exported-0.24& probably 5.5.8)
> https://bbs.archlinux.org/viewtopic.php?pid=893814#p893814
>
> nicoalas: (probably exported-0.24/5.5.11)
> https://bbs.archlinux.org/viewtopic.php?id=116540
Thanks, Frank. It's definitely important for them to run a version that
works with MySQL 5.5, if they're using MySQL 5.5, so we do need to get
them to upgrade to -fixes (even though it won't fix this issue).
I /think/ however, I've figured out what's going on. I was able to
reproduce the symptoms, using an "unusual" approach to creating the
MythTV database. What I found is not a MySQL 5.5 issue--it would be the
same on any MySQL version. The problem seems to be caused by a
combination of using an over-privileged MySQL user and an issue in Qt.
I have a fix that I'll be pushing shortly, so if the Arch packager (is
that you?) could make available packages for the new version with the
fix, that may solve the problem.
Basically, I was able to reproduce the symptoms by using the MySQL root
user to access the database (actually specified root in the mythtv-setup
dialog asking for database connection information). However, the same
problem would occur if any other user that had access to any
non-mythconverg tables were specified (so, if the mythtv MySQL user had
access to tables in some other database on the same MySQL server, it
would give the same failure). I'm guessing, however, that these users
are actually specifying the MySQL root user--in which case, it would be
good to explicitly document that they should use the less-privileged
mythtv user they just created (if asked for database connection
information) in your HOWTO at
https://wiki.archlinux.org/index.php/MythTV_HOWTO#Setting_up_the_database .
Since the HOWTO tells them to create a mysql.txt that specifies the
mythtv user, it may not be what's happening, but it's the only way I
could repro the symptoms.
Anyway, let me get the patch in place, and I'll follow up with the
revision information in here a bit later.
Thanks,
Mike
More information about the mythtv-users
mailing list