Re: Kontact broken after upgrading to KDE 4.7.2
Am Freitag, 2. Dezember 2011 schrieb Michael Strobel:
> InnoDB: Last MySQL binlog file position 0 2654, file name
> ./mysql-bin.000003 111201 14:18:26 InnoDB: Started; log sequence
> number 0 8713003 111201 14:18:26 [Warning] Can't open and lock time
> zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying
> to live without them 111201 14:18:26 [ERROR] Can't open and lock
> privilege tables: Table 'mysql.servers' doesn't exist 111201 14:18:26
> [Note] /usr/sbin/mysqld: ready for connections. Version:
> '5.1.58-1' socket:
> '/home/michael/.local/share/akonadi/socket-MacBook/mysql.socket' port
> : 0 (Debian) InnoDB: Error: Removing element from mem pool free list
> 64 though the InnoDB: element is not marked free!
> InnoDB: Apparent memory corruption: mem dump len 500; hex
> 0000000000000000000000000000000000000000000000000000000000000000000000
[…]
> asc
> | P =w_
>
> 0 t 1C 0| (C =w_
>
>
>
> ; InnoDB: Scanning backward trying to find previous allocated
> mem blocks 111201 14:18:26 - mysqld got signal 11 ;
> This could be because you hit a bug. It is also possible that this
> binary or one of the libraries it was linked against is corrupt,
> improperly built, or misconfigured. This error can also be caused by
> malfunctioning hardware. We will try our best to scrape up some info
> that will hopefully help diagnose the problem, but since we have
> already crashed, something is definitely wrong and this may fail.
This and the following doesn´t look like a KDE problem at all.
Did you have a sudden power outage or crash in the last time. I´ve heard
reports that MySQL with the default configuration that Akonadi uses for it
is prone to database corruptions after such occurences.
Here Kontact works with KDE 4.7.2. But I am using a system-wide PostgreSQL
database for it.
As long as only contacts are stored in Akonadi it should be possible to
do:
1) akonadictl stop
2) mv .local/share/akonadi ls -l .local/share/akonadi-broken
3) akonadictl start
Otherwise you would need to repair the database manually for now. Maybe
its sufficient to remove the binlog file(s) - in that case you will loose
some changes to the databases.
But AFAIR even with mail, there is nothing in there, that couldn´t be
rebuilt from source.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: