You are not logged in.
Kmail gives the following error whenever I try to start it
The Akonadi personal information management service is not running. This application cannot be used without it
After getting the error i tried to start Akonadi manually from the terminal, I got the following result.
[mukund@ArchLinux ~]$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[mukund@ArchLinux ~]$ org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/mukund/.local/share/akonadi/mysql.conf", "--datadir=/home/mukund/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-09 14:46:20 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 6844 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
After seeing the above error I took a look at the mysql.err file located in ~/.local/share/akonadi/db_data/mysql.err which gave me the below output
2022-06-09 14:46:20 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2022-06-09 14:46:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-06-09 14:46:20 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-09 14:46:20 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-09 14:46:20 0 [Note] InnoDB: Using Linux native AIO
2022-06-09 14:46:20 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-06-09 14:46:20 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-09 14:46:20 0 [ERROR] InnoDB: File ./ib_logfile0 was not found
2022-06-09 14:46:20 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-06-09 14:46:20 0 [Note] InnoDB: Starting shutdown...
2022-06-09 14:46:21 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-06-09 14:46:21 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-06-09 14:46:21 0 [ERROR] Unknown/unsupported storage engine: innodb
2022-06-09 14:46:21 0 [ERROR] Aborting
Then I noticed the line " [ERROR] InnoDB: File ./ib_logfile0 was not found", so i created the file under the directory "~/local/share/akonadi/db_data/ib_logfile0".
After creating the file I tried to start Akonadi. which resulted in the following
2022-06-09 15:03:33 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2022-06-09 15:03:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-06-09 15:03:33 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-09 15:03:33 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-09 15:03:33 0 [Note] InnoDB: Using Linux native AIO
2022-06-09 15:03:33 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-06-09 15:03:33 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-09 15:03:33 0 [ERROR] InnoDB: ib_logfile0 is empty, and LSN is unknown.
2022-06-09 15:03:33 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2022-06-09 15:03:33 0 [Note] InnoDB: Starting shutdown...
2022-06-09 15:03:33 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-06-09 15:03:33 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-06-09 15:03:33 0 [ERROR] Unknown/unsupported storage engine: innodb
2022-06-09 15:03:33 0 [ERROR] Aborting
After encountering the below output, I deleted the directory with the command "rm -r ~/.local/share/akonadi/"
2022-06-09 15:03:33 0 [ERROR] InnoDB: ib_logfile0 is empty, and LSN is unknown.
After doing all of that I'm now back to square 1, so i uninstalled then reinstalled kmail which didn't work either.
I don't know what I'm doing wrong but nothing seems to work.
Offline
Yes after last update akonadi is not starting:
[audiolinux@archlinux ~]$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[audiolinux@archlinux ~]$ org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/audiolinux/.local/share/akonadi/mysql.conf", "--datadir=/home/audiolinux/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-09 15:10:59 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 8451 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
Offline
Offline
I was also affected by the Akonadi bug described in the first post after a pacman -Syu today. Downgrading the mariadb packages as mentioned in the aforesaid post did the trick for me. Akonadi now works again.
mariadb (10.8.3-1 => 10.7.4-1)
mariadb-clients (10.8.3-1 => 10.7.4-1)
mariadb-libs (10.8.3-1 => 10.7.4-1)
-Vinu.
Offline
Experienced the same, but for me simple `touch ib_logfile0` solved the problem w/o downgrading `mariadb`. Probably, I'm just lucky ☺.
uname == latest pf-kernel
Offline
Yes that did it!
ben-arch wrote:I was also affected by the Akonadi bug described in the first post after a pacman -Syu today. Downgrading the mariadb packages as mentioned in the aforesaid post did the trick for me. Akonadi now works again.
mariadb (10.8.3-1 => 10.7.4-1)
mariadb-clients (10.8.3-1 => 10.7.4-1)
mariadb-libs (10.8.3-1 => 10.7.4-1)-Vinu.
Offline
same here after last update Akonadi and kmail emai client stop working
[~]$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[~]$ org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/slaw/.local/share/akonadi/mysql.conf", "--datadir=/home/slaw/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-09 22:42:49 0 [Note] /usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 16653 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
Last edited by infoslaw (2022-06-09 20:49:45)
Offline
All, if you expect some help on this, post your `~/.local/share/akonadi/db_data/mysql.err`. It might be the case the DB needs upgrade, and to find out also post the output of this:
$ mariadb-upgrade --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/run/user/$(id -u)/akonadi/mysql.socket --check-if-upgrade-is-needed
uname == latest pf-kernel
Offline
Here is output:
mariadb-upgrade --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/run/user/$(id -u)/akonadi/mysql.socket --check-if-upgrade-is-needed
Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (2)
FATAL ERROR: Upgrade failed
Offline
Here is output:
mariadb-upgrade --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/run/user/$(id -u)/akonadi/mysql.socket --check-if-upgrade-is-needed Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (2) FATAL ERROR: Upgrade failed
But what's in `~/.local/share/akonadi/db_data/mysql.err` ?
uname == latest pf-kernel
Offline
I'm sorry below data from mysql.err
2022-06-10 8:49:00 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2022-06-10 8:49:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-06-10 8:49:00 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-10 8:49:00 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-10 8:49:00 0 [Note] InnoDB: Using Linux native AIO
2022-06-10 8:49:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-06-10 8:49:00 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-10 8:49:00 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2022-06-10 8:49:00 0 [ERROR] InnoDB: invalid undo header offset 0
2022-06-10 8:49:00 0 [Note] InnoDB: Retry with innodb_force_recovery=5
2022-06-10 8:49:00 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2022-06-10 8:49:00 0 [Note] InnoDB: Starting shutdown...
2022-06-10 8:49:00 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-06-10 8:49:00 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-06-10 8:49:00 0 [ERROR] Unknown/unsupported storage engine: innodb
2022-06-10 8:49:00 0 [ERROR] Aborting
Offline
I'm sorry below data from mysql.err
2022-06-10 8:49:00 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152 2022-06-10 8:49:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.12 2022-06-10 8:49:00 0 [Note] InnoDB: Number of transaction pools: 1 2022-06-10 8:49:00 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-06-10 8:49:00 0 [Note] InnoDB: Using Linux native AIO 2022-06-10 8:49:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2022-06-10 8:49:00 0 [Note] InnoDB: Completed initialization of buffer pool 2022-06-10 8:49:00 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2022-06-10 8:49:00 0 [ERROR] InnoDB: invalid undo header offset 0 2022-06-10 8:49:00 0 [Note] InnoDB: Retry with innodb_force_recovery=5 2022-06-10 8:49:00 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption 2022-06-10 8:49:00 0 [Note] InnoDB: Starting shutdown... 2022-06-10 8:49:00 0 [ERROR] Plugin 'InnoDB' init function returned error. 2022-06-10 8:49:00 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2022-06-10 8:49:00 0 [ERROR] Unknown/unsupported storage engine: innodb 2022-06-10 8:49:00 0 [ERROR] Aborting
So, as suggested:
2022-06-10 8:49:00 0 [Note] InnoDB: Retry with innodb_force_recovery=5
add this:
innodb_force_recovery=5
to `~/.local/share/akonadi/mysql.conf` file under the `[mysqld]` section and then start akonadi again. If it fails, show what's in `mysql.err` again.
uname == latest pf-kernel
Offline
Experienced the same, but for me simple `touch ib_logfile0` solved the problem w/o downgrading `mariadb`. Probably, I'm just lucky ☺.
This worked for me.
Offline
Akonadi starting but after while crashing
I think that got my problem after restoring all below folders with files from local backup
~/.local/share/
akonadi
akonadi_davgroupware_resource_0
akonadi_google_resource_2
akonadi_googlecontacts_resource_0
akonadi_googlecontacts_resource_1
akonadi_googlecontacts_resource_2
akonadi_googlecontacts_resource_3
akonadi_googlecontacts_resource_5
akonadi_googlecontacts_resource_6
akonadi_maildir_resource_0
akonadi_migration_agent
and
~/.config/akonadi
here part from mysql.err
2022-06-10 11:25:19 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2022-06-10 11:25:19 0 [Note] InnoDB: !!! innodb_force_recovery is set to 5 !!!
2022-06-10 11:25:19 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-06-10 11:25:19 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-10 11:25:19 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-10 11:25:19 0 [Note] InnoDB: Using Linux native AIO
2022-06-10 11:25:19 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-06-10 11:25:19 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-10 11:25:19 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 9475691045 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=0] log sequence number 9508560475 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-06-10 11:25:19 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2022-06-10 11:25:19 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2022-06-10 11:25:19 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2022-06-10 11:25:19 0 [Note] InnoDB: log sequence number 9385967090; transaction id 0
2022-06-10 11:25:19 0 [Note] InnoDB: Loading buffer pool(s) from /home/slaw/.local/share/akonadi/db_data/ib_buffer_pool
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 9511849765 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 9511864852 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=45] log sequence number 9511853827 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=48] log sequence number 9511865078 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=46] log sequence number 9511861846 is in the future! Current system log sequence number 9385967090.
2022-06-10 11:25:19 0 [ERROR] InnoDB: Page [page id: space=0, page number=50] log sequence number 9511869480 is in the future! Current system log sequence number 9385967090.
Is it good idea to delete all above folders to let create Akonadi empty database with default files and after import KMail all emails from backup?
Last edited by infoslaw (2022-06-10 09:57:36)
Offline
I'd rather dump databases while in the recovery mode, and then recreate them using the dump. Refer to https://mariadb.com/kb/en/innodb-recovery-modes/
uname == latest pf-kernel
Offline
Then I noticed the line " [ERROR] InnoDB: File ./ib_logfile0 was not found", so i created the file under the directory "~/local/share/akonadi/db_data/ib_logfile0".
hi all, thanks for the tip, in my case all works fine again with adding that file :-)
KF5 & Plasma5 (git versions) - Awesome WM
ASUS Sabertooth 990FX - AMD FX8350 - ATI Radeon HD 7970
[testing] repo
Offline
I was also successful with creating ib_logfile0 as per:
touch ~/.local/share/akonadi/db_data/ib_logfile0
Offline
I was also successful with creating ib_logfile0 as per:
touch ~/.local/share/akonadi/db_data/ib_logfile0
This worked for me. Thank you.
Offline
hi guys,
i need your help. i have added innodb_force_recovery = 5 and also created touch ~/.local/share/akonadi/db_data/ib_logfile0.
unfortunately i get the following error:
2022-06-12 9:45:29 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2022-06-12 9:45:29 0 [Note] InnoDB: !!! innodb_force_recovery is set to 5 !!!
2022-06-12 9:45:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-06-12 9:45:29 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-12 9:45:29 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-12 9:45:29 0 [Note] InnoDB: Using Linux native AIO
2022-06-12 9:45:29 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-06-12 9:45:29 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-12 9:45:29 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2022-06-12 9:45:29 0 [ERROR] InnoDB: ib_logfile0 is empty, and LSN is unknown.
2022-06-12 9:45:29 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2022-06-12 9:45:29 0 [Note] InnoDB: Starting shutdown...
2022-06-12 9:45:29 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-06-12 9:45:29 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-06-12 9:45:29 0 [ERROR] Unknown/unsupported storage engine: innodb
2022-06-12 9:45:29 0 [ERROR] Aborting
Last edited by St.Boom (2022-06-12 07:46:38)
Offline
Same here.
Doesn't matter what I tried, touch and/or innodb_force_recovery. It's the same or similar error. Downgrade to v10.7.4 was the only solution for me. I have that problem on multi devices. Also on a fresh Arch setup.
Edit:
For whatever reason that way the database of aknoadi gets updated as well to v.10.8.3
downgrade mariadb-10.7.4-1 mariadb-clients-10.7.4-1 mariadb-libs-10.7.4-1
rm -rf ~/.local/share/akonadi/
akonadictl start
akonadictl stop
pacman -S mariadb mariadb-clients mariadb-libs
akonadictl start
This works for all my devices. Some reboots may be required if you have some D-BUS connection errors.
Last edited by danSman (2022-06-14 20:48:51)
Offline