[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself

[Grósz Dániel]

https://bugs.kde.org/show_bug.cgi?id=425131

Grósz Dániel <groszdanielpub at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |groszdanielpub at gmail.com

--- Comment #6 from Grósz Dániel <groszdanielpub at gmail.com> ---
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 the assignee for the bug.