[Akonadi] [Bug 334205] New: Error code: 2013 with MariaDB 10.0.10

[Andrea Scarpino]

https://bugs.kde.org/show_bug.cgi?id=334205

Bug ID: 334205
Summary: Error code: 2013 with MariaDB 10.0.10
Classification: Unclassified
Product: Akonadi
Version: 1.12.1
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: server
Assignee: kdepim-***@kde.org
Reporter: ***@kde.org

On Arch Linux system mariadb has been updated to 10.x.

Since that moment I can't use KMail anymore, I get:
"The Email program encountered a fatal error and will terminate now.
The error was:
Failed to fetch the resource collection."

As this is a major update, mysql_upgrade is needed but I *guess* Akonadi
doesn't that automatically.

Reproducible: Always

Steps to Reproduce:
1. Upgrade MariaDB to 10.x
2. Restart Akonadi/system
Actual Results:
Can't start KMail

Expected Results:
Everything works!

* mariadb 10.0.10
* kmail 4.13.0

[Andrea Scarpino]

https://bugs.kde.org/show_bug.cgi?id=334205

--- Comment #1 from Andrea Scarpino <***@kde.org> ---
Created attachment 86397
--> https://bugs.kde.org/attachment.cgi?id=86397&action=edit
akonadi start output

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=334205

Daniel Vrátil <***@redhat.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |***@redhat.com
Resolution|--- |INVALID

--- Comment #2 from Daniel Vrátil <***@redhat.com> ---
DB error: "Lost connection to MySQL server during query" means that the MySQL
server has crashed while running your query.

This is caused either by a bug in MySQL or, more probably, by data corruption.
You can either try to rescue the database using some tools, or just recreate
the database from scratch and reconfigure Akonadi.

[Andrea Scarpino]

https://bugs.kde.org/show_bug.cgi?id=334205

Andrea Scarpino <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Attachment #86397|0 |1
is obsolete| |

--- Comment #3 from Andrea Scarpino <***@kde.org> ---
Created attachment 86398
--> https://bugs.kde.org/attachment.cgi?id=86398&action=edit
Akonadi selftest report

[Andrea Scarpino]

https://bugs.kde.org/show_bug.cgi?id=334205

Andrea Scarpino <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
Ever confirmed|0 |1

--- Comment #4 from Andrea Scarpino <***@kde.org> ---
I wiped everything related to Akonadi, and it can't setup a new installation.

[Hussam Al-Tayeb]

https://bugs.kde.org/show_bug.cgi?id=334205

Hussam Al-Tayeb <***@visp.net.lb> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@visp.net.lb

[Hussam Al-Tayeb]

https://bugs.kde.org/show_bug.cgi?id=334205

--- Comment #5 from Hussam Al-Tayeb <***@visp.net.lb> ---
Confirmed here.
I upgraded to mariadb 10.0.10, logged off my kde session and cleared the
akonadi database (rm -rf ~/.local/share/akonadi).
When i logged onto KDE, akonadi started but then mysqld crashed.
Downgrading back to mariadb 5.5.37 fixed the crash.

[phanisvara das]

https://bugs.kde.org/show_bug.cgi?id=334205

phanisvara das <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #6 from phanisvara das <***@gmail.com> ---
same here, can't get akonadi to run with mariaDB 10.x

here's the error report i got. i don't pretend to really understand what's
going on, but it looks as if mariaDB had a problem with innoDB -- even though
that only happens when trying to run akonadi. apart from that, mariaDB 10.x was
working fine.

the DB itself doesn't appear to be corrupt. downgrading to mariaDB 5.37.x
solved the problem. w/o clearing the DB, akonadi works fine.

[phanisvara das]

https://bugs.kde.org/show_bug.cgi?id=334205

--- Comment #7 from phanisvara das <***@gmail.com> ---
Created attachment 86405
--> https://bugs.kde.org/attachment.cgi?id=86405&action=edit
mariaDB error log after trying to start akonadi

[g***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=334205

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[desaparecido]

https://bugs.kde.org/show_bug.cgi?id=334205

desaparecido <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #8 from desaparecido <***@gmail.com> ---
Hi, same problem here, I can confirm it too. Like others, downgrading mariadb
and cleaning akonadi database of my user all works again. Needed to clean
/var/lib/mysql/ib_logfile* files to clean start mysql after downgrade

[Arthur Țițeică]

https://bugs.kde.org/show_bug.cgi?id=334205

Arthur Țițeică <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[phanisvara das]

https://bugs.kde.org/show_bug.cgi?id=334205

--- Comment #9 from phanisvara das <***@gmail.com> ---
yes, i had to delete those logfiles too, but the DB itself survived up- and
downgrade intact. akonadi works happily with the 5.37.x server, not with 10.x.

on the archlinux bug tracker (link above) somebody suggested re-compiling qt4
and akonadi against mariaDB 10.x instead of 5.x. another user tried recompiling
akonadi only, which didn't help.

[l***@gmail.com]

https://bugs.kde.org/show_bug.cgi?id=334205

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #10 from ***@gmail.com ---
Another report (from me):
https://bugs.archlinux.org/task/40191

I recreated the database (dropped the akonadi database, removed the "db_data"
dir) and tried to import a dump from mysqldump. It still crashes, looks like it
is a mariadb 10.0.10 issue?

[Andrea Scarpino]

https://bugs.kde.org/show_bug.cgi?id=334205

Andrea Scarpino <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |UPSTREAM

--- Comment #11 from Andrea Scarpino <***@kde.org> ---
Seems that rebuilding mariadb with gcc 4.8 fixes this.

[Hussam Al-Tayeb]

https://bugs.kde.org/show_bug.cgi?id=334205

--- Comment #12 from Hussam Al-Tayeb <***@visp.net.lb> ---
(In reply to comment #11)

Post by Andrea Scarpino
Seems that rebuilding mariadb with gcc 4.8 fixes this.

Since compiling Qt4 with gcc 4.9 results in a broken libQtScript.so, this is a
probably a gcc bug?

[Andrea Scarpino]

https://bugs.kde.org/show_bug.cgi?id=334205

--- Comment #13 from Andrea Scarpino <***@kde.org> ---
(In reply to comment #12)

Post by Hussam Al-Tayeb
Since compiling Qt4 with gcc 4.9 results in a broken libQtScript.so, this is
a probably a gcc bug?

Yes, but please don't go OT any further. See
https://bugreports.qt-project.org/browse/QTBUG-38733