I ran the following commands and can now run mythbackend.<br><ol><li>mysql -u root mythconverg</li><li>mysql> grant all on mythconverg.* to mythtv@"localhost" identified by "mythtv";<br>mysql> flush privileges;
</li></ol>The hard drive then just keeps chugging and I get a whole bunch of output like this:<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
[mpeg2video @ 0x2abb253dcfb0]invalid cbp at 32 67<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 20 56<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 3 57<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 74 58<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 76 59
<br>[mpeg2video @ 0x2abb253dcfb0]mb incr damaged<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 13 61<br>[mpeg2video @ 0x2abb253dcfb0]mb incr damaged<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 27 63<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 107 64
<br>[mpeg2video @ 0x2abb253dcfb0]mb incr damaged<br>[mpeg2video @ 0x2abb253dcfb0]ac-tex damaged at 51 66<br>[mpeg2video @ 0x2abb253dcfb0]invalid cbp at 1 67<br>[mpeg2video @ 0x2afe83f92fb0]00 motion_type at 118 51<br>[mpeg2video @ 0x2afe83f92fb0]Warning MVs not available
<br>[mpeg2video @ 0x2afe83f92fb0]00 motion_type at 4 55<br>[mpeg2video @ 0x2afe83f92fb0]00 motion_type at 55 57<br>[mpeg2video @ 0x2afe83f92fb0]00 motion_type at 3 56<br>[mpeg2video @ 0x2afe83f92fb0]Warning MVs not available
</blockquote><div><br>What you see above is the tail of all the output. Is it just cleaning up some video footage that didn't get cleaned before the computer ran out of disk space? Should I be concerned?<br><br>Furthermore, I feel that adding "
mythtv@localhost" was a bit weird. Why did changing this get it to work? I don't remember adding that before... the only thing I ever did in mysql was the GRANT ALL on my subnet for mythtv...<br><br>Thoughts? Opinions?
<br><br>Thanks,<br><br>Eric<br></div><br><div><span class="gmail_quote">On 11/4/07, <b class="gmail_sendername">Eric Robinson</b> <<a href="mailto:ryunokokoro@gmail.com">ryunokokoro@gmail.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;">
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 to be able to import properly. Things went slowly but I eventually got it to work.
<br><br>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.
<br><br>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.
<br><br>[The error logs contained seemingly endless copies of the same report: some error from libdvdread (or something) saying it couldn't access the drive.]<br><br>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:
<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">DBHostName=localhost<br>DBUserName=mythtv<br>DBName=mythconverg<br>DBPassword=mythtv
</blockquote><div> <br>However, I still cannot log into mythbackend. Here's the sequence I now try to follow without any results:<br><ol><li>mysql -u root mythconverg</li><ol><li>grant all on mythconverg.* to mythtv@"
192.168.10.%" identified by "mythtv";</li><li>flush privileges;</li></ol><li>mythtv-setup</li><ol><li>all settings default (this was what I used to set up the computer initially and had everything running smoothly).
</li><li>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 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 load setting: Language<br></li></ol><li>mythbackend</li><ol><li>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 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.</li></ol></ol>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 wasn't reflected in /etc/mythtv/mysql.txt. Is that expected?
<br><br>Thanks!<br><br>- Eric<br></div>
</blockquote></div><br>