[mythtv-users] Upgraded database, myth* can't connect

Hika van den Hoven hikavdh at gmail.com
Fri Nov 13 23:59:31 UTC 2015


Hoi Dale,

Saturday, November 14, 2015, 12:41:56 AM, you wrote:

> On 11/13/2015 05:52 PM, Hika van den Hoven wrote:
>> Hoi Dale,
>> 
>> Friday, November 13, 2015, 11:21:35 PM, you wrote:
>> 
>>> This past weekend I finally upgraded my database, and moved from mysql
>>> to mariadb.  Now none of the normal myth* programs can connect to it.
>> 
>>> I can successfully connect at the command line with: "mysql -u mythtv -p
>>> -h <name> mythconverg".  On the backend system I can omit the "-h",
>>> which I presume means connecting through a Unix socket.  I can connect
>>> to loopback, I can connect to the machine by IP.  I can run the command
>>> from other machines on my network and connect OK.
>> 
>>> Also on the backend system, I can run mythconverg_backup.pl and
>>> optimize_mythdb.pl.  Plus when I unzip the database backup file, it
>>> looks good.
>> 
>>> I just can't run mythtv-setup or mythbackend.  I get:
>>> $ mythbackend
>>> QSqlDatabase: QMYSQL driver not loaded
>>> QSqlDatabase: available drivers: QSQLITE QMYSQL3 QMYSQL
>> 
>>> Cannot login to database
>> 
>>> Would you like to configure the database connection now? [no]
>>> 2015-11-13 14:37:40.452353 C  mythbackend version: fixes/0.26 [v0.26.0]
>>> www.mythtv.org
>>> 2015-11-13 14:37:40.452362 C  Qt version: compile: 4.8.5, runtime: 4.8.5
>>> 2015-11-13 14:37:40.452367 N  Enabled verbose msgs:  general
>>> 2015-11-13 14:37:40.452375 N  Setting Log Level to LOG_INFO
>>> 2015-11-13 14:37:40.452882 I  Added logging to the console
>>> 2015-11-13 14:37:40.452940 I  Setup Interrupt handler
>>> 2015-11-13 14:37:40.452955 I  Setup Terminated handler
>>> 2015-11-13 14:37:40.452964 I  Setup Segmentation fault handler
>>> 2015-11-13 14:37:40.452972 I  Setup Aborted handler
>>> 2015-11-13 14:37:40.452981 I  Setup Bus error handler
>>> 2015-11-13 14:37:40.452987 I  Setup Floating point exception handler
>>> 2015-11-13 14:37:40.452996 I  Setup Illegal instruction handler
>>> 2015-11-13 14:37:40.453005 I  Setup Real-time signal 0 handler
>>> 2015-11-13 14:37:40.453036 N  Using runtime prefix = /usr
>>> 2015-11-13 14:37:40.453060 N  Using configuration directory =
>>> /home/mythtv/.mythtv
>>> 2015-11-13 14:37:40.453125 I  Assumed character encoding: en_US.UTF-8
>>> 2015-11-13 14:37:40.453312 I  Using localhost value of localhost
>>> 2015-11-13 14:37:40.454324 E  Unable to init db connection.
>>> 2015-11-13 14:37:40.454330 E  MSqlDatabase::OpenDatabase(), db object is
>>> not valid!
>>> 2015-11-13 14:37:40.681354 I  Starting mythlogserver
>>> 2015-11-13 14:37:40.681762 I  Starting process manager
>>> 2015-11-13 14:37:40.685529 I  Starting IO manager (write)
>>> 2015-11-13 14:37:40.685783 I  Starting IO manager (read)
>>> 2015-11-13 14:37:40.686091 I  Starting process signal handler
>>> 2015-11-13 14:37:40.786510 I  Added logging to mythlogserver at TCP:35327
>>> ^C^C
>>> $
>>> I can run it as root, I can run it as user mythtv, it doesn't matter.
>>> I've searched on this topic, and the most common diagnosis seems to be
>>> that the user running the command doesn't have access to
>>> ~/.mythtv/config.xme, but that's not the case here.
>> 
>>> There just wasn't that much changed, this worked before the database
>>> upgrade, and the database itself looks good.
>> 
>>> Thanks for any suggestions,
>>> Dale Pontius
>>> _______________________________________________
>> 
>> 
>> I guess qt and maria are not properly linked. Here on Gentoo I simply
>> would rebuild qtsql, but you might need a qt package linked against
>> mariadb?
>> 
> I've rebuilt qtsql already, but I suppose I should go to town with ldd
> and find out if I need to rebuild anything else.  I had a little bit of
> a go-around with UTF-8 (and of course utf-8, which isn't the same thing)
> and have done numerous rebuilds, but maybe I just need to do it again.
> I should be able to walk through things with ldd and see.

> We'll see.
> Dale

> _______________________________________________

Oh, and you have both server and client libraries both in mysql and in
mariadb. They can be in separate package, although I think they can
mix in some way. On different machines the client of the one can
access the server of the other.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens



More information about the mythtv-users mailing list