I do remember meddling with DB stuff. The details button doesn't give any details in UI error message. Perhaps using snaps by ubuntu may have helped as they package everything together for distribution and repository agnostic.

jk@linux-oobn:~> pkill akonadi_control
jk@linux-oobn:~> pkill akonadiserver
jk@linux-oobn:~> mysqladmin shutdown --socket ~/.local/share/akonadi/socket-$(hostname)/mysql.socket
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/home/jk/.local/share/akonadi/socket-linux-oobn/mysql.socket' (111)'
Check that mysqld is running and that the socket: '/home/jk/.local/share/akonadi/socket-linux-oobn/mysql.socket' exists!
jk@linux-oobn:~> akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
jk@linux-oobn:~> org.kde.pim.akonadiserver: Failed to connect to database!
org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-jk.fcFdP8/mysql.socket' (111 \"Connection refused\") QMYSQL: Unable to connect"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...

Let me confirm: are you using Snap packages to run the PIM stack?

I'm not. I'm complaining that it may have not be screwed like that in a snap package.

What distro and Applications version are you using? Recent version recover gracefully from database errors, older ones won't.
A workaround is to start mysqld manually with the same parameters as akonadictl start.

Opensuse tumbleweed, and 17.04. From error logs I start aconadi without any parameters.

Code: Select all

error: 'Can't connect to local MySQL server through socket '/home/jk/.local/share/akonadi/socket-linux-oobn/mysql.socket' (111)'
Check that mysqld is running and that the socket: '/home/jk/.local/share/akonadi/socket-linux-oobn/mysql.socket' exists!
[...]
org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-jk.fcFdP8/mysql.socket' (111


Unrelated, but you're attempting to use two different mariadb/mysql instances.

Try running

Code: Select all

mysqld_safe --defaults-file=$HOME/.local/share/akonadi/mysql.conf --datadir=$HOME/.local/share/akonadi/db_data --socket /tmp/akonadi-jk.fcFdP8/mysql.socket

Then issue akonadictl start in another terminal.

jk@linux-oobn:~> mysqld_safe --defaults-file=$HOME/.local/share/akonadi/mysql.conf --datadir=$HOME/.local/share/akonadi/db_data --socket /tmp/akonadi-jk.fcFdP8/mysql.socket
sed: -e expression #1, char 9: unknown option to `s'
170522 01:01:53 mysqld_safe Logging to '/home/jk/.local/share/akonadi/db_data/mysql.err'.
170522 01:01:53 mysqld_safe Directory '/var/run/mysql' for UNIX socket file don't exists.

Tried deleting mariadb and reinstalling mysql drivers.

sed: -e expression #1, char 9: unknown option to `s'

This looks suspicious to me...

there isn't even sed in there?

Can you try creating /var/run/mysql and see if it still doesn't run?

sudo mkdir var/run/mysql: didn't work

Was I suppose to try reinstalling akonadi which in opensuse will basically prompt you to get the dependencies right?

You may want to, indeed. I run openSUSE myself, but I've never seen the issue you described.

Somehow clearing var/tmp folder using some weird command helped, or I may have resolved dependencies before and deleting settings in tmp brought akonadi back alife spamming for gmail credentials and reminder daemon on.