[mythtv-users] Myth Front End can't connect with database
Lan Barnes
lan at falleagle.net
Wed Apr 4 02:01:07 UTC 2007
Alas, I'm not that far along yet.
I set DBHostName in /home/mythtv/.mythtv/mysql.txt to the server's IP
addr, 192.168.1.66. I checked /etc/my.cnf and there was no IP in it. I
added
bind-address=192.168.1.66
No joy so I tried without it. No joy there there either. BTW, I'm assuming
these could have been the host name assuming it's in /etc/hosts.
lokkit is turned off. /etc/hosts.[deny|allow] are empty. I am rebooting
between tests (superstitiously, I grant you).
I can connect with mythconverg using msql on the server (xena) when I use
-h localhost but not -h xena. Same when I substitute IP addrs.
I cleaned out the logs and rebooted. Here is /var.log/mythtv/mythbackend.log
****
2007-04-03 18:41:49.511 Using runtime prefix = /usr
2007-04-03 18:41:49.946 New DB connection, total: 1
2007-04-03 18:41:49.964 Unable to connect to database!
2007-04-03 18:41:49.966 Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user 'mythtv'@'xena' (using password: YES)
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2007-04-03 18:41:50.027 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
2007-04-03 18:41:50.081 Failed to init MythContext, exiting.
mythtv/mythbackend.log (END)
****
... and here is /var/log/mysqld.log
****
070403 18:39:18 [Note] /usr/libexec/mysqld: Normal shutdown
070403 18:39:18 InnoDB: Starting shutdown...
070403 18:39:19 InnoDB: Shutdown completed; log sequence number 0 43655
070403 18:39:19 [Note] /usr/libexec/mysqld: Shutdown complete
070403 18:39:19 mysqld ended
070403 18:41:00 mysqld started
070403 18:41:01 InnoDB: Started; log sequence number 0 43655
070403 18:41:02 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source
distribution
****
I'm completely baffled as to why I can't get mysql to talk over the
machine's IP addr (I'm a postgres guy, which is OK except now ;-)
I gotta go do a thing, but when I return, I'll be grateful for anyone who
can spare some insight.
Once you've tasted the joys of Myth, it's hard to give it up even for a
little moment :'-( But we will prevail.
On Tue, April 3, 2007 12:03 pm, Donald Webster wrote:
> On the laptop, did you edit your mysql.txt to point to the right db?
>
> On 4/3/07, Lan Barnes <lan at falleagle.net> wrote:
>> Newbie. I installed mythfrontend plus dependencies on my laptop using the
>> MythDora 3.2 DVD image. The back end is MythDora as well. I changed the
back end from 127.0.0.1 (two places, same screen in mythsetup) to
192.168.1.66 (IP mildly changed to give pitifully little protection).
Myth
>> on the server still works, so I assume the changes took in both places.
mythconverge user and password mythtv/mythtv, the default.
>> On the server as root, I ran:
>> mysql -u root mythconverge
>> Then, in mysql> I ran
>> grant all on mythconverge.* to mythtv@"192.168.1.%" identified as
>> "mythtv";
>> flush privileges;
>> Both returned with 0 records updated, which I accepted as success (because
>> I didn't expect any recoprds to change).
>> Now when I go into mythfrontend on the laptop, it goes into the config
screens with the message that it can't connect with the database. What
should I check/do?
>> --
>> Lan Barnes
>> SCM Analyst Linux Guy
>> Tcl/Tk Enthusiast Biodiesel Brewer
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
> --
> AIM: fryfrog
> ICQ: 304825
> WWW: http://www.fryfrog.com
>
--
Lan Barnes
SCM Analyst Linux Guy
Tcl/Tk Enthusiast Biodiesel Brewer
More information about the mythtv-users
mailing list