[mythtv-users] mythtv-users Digest, Vol 138, Issue 75

[Nicolas Krzywinski]

Am 26.09.2014, 05:13 Uhr, schrieb <mythtv-users-request at mythtv.org>:

> Message: 3
> Date: Thu, 25 Sep 2014 10:08:47 -0400
> From: Tom Lichti <tom at redpepperracing.com>
> To: Discussion about MythTV <mythtv-users at mythtv.org>
> Subject: Re: [mythtv-users] Sudden seemingly-random database issues
> Message-ID:
> 	<CACXumDkT+JOPZaz3vw4VVYSFOW18m_VCB=vvwwjsDoo==fYxVg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> On Wed, Sep 24, 2014 at 9:47 PM, Brian S <inanimatecrbnrod at hotmail.com>
> wrote:
>
>>  On Mon, Sep 22, 2014 at 8:01 PM, Brian S <inanimatecrbnrod at hotmail.com
>>> <mailto:inanimatecrbnrod at hotmail.com>> wrote:
>>>
>>>  --- Wall of text deleted ---
>>>
>>> I think one of the fixes posted here will probably help:
>>>
>>> http://askubuntu.com/questions/127264/cant-start-
>>> mysql-mysql-respawning-too-fast-stopped
>>>
>>> Tom
>>>
>>>
>> InnoDB: Failing assertion: purge_sys->purge_trx_no <=
>> purge_sys->rseg->last_trx_no
>> InnoDB: We intentionally generate a memory trap.
>> InnoDB: Submit a detailed bug report tohttp://bugs.mysql.com <
>> http://bugs.mysql.com/>.
>> InnoDB: If you get repeated assertion failures or crashes, even
>> InnoDB: immediately after the mysqld startup, there may be
>> InnoDB: corruption in the InnoDB tablespace. Please refer to
>> InnoDB:http://dev.mysqlto  
>> .com/doc/refman/5.5/en/forcing-innodb-recovery.html
>> InnoDB: about forcing recovery.
>>
> I would start there, especially if you get that every time you try to
> startup mysql.
> Tom
There is a main question to answer in your situation, prior to chosing  
appropriate actions.
The data that the corrupted logic contains is:
a) important
b) nice to have
c) completely replacable

For c), removing the mysql packages inclusive configuration, followed by  
reinstall (and restore of a backup afterwards) would be easiest and  
quickest
For b), the time for recovery actions should be limited
For a), first backup the current state without altering anything! (disk  
image or file copy e. g.)

Regarding your issue:
MySQL is the database server, which seems to be fine in your case. But to  
provide any functionality, a database server needs a storage engine,  
InnoDB in your case (MyISAM is an example of another engine). Therefore, a  
working storage engine is mandatory for successful mysql startup - which  
fails in your case.
It says the InnoDB data files are corrupt and it can not read/build the  
table structure therefore. Ignore any auxiliary recovery actions therefore  
(e. g. apparmor) and concentrate on repair of the InnoDB file(s).
I did the same (or similar) as you some times ago and I can remember that  
it was possible to really nice and quickly fix this via the mysqladmin  
command .... as far as I remember. This command did worked without the  
need to start the mysql server process prior. You have to execute it on  
the affected machine locally, of course. Now I am not sure about the  
authentication part .... it may be possible that you are authenticated  
automatically for the mysqladmin command if it is executed as root, but  
this is really unsure now.

Please apologize any errors/confused parts in my text as I am in vacations  
right now and am writing this via onscreen keyboard on a tablet (onboard  
on ubuntu) while sitting in the hotel room, consuming free wifi.. ;-)

Good luck!
Nicolas

-- 
Erstellt mit Operas E-Mail-Modul: http://www.opera.com/mail/