[mythtv-users] Possible Errata/Bug Myth

[Chris Everest]

While performing a fresh install of MythTV (mythtv-suite-0.19-57.at) on FC5
for use a slave backend, the command:

service mythbackend start

this will not start the slave backend properly.  An error in the log stated
that the master database could not be found while attempting to connect to
mysqld on localhost.  The only workaround was to start the slave backend by
running the server directly with command:

 /etc/rc.d/init.d/mythbackend start

I have been using this workaround since the release of FC5.  Today I
realized the mythtv-setup program was using /root/.mythtv/mysql.txt for
backend configuration while the Fedora service interface was using
/.mythtv/mysql.txt.  Yes, that is right! It was created in the root
dorectory.  This caused the mysql.txt file to be created (if not already
present) with the default value of localhost as the master backend hostname.

Is this a bug/errata?  I tried the same exact installation on both i686 and
x86_64 with the same results.  The only difference on the slave and the
master installs is that I did not create a mythtv user before the
mythtv-suite was installed.  I suspect that the installation on the slave
without a user already created, built the mythtv user as a 'no login and no
rights' kind of user and it's profile and path were junked. As soon as I
edited the /.mythtv/mysql.text to the correct master backend hostname the
service and chkconfig interfaces worked again.  Now this is not the correct
place for the config to be placed.  Can anyone tell how to move that config
to /var/lib/mythtv/mysql.txt so that the service interface uses it corectly?

The error message is here:

2006-04-09 18:10:30.730 Using runtime prefix 2006-04-09 18:10:30.752 Unable to read configuration file mysql.txt
2006-04-09 18:10:30.753 Trying to create a basic mysql.txt file
2006-04-09 18:10:30.770 Writing settings file //.mythtv/mysql.txt
2006-04-09 18:10:30.797 New DB connection, total: 1
2006-04-09 18:10:30.801 Unable to connect to database!
2006-04-09 18:10:30.802 Driver error was [1/2002]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2006-04-09 18:10:30.857 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError?  Strange...
2006-04-09 18:10:30.908 Failed to init MythContext, exiting.

Someone, please use this post to your advantage.  It's racked my brain for
several weeks.


--
Chris Everest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060416/428faa4c/attachment.htm