<br><br><div><span class="gmail_quote">On 11/4/07, <b class="gmail_sendername">Paul Harrison</b> <<a href="mailto:mythtv@dsl.pipex.com">mythtv@dsl.pipex.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Eric Robinson wrote:<br>> Before I get into stuff, I'll give some background to my situation.<br>><br>> Last Wednesday evening I installed the packages required for MythDVD<br>> to be able to import properly. Things went slowly but I eventually
<br>> got it to work.<br>><br>> Thursday comes around and all of a sudden the Frontends started<br>> hanging. I went downstairs and found a crazy set of error messages in<br>> the terminal running mythbackend. Some huge block of MYSQL selections
<br>> and such that came up in an error surrounded by fairly normal reports.<br>><br>> It turns out that the Mythtv error logs had gotten to be several<br>> gigabytes in size and actually filled the filesystem, making booting
<br>> and any actual operation a chore for the system. After deleting the<br>> files, the system returned to its peppy self.<br>><br>> [The error logs contained seemingly endless copies of the same report:<br>
> some error from libdvdread (or something) saying it couldn't access<br>> the drive.]<br>><br>> I ran mythtv-setup while the computer was in that filled up state and<br>> screwed up the mysql settings. After I made room on the drive I ran
<br>> it again and filled all the settings with the standard affair. My<br>> /etc/mythtv/mysql.txt file now contains the following:<br>><br>> DBHostName=localhost<br>> DBUserName=mythtv<br>> DBName=mythconverg
<br>> DBPassword=mythtv<br>><br>><br>> However, I still cannot log into mythbackend. Here's the sequence I<br>> now try to follow without any results:<br>><br>> 1. mysql -u root mythconverg
<br>> 1. grant all on mythconverg.* to mythtv@" 192.168.10.%"<br>> identified by "mythtv";<br>> 2. flush privileges;<br>> 2. mythtv-setup<br>> 1. all settings default (this was what I used to set up the
<br>> computer initially and had everything running smoothly).<br>> 2. Snipped terminal output sample (from mythtv-setup):<br>> QSqlQuery::exec: database not open<br>> QSqlQuery::exec: database not open
<br>> 2007-11-04 12:04:53.365 DB Error (KickDatabase):<br>> Query was:<br>> SELECT NULL;<br>> No error type from QSqlError? Strange...<br>> 2007-11-04 12:04:
53.419 Unable to connect to database!<br>> 2007-11-04 12:04:53.420 Driver error was [1/1045]:<br>> QMYSQL3: Unable to connect<br>> Database error was:<br>> Access denied for user 'mythtv'@'localhost' (using
<br>> password: YES)<br>><br>> QSqlQuery::exec: database not open<br>> QSqlQuery::exec: database not open<br>> 2007-11-04 12:04:53.474 DB Error (KickDatabase):
<br>> Query was:<br>> SELECT NULL;<br>> No error type from QSqlError? Strange...<br>> 2007-11-04 12:04: 53.528 Database not open while trying to<br>> load setting: Language
<br>> 3. mythbackend<br>> 1. Terminal output:<br>> 2007-11-04 12:07:51.453 Using runtime prefix = /usr<br>> 2007-11-04 12:07:51.460 New DB connection, total: 1<br>> 2007-11-04 12:07:
51.464 Unable to connect to database!<br>> 2007-11-04 12:07:51.464 Driver error was [1/1045]:<br>> QMYSQL3: Unable to connect<br>> Database error was:<br>> Access denied for user 'mythtv'@'localhost' (using
<br>> password: YES)<br>><br>> QSqlQuery::exec: database not open<br>> QSqlQuery::exec: database not open<br>> 2007-11-04 12:07:51.518 DB Error (KickDatabase):
<br>> Query was:<br>> SELECT NULL;<br>> No error type from QSqlError? Strange...<br>> 2007-11-04 12:07: 51.573 Failed to init MythContext, exiting.<br>><br>> Anyone have any idea why I'm unable to connect? Anyone have any ideas?
<br>><br>> I tried changing the "Host" value in mythtv-setup but that change<br>> wasn't reflected in /etc/mythtv/mysql.txt. Is that expected?<br>><br>> Thanks!<br>><br>> - Eric<br>>
<br>Check you haven't got other mysql.txt files in other locations with<br>different settings. ~/.mythtv/mysql.txt and<br>'/usr/share/mythtv/.mysql.txt are common locations. Not sure if<br>/etc/mythtv/mysql.txt is even one of the locations searched?
<br><br>Paul H.</blockquote><div><br>[Sorry for that last top-post. Can't remember which is bad and which isn't.]<br><br>~/.mythtv/mysql.txt exists now (it didn't after the computer crash). It contains the following:
<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">DBHostName=<a href="http://127.0.0.1">127.0.0.1</a><br>DBUserName=mythtv<br>DBPassword=mythtv
<br>DBName=mythconverg<br>DBType=QMYSQL3</blockquote><div><br>followed by a whole lot of commented lines with various options. I don't think this reflects the changes I make in mythtv-setup or the General settings menu in mythfrontend. However, if I change that file directly so that DBHostName is my
192.168.x.x IP address, then that's reflected in the output of mythbackend! That was likely the problem! Thanks!<br></div><br>I also checked /usr/share/mythtv/.mysql.txt and it's nothing more than a symbolic link to /etc/mythtv/mysql.txt:
<br><br>lrwxrwxrwx 1 root root 21 2007-10-19 00:43 mysql.txt -> /etc/mythtv/mysql.txt<br></div></div><br>Back in business! Thanks!<br>