[mythtv-users] mythfrontend database connection errors

[Michael T. Dean]

On 03/05/2010 01:04 PM, Shreyas A wrote:
> After upgrading to mythtv 0.22, mythfrontend has trouble connecting to 
> the database. The logs show that the errors always start occurring 
> after the third DB connection is setup. mythbackend has no troubles 
> connecting to the database, and I've checked 
> /usr/share/mysql/charsets/Index.xml file and latin1 is listed as a 
> valid character set. Any pointers as to how to fix this problem?
>
> Here is the relevant part of the mythfrontend logs...
>
> 2010-02-27 17:00:08.441 TV: Changing from None to Watching 
> WatchingPreRecorded2010-02-27 17:00:08.441 New DB connection, total: 3
> ^GCharacter set 'latin1' is not a compiled character set and is not 
> specified in
>  the '/usr/share/mysql/charsets/Index.xml' file
> 2010-02-27 17:00:08.442 Realtime priority would require SUID as 
> root.2010-02-27 17:00:08.442 Unable to connect to database!
> 2010-02-27 17:00:08.442 Driver error was [1/2019]:QMYSQL: Unable to 
> connect
> Database error was:
> Can't initialize character set latin1 (path: /usr/share/mysql/charsets/)
>
> QSqlQuery::exec: database not open
> ^GCharacter set 'latin1' is not a compiled character set and is not 
> specified in
>  the '/usr/share/mysql/charsets/Index.xml' file
> QSqlQuery::exec: database not open
> 2010-02-27 17:00:08.493 No error type from QSqlError? 
>  Strange...2010-02-27 17:00:08.543 Database not open while trying to 
> load setting: UseVideo
> Timebase
> 2010-02-27 17:00:08.546 Video timing method: USleep with busy wait
> ^GCharacter set 'latin1' is not a compiled character set and is not 
> specified in the '/usr/share/mysql/charsets/Index.xml' file
> 2010-02-27 17:00:11.547 Unable to connect to database!
> 2010-02-27 17:00:11.547 Driver error was [1/2019]:
> QMYSQL: Unable to connect
> Database error was:
> Can't initialize character set latin1 (path: /usr/share/mysql/charsets/)
>
> QSqlQuery::exec: database not open
> ^GCharacter set 'latin1' is not a compiled character set and is not 
> specified in the '/usr/share/mysql/charsets/Index.xml' file
> QSqlQuery::exec: database not open
> 2010-02-27 17:00:11.598 No error type from QSqlError?  Strange...

That's definitely a MySQL problem.  Either you have a broken MySQL 
install or you need to upgrade because 
http://bugs.mysql.com/bug.php?id=45058 is actually hitting you.  Upgrade 
to MySQL to 5.1.43+, 5.5.1+, or 6.0.14+.  Or, based on comments in that 
bug, maybe you're actually using a version with the first patch in it 
but without the second patch (which would explain why you're the 
first/only person to have seen this issue) and you need to either 
downgrade MySQL (to the versions before the aforementioned) or upgrade 
to a version that contains the 2nd patch (which seems to fix problems 
caused by the 1st patch).

Mike