[mythtv-users] Can't start Mythbackend

[Eric Robinson]

On 11/4/07, Paul Harrison <mythtv at dsl.pipex.com> wrote:
>
> Eric Robinson wrote:
> > Before I get into stuff, I'll give some background to my situation.
> >
> > Last Wednesday evening I installed the packages required for MythDVD
> > to be able to import properly.  Things went slowly but I eventually
> > got it to work.
> >
> > Thursday comes around and all of a sudden the Frontends started
> > hanging.  I went downstairs and found a crazy set of error messages in
> > the terminal running mythbackend.  Some huge block of MYSQL selections
> > and such that came up in an error surrounded by fairly normal reports.
> >
> > It turns out that the Mythtv error logs had gotten to be several
> > gigabytes in size and actually filled the filesystem, making booting
> > and any actual operation a chore for the system.  After deleting the
> > files, the system returned to its peppy self.
> >
> > [The error logs contained seemingly endless copies of the same report:
> > some error from libdvdread (or something) saying it couldn't access
> > the drive.]
> >
> > I ran mythtv-setup while the computer was in that filled up state and
> > screwed up the mysql settings.  After I made room on the drive I ran
> > it again and filled all the settings with the standard affair.  My
> > /etc/mythtv/mysql.txt file now contains the following:
> >
> >     DBHostName=localhost
> >     DBUserName=mythtv
> >     DBName=mythconverg
> >     DBPassword=mythtv
> >
> >
> > However, I still cannot log into mythbackend.  Here's the sequence I
> > now try to follow without any results:
> >
> >    1. mysql -u root mythconverg
> >          1. grant all on mythconverg.* to mythtv@" 192.168.10.%"
> >             identified by "mythtv";
> >          2. flush privileges;
> >    2. mythtv-setup
> >          1. all settings default (this was what I used to set up the
> >             computer initially and had everything running smoothly).
> >          2. Snipped terminal output sample (from mythtv-setup):
> >             QSqlQuery::exec: database not open
> >             QSqlQuery::exec: database not open
> >             2007-11-04 12:04:53.365 DB Error (KickDatabase):
> >             Query was:
> >             SELECT NULL;
> >             No error type from QSqlError?  Strange...
> >             2007-11-04 12:04:53.419 Unable to connect to database!
> >             2007-11-04 12:04:53.420 Driver error was [1/1045]:
> >             QMYSQL3: Unable to connect
> >             Database error was:
> >             Access denied for user 'mythtv'@'localhost' (using
> >             password: YES)
> >
> >             QSqlQuery::exec: database not open
> >             QSqlQuery::exec: database not open
> >             2007-11-04 12:04:53.474 DB Error (KickDatabase):
> >             Query was:
> >             SELECT NULL;
> >             No error type from QSqlError?  Strange...
> >             2007-11-04 12:04: 53.528 Database not open while trying to
> >             load setting: Language
> >    3. mythbackend
> >          1. Terminal output:
> >             2007-11-04 12:07:51.453 Using runtime prefix = /usr
> >             2007-11-04 12:07:51.460 New DB connection, total: 1
> >             2007-11-04 12:07:51.464 Unable to connect to database!
> >             2007-11-04 12:07:51.464 Driver error was [1/1045]:
> >             QMYSQL3: Unable to connect
> >             Database error was:
> >             Access denied for user 'mythtv'@'localhost' (using
> >             password: YES)
> >
> >             QSqlQuery::exec: database not open
> >             QSqlQuery::exec: database not open
> >             2007-11-04 12:07:51.518 DB Error (KickDatabase):
> >             Query was:
> >             SELECT NULL;
> >             No error type from QSqlError?  Strange...
> >             2007-11-04 12:07: 51.573 Failed to init MythContext,
> exiting.
> >
> > Anyone have any idea why I'm unable to connect?  Anyone have any ideas?
> >
> > I tried changing the "Host" value in mythtv-setup but that change
> > wasn't reflected in /etc/mythtv/mysql.txt.  Is that expected?
> >
> > Thanks!
> >
> > - Eric
> >
> Check you haven't got other mysql.txt files in other locations with
> different settings. ~/.mythtv/mysql.txt and
> '/usr/share/mythtv/.mysql.txt are common locations. Not sure if
> /etc/mythtv/mysql.txt is even one of the locations searched?
>
> Paul H.


[Sorry for that last top-post.  Can't remember which is bad and which
isn't.]

~/.mythtv/mysql.txt exists now (it didn't after the computer crash).  It
contains the following:

> DBHostName=127.0.0.1
> DBUserName=mythtv
> DBPassword=mythtv
> DBName=mythconverg
> DBType=QMYSQL3


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!

I also checked /usr/share/mythtv/.mysql.txt and it's nothing more than a
symbolic link to /etc/mythtv/mysql.txt:

lrwxrwxrwx   1 root root    21 2007-10-19 00:43 mysql.txt ->
/etc/mythtv/mysql.txt

Back in business!  Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20071104/619b7c13/attachment.htm