Akonadi and MariaDB 10.2.8
 

Hi there,

I have just upgraded to slackware64 current changes for Wed, 30 Aug 2017 02:41:28 GMT.

Now akonadi says:

Is there something I can do to update Akonadi's database before starting it?

Probably qt4 and akonadi need rebuild with the new mariadb, i use plasma5 here and qt5, need also rebuild.

looking a little around seems like these are the rebuild candidates
I had to modify the ulogd.SlackBuild because sgml2html is not able to process the file anymore :( (but we still have the *.txt doc)

Oh! Also in AlienBob's plasma5 and qt5 wagon here. Sorry not to mention that!

I'm recompiling qt5-5.9.1, but it takes between 4 and 6 hours here, after, I would post a message on Eric's blog.

Same issue here on stock 64-current, Akonadi server did not start after the 2017-08-30 updates. My temporary solution is to fall back to the previous mariadb-10.0.32 and jemalloc-3.6.0 packages until the dependencies are ironed out. Akonadi starts now as expected. I'll keep an eye out for breakages I may have introduced with falling back on these 2 packages.

Where did you find these old -current packages?

I checked the https://mirrors.slackware.com/mirrorlist/ and found a mirror that had not updated yet with the latest packages. https://dfw.mirror.rackspace.com/slackware/ was still showing the old packages for slackware64-current.

Tks a lot!

After downgrading to mariadb-10.0.32, it's important to follow these steps to also downgrade databases.

So Akonadi could restart after downgrading, follow this step and then:

That should bring your email, calendar and contacts back, although no new entries could be added (even new emails arriving). There will be errors like this in Akonadi's log:

Removing innodb_force_recovery = 1 from ~/.local/share/akonadi/mysql.conf will lead to Akonadi refusing to start again.

At least this will give you a read only environment so you can access your stuff until more robust fixes arise. Time to use your account web UI for a while.

Finally i have rebuild qt5 for nothing, because this mariadb version have a problem with akonadi (plasma5) version:

https://www.mail-archive.com/kde-bug...msg168566.html

Good to know! This holds me to rm -rf ~/.local/share/akonadi, configure and sync the whole thing again to get into the same conclusion as you. Thanks for sharing.

Just for the record, those steps aren't needed for slackware64-current with the stock KDE 4.14.35. The 2 package downgrades allowed akonadi to work without any other modifications.

Refinally ;)

i have applied this unofficial patch to akonadi (plasma5 version) i use akonadi-17.08.0.

--- akonadi-17.04.3/src/server/storage/dbconfigmysql.cpp 2017-08-11 23:29:02.088613966 +0800
+++ akonadi-17.04.3/src/server/storage/dbconfigmysql.cpp 2017-08-11 23:22:18.808432643 +0800
@@ -492,7 +492,7 @@
}
}

- QSqlDatabase::removeDatabase(initCon);
+ //QSqlDatabase::removeDatabase(initCon);
return success;
}

akonadi and kmail seem worked correctly ;)

It turns out that a...

...worked a lot better than I expected! I thought I was being forced to reconfigure all accounts and settings for Kontact Suite (KMail, KOrganizer and KAddressBook and friends ) from scratch. My mistake! Accounts and settings are kept elsewhere, just their content are sync'ed again (email messages, contacts and calendars).

So if you're bitten by this while in KDE5 and are in a hurry for your precious data, first downgrade to mariadb-10.0.32 as shown above, then run:

Give the thing some time to sync the whole thing again. Might take hours depending on your data size and connection speed.

A bonus: my +5 years old Akonadi data directory was 8.6GB in size. After this resync it is now 4GB. 4.6GB of what seems pure overhead was gone.

EDIT:
For now, I advise you to put mysql and jemalloc in /etc/slackpkg/blacklist (or greylist if you use slackpkg+).

Yesterday's updates,

yep, Pat (thanks!) also fixed linuxdoc-tools (most probably through the perl updates) so that sgml2html generates the html docs correctly.

EDIT: ah, I just saw the ulogd.SlackBuild: he moved away the "set -e" instead :)

