[mythtv-users] Sudden seemingly-random database issues

[Tom Lichti]

On Sat, Sep 27, 2014 at 3:56 PM, Brian S <inanimatecrbnrod at hotmail.com>
wrote:

>
>> Next, I was able to get the mysql daemon to start by adding the
> "innodb_force_recovery = 2" flag to /etc/mysql/my.cnf. First tried =1 and
> got the same error as previously noted.
>
> With mysql up and running I checked all databases/tables with:
> mysqlcheck -c -u root -p --all-databases
> Output indicated all tables in both the mysql database and the mythconverg
> database were "OK." (again can attach output if useful).
> This may have been a bad idea, but with mysql running with the force
> recovery option, I was able to start the BE process successfully and begin
> watching a program on the FE. The DB check on mythweb also indicated all
> the mythconverg tables were ok.
>
> So based on what I have been able to find, the next step seems to be to
> dump all the tables and then restore a copy of them, however based on what
> I have so far, a corrupt table doesn't seem to be the problem(?), so I'm
> not sure dumping/restoring is the best way to go. Would this be the logical
> next step, or should I try something else?
>
> Thanks again for all your help.
>
>
The reason myisamcheck didn't work is because it's for fixing ISAM tables,
not InnoDB. It looks like you've got it working, I would make a backup,
just so you have one, but it's probably not necessary. I'd also remote the
force recovery flag, otherwise it's likely going to do it every time you
start mysql.

Good work!

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140927/66d7f1ba/attachment.html>