[mythtv-users] 0.19 Master Backend Can't Connect to Mysql Database

[Nick]

On 14/02/06, Chase Douglas <cndougla at purdue.edu> wrote:
> I have been running mythtv for a while now with a master and a slave
> backend. After upgrading to mythtv 0.19 on both the master and slave,
> the slave can no longer connect. I get the following in the log:
>
> 2006-02-14 00:36:54.469 Using runtime prefix = /usr
> 2006-02-14 00:36:54.487 New DB connection, total: 1
> 2006-02-14 00:36:54.488 Unable to connect to database!
> 2006-02-14 00:36:54.489 Driver error was [1/2002]:
> QMYSQL3: Unable to connect
> Database error was:
> Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)
>
> QSqlQuery::exec: database not open
> QSqlQuery::exec: database not open
> 2006-02-14 00:36:54.541 DB Error (KickDatabase):
> Query was:
> SELECT NULL;
> No error type from QSqlError?  Strange...
> 2006-02-14 00:36:54.601 Failed to init MythContext, exiting.
>
> I updated mysql over the weekend to 4.1.14 and re-emerged qt afterwards
> on both master and slave backends. At that point the slave backend could
> still connect to the master backend with mythtv 0.18.1. Now that I've
> upgraded and can't connect, I tried to re-emerge qt just to rule that
> out, and I still get this error. Then I tried mythtv-setup, and after
> supplying the database information, it connected to the database and was
> able to access everything. However, mythbackend still will not connect
> to it. I'm running Gentoo and using the ebuilds in portage for mythtv on
> the slave and master now (didn't on the master until now). What could be
> wrong?

You don't want to connect to mysql running locally on the slave. If
mythtv-setup can connect to the master, I'd expect your mysql.txt file
to contain the correct settings, but it can't help to reverify them.
Have any hostnames changed?

If you only run a frontend on the slave machine (stop mythbackend on
the slave) can it connect successfully to the master machine?

Nick