Yes, but these changes doesn't solve the akonadi problem.:mad:

This, on the latest slackware(64)-current, with a clean installation. And yes, it worked fine with previous MySQL package.

To note this pvio_socket plugin tried to be loaded. The fun is that this one is specific to Windows environment, from what I understand... :D

Yes, I know, but at least things are otherwise a little better than without the recompiles. When I moved things to use mariadb 10.2.x I hadn't fully grasped the extent to which the API has become incompatible... and frankly, I still haven't. I'll be looking into what can be done to get things working again (help appreciated, of course). Otherwise reverting back to the older mariadb branch and related packages is still an option, as is dumping the incompatible KDE4 packages and just moving ahead to plasma if things work better there. I'd rather not step onto that treadmill just yet though. IMHO there's still some life left in KDE4.

My apologies for the blunder in first not noticing the library soname bumps and renames and breaking things that linked to the old names, and then for not realizing that it wasn't going to be as simple as just recompiling against the new ones. We'll get to the bottom of this though.

No problem Pat, thanks for your answer, another solution, it seem the mariadb 10.1 Series do not have this problem ;)

this version is used by many other distro but..... ;)

Just to note that looks like even Plasma 5 has problems and struggle with the MariaDB 10.2.x ...

And looks like those nutty scientists who develop MariaDB have a very personal take on the software versioning.

Because that goddamned 10.2.x looks like a freaking ELEVEN all the way! And I think is better us to take it as it is, for real: MariaDB 11.x ;)

BTW, maybe that pvio_socket plugin issue could be a path to follow for fixing the things, at least on KDE4. :D

PS. Looks like there are others who hit on this pvio_socket issue too: https://forums.gentoo.org/viewtopic-p-8102400.html and https://bugs.gentoo.org/show_bug.cgi?id=626464

PS2. Also a bug report there: https://bugs.kde.org/show_bug.cgi?id=383991 and it is taken as UNCONFIRMED.

I'm with you on that assessment, Darth.

Nice find Darth! The quoted link I left above from your post had a patch for akonadi. Specifics listed in #3 below. I now have a fully updated slackware64-current running a recompiled akonadi package.

#1 - I deleted my Akonadi database directory which (may or may not need this step):
#2 - modified the /usr/share/config/akonadi/mysql-global.conf to remove a deprecated MariaDB command.
#3 - Rebuild the akonadi package in /tmp after applying the change listed below. (Thanks Darth!)
Restarted Akonadi using the System Settings / Personal Information icon in KDE4.

Shazam! Akonadi is working in slackware64-current fully updated to Wed Aug 30 22:34:34 UTC 2017 (plus the recompiled akonadi package)!

Here you go,

:)

People in -current with KDE4 should be happy now!

For the ones with KDE5, let's wait for AlienBOB's annoucement.

I have posted the solution (for akonadi plasma5) on Eric blog yesterday, But he is overworked in this moment...

Yeah, I have read your post there. Thanks for let him now and to provide a patch. Let's give the guy the time he needs.

Right now we have two workarounds:

1. Users who DON'T upgraded MariaDB: pin some packages (see bellow).
2. Users who upgraded MariaDB: downgrade MariaDB, rebuild Akonadi's db and pin some packages.

Until a fix for AlienBOB's KDE5 hit the wild, packages in the black/grey list for the moment are:

Yesterday Eric (aka AlienBOB) released new KDE 5_17.09 packages.

After removing ~/.local/share/akonadi and try to 'akonadictl start', CLI says:

It looks like it came without the patch pointed out by @gmgf to fix the issue.

The ones relying on KDE 5 in -current are still in mud waters with MariaDB 10.2.8. :(

PS: I've already warned Eric about the issue on the release post.

Eric have replied to mine and others comments regarding this issue. The underlying issue is Qt related, not Akonadi itself. There is no solution yet. So we have to wait further.

Good news! Eric has provided a new Akonadi package with the patch proposed by @gmgf! Akonadi is playing nice with MariaDB 10.2. Yay!

Thank you, AlienBOB!