[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 --- Comment #9 from Jos van den Oever --- The issue happened again on two machines. Removing the files `~/.local/share/akonadi/db_data/ib_logfile*` solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #8 from Jos van den Oever --- This bug has happened on a laptop I maintain as well. The file `~/.local/share/akonadi/db_data/mysql.err` reported that InnoDB missed MLOG_CHECKPOINT between another checkpoint and the end. The database would not start because of this. The user had no feedback. All they could see was a message in KMail that akonadi would not start. Removing the files `~/.local/share/akonadi/db_data/ib_logfile*` solved the issue. Perhaps a solution might be to let akonadictl make a backup of the db_data directory and then remove the ib_logfiles and retry starting up. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Silvan Calarco changed: What|Removed |Added CC||silvan.cala...@mambasoft.it -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr --- Comment #7 from Sébastien P. --- I had a similar issue: * upgrade mariadb * later, a crash => impossible to restart akonadi ~/.local/share/akonadi/db_data/mysql.err.old: 2021-03-13 14:51:11 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.17. 2021-03-13 14:51:11 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Removing ib_logfile0 and ib_logfile1 solved that. Maybe akonadi should tell us to look at this file? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Grósz Dániel changed: What|Removed |Added CC||groszdaniel...@gmail.com --- Comment #6 from Grósz Dániel --- I have had a similar issue recently, after several system crashes (hard resets), and possibly a mariadb update. I start KMail. It said it couldn't start the Akonadi service. Clicking the Start button again, it did nothing. 'akonadictl start' did nothing, no output at all. 'akonadictl start --verbose' indicated that it couldn't start the mysql server, similarly to the original description of this bug report. Attempting to start the mysql (mariadb) server manually, with the same arguments that the Akonadi server uses, just said that it was starting the server, then quit with exit code 1. Same if I added the --verbose flag. Still no clue why. Then it occurred to me to check the mysql log. It was this: 2020-11-06 23:28:28 0 [Note] InnoDB: Using Linux native AIO 2020-11-06 23:28:28 0 [Note] InnoDB: Uses event mutexes 2020-11-06 23:28:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-11-06 23:28:28 0 [Note] InnoDB: Number of pools: 1 2020-11-06 23:28:28 0 [Note] InnoDB: Using SSE4.2 crc32 instructions 2020-11-06 23:28:28 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2020-11-06 23:28:28 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2020-11-06 23:28:28 0 [Note] InnoDB: Completed initialization of buffer pool 2020-11-06 23:28:28 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-11-06 23:28:28 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.13. 2020-11-06 23:28:28 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2020-11-06 23:28:28 0 [Note] InnoDB: Starting shutdown... 2020-11-06 23:28:28 0 [ERROR] Plugin 'InnoDB' init function returned error. 2020-11-06 23:28:28 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2020-11-06 23:28:28 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-11-06 23:28:28 0 [ERROR] Unknown/unsupported storage engine: innodb 2020-11-06 23:28:28 0 [ERROR] Aborting After some further googling, I resolved it by removing ~/.local/share/akonadi/db_data/ib_logfile* . Akonadi works fine now. I still have no idea why this was needed, and why it works. Akonadi should handle this scenario in a more user-friendly way. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Boudewijn Rempt changed: What|Removed |Added Summary|"Unknown Error" and akonadi |After crashing, akonadi |doesn't start |cannot start up and cannot ||recover itself --- Comment #5 from Boudewijn Rempt --- Okay, going to .local/share/akonadi/db_data and removing ib_logfile0 and ib_logfile1 got kmail started again. (Tip from http://mytechmembank.blogspot.com/2017/10/recovering-crashed-mysql-instance.html) But that is not a solution, of course. It should never, ever be necessary do something like that just because a mail client has bug that causes a crash. Akonadi should be able to recover itself. -- You are receiving this mail because: You are watching all bug changes.
