LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-30-2017, 02:54 AM   #1
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Rep: Reputation: Disabled
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:

Code:
$ akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QSqlDatabase: QMYSQL driver not loaded
QSqlDatabase: available drivers: QSQLITE QSQLITE3 QMYSQL QMYSQL3
org.kde.pim.akonadiserver: Invalid database object during database server startup
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...
Is there something I can do to update Akonadi's database before starting it?
 
Old 08-30-2017, 05:07 AM   #2
gmgf
Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 960

Rep: Reputation: 306Reputation: 306Reputation: 306Reputation: 306
Probably qt4 and akonadi need rebuild with the new mariadb, i use plasma5 here and qt5, need also rebuild.
 
Old 08-30-2017, 08:13 AM   #3
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 3,834

Rep: Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890Reputation: 1890
looking a little around seems like these are the rebuild candidates
Code:
amarok                                                                                     
calligra                                                                                   
perl                                                                                       
qt                                                                                         
redland                                                                                    
ulogd
I had to modify the ulogd.SlackBuild because sgml2html is not able to process the file anymore (but we still have the *.txt doc)
Code:
--- ./ulogd.SlackBuild.orig     2015-12-06 21:28:26.000000000 +0100
+++ ./ulogd.SlackBuild  2017-08-30 15:06:41.999702802 +0200
@@ -82,7 +82,6 @@
 
 cd doc
   sgml2txt ulogd.sgml
-  sgml2html -s 0 ulogd.sgml
 cd ..
 
 find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | \
@@ -102,7 +101,7 @@
 
 mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION/samples
 cp -a \
-  AUTHORS COPYING* README* TODO doc/ulogd.{txt,html} \
+  AUTHORS COPYING* README* TODO doc/ulogd.txt \
   $PKG/usr/doc/$PKGNAM-$VERSION
 cp -a doc/*.sql doc/*.table $PKG/usr/doc/$PKGNAM-$VERSION/samples
 
Old 08-30-2017, 10:17 AM   #4
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by gmgf View Post
Probably qt4 and akonadi need rebuild with the new mariadb, i use plasma5 here and qt5, need also rebuild.
Oh! Also in AlienBob's plasma5 and qt5 wagon here. Sorry not to mention that!

Last edited by denydias; 08-30-2017 at 10:18 AM. Reason: typo
 
Old 08-30-2017, 11:02 AM   #5
gmgf
Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 960

Rep: Reputation: 306Reputation: 306Reputation: 306Reputation: 306
Quote:
Originally Posted by denydias View Post
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.
 
Old 08-30-2017, 11:32 AM   #6
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 467

Rep: Reputation: 67
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.
 
Old 08-30-2017, 12:20 PM   #7
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Chuck56 View Post
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.
Where did you find these old -current packages?
 
Old 08-30-2017, 12:30 PM   #8
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 467

Rep: Reputation: 67
Quote:
Originally Posted by denydias View Post
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.
 
Old 08-30-2017, 12:43 PM   #9
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Chuck56 View Post
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!
 
Old 08-30-2017, 01:47 PM   #10
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: Disabled
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:

Code:
$ cd ~/.local/share/akonadi/
$ rm -rf *.old socket-* db_data/ib_logfile* db_data/*.err db_data/*.old
$ akonadictl start
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:

Code:
Connecting to deprecated signal org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: 1036
org.kde.pim.akonadiserver:   DB error:  "Table 'pimitemtable' is read only"
org.kde.pim.akonadiserver:   Error text: "Table 'pimitemtable' is read only QMYSQL3: Não foi possível executar a expressão"
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
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.

Last edited by denydias; 08-30-2017 at 01:52 PM.
 
Old 08-30-2017, 01:51 PM   #11
gmgf
Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 960

Rep: Reputation: 306Reputation: 306Reputation: 306Reputation: 306
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
 
Old 08-30-2017, 01:59 PM   #12
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by gmgf View Post
Finally i have rebuild qt5 for nothing, because this mariadb version have a problem with akonadi (plasma5) version:
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.
 
Old 08-30-2017, 02:15 PM   #13
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 467

Rep: Reputation: 67
Quote:
Originally Posted by denydias View Post
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: ...
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.
 
Old 08-30-2017, 03:15 PM   #14
gmgf
Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 960

Rep: Reputation: 306Reputation: 306Reputation: 306Reputation: 306
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
 
Old 08-31-2017, 01:30 AM   #15
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by denydias View Post
At least this will give you a read only environment...
It turns out that a...

Code:
mv ~/.local/share/akonadi ~/.local/share/akonadi.orig
...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:

Code:
akonadictl stop
rm -rf ~/.local/share/akonadi
akonadictl start
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+).

Last edited by denydias; 08-31-2017 at 01:33 AM.
 
  


Reply

Tags
akonadi, current, mysql


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Akonadi in Debian 8 platypo Linux - Software 9 11-13-2016 08:25 PM
[SOLVED] current, akonadi, mariadb, mysql and kmail pchristy Slackware 4 03-17-2016 06:43 AM
Akonadi GlennsPref Mandriva 7 03-04-2011 04:56 AM
Akonadi x42bn6 Linux - Newbie 5 12-11-2009 06:07 AM
Has Anyone Gotten Akonadi to Work? tronayne Slackware 13 10-23-2009 08:02 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration