FS#40191 - [mariadb-clients] After upgrading mysql, akonadi crashes the server

Attached to Project: Arch Linux
Opened by Peter Wu (Lekensteyn) - Friday, 02 May 2014, 14:46 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 14 May 2014, 09:34 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrea Scarpino (BaSh)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After upgrading some packages today, KMail broke because the mysql daemon somehow died. Upon further inspection, mysqld has segfaulted. (See mysql.err)

Manually starting mysqld, then run `mysqlcheck --optimize` against it also crashed the server.

Assuming that some file got corrupted, I used mysqldump to dump the database, dropped the database, created an empty database and tried to import it. That failed too with a similar backtrace (see mysql-manual-create.err.txt)

Additional info:
* mariadb-clients 10.0.10-1

Steps to reproduce:

1. Start mysqld with akonadi's database
/usr/bin/mysqld \
--defaults-file=$HOME/.local/share/akonadi/mysql.conf \
--datadir=$HOME/.local/share/akonadi/db_data/ \
--socket=/tmp/akonadi-.../mysql.socket
2. mysqlcheck \
--defaults-file=$HOME/.local/share/akonadi/mysql.conf \
--socket=/tmp/akonadi-.../mysql.socket \
--repair akonadi
3. DB crashes.

(alternatively: start KMail and observe that mysqld crashes)
   mysql.err.txt (3.3 KiB)
   mysql-manual-create.err.txt (4.6 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 14 May 2014, 09:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  mariadb 10.0.11-2
Comment by Peter Wu (Lekensteyn) - Friday, 02 May 2014, 14:50 GMT
Anothers have confirmed issues with MariaDB 10.0.10 and akonadi too:
https://bugs.kde.org/show_bug.cgi?id=334205

Please hold it back in testing.
Comment by Bartłomiej Piotrowski (Barthalion) - Friday, 02 May 2014, 15:26 GMT
We are aware of the problem. Additionally before I move the new MariaDB out of [testing], we'll need an announcement too, so don't worry about it.

The problem has been reported on KDE's and MariaDB's bugtrackers too.
Comment by phanisvara das (phani00) - Wednesday, 14 May 2014, 08:02 GMT
  • Field changed: Percent Complete (100% → 0%)
same thing happens with mariadb 10.0.11-1
Comment by Evangelos Foutras (foutrelis) - Wednesday, 14 May 2014, 08:59 GMT
Could you please confirm that mariadb 10.0.11-2 is working as expected?
Comment by Peter Wu (Lekensteyn) - Wednesday, 14 May 2014, 09:06 GMT
Yes, this got fixed with rebuild in 10.0.10-2.
Comment by phanisvara das (phani00) - Wednesday, 14 May 2014, 09:09 GMT
don't know if the previous comment is a typo and meant to say, "10.0.11-2." the new version, ~.11-2 hasn't made it into my mirror yet. will let you know when it does.
Comment by Luis Davila (desaparecido) - Wednesday, 14 May 2014, 09:30 GMT
yes it's fixed in last mariadb 10.0.11-2 version..
Comment by Peter Wu (Lekensteyn) - Wednesday, 14 May 2014, 09:32 GMT
@phani00 it's in the testing repo.

Loading...