Bug 443459 - The Akonadi personal information management service is not running. This application cannot be used without it.
Summary: The Akonadi personal information management service is not running. This appl...
Status: REOPENED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.22.3
Platform: Debian stable Other
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-08 03:13 UTC by (Daniel James Ray Hunt)
Modified: 2023-11-28 10:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
What I saw when trying to open KAddressBook for first time (52.04 KB, image/png)
2023-10-23 02:27 UTC, Mike Lieberman
Details
attachment-420319-0.html (6.96 KB, text/html)
2023-11-28 10:36 UTC, Mike Lieberman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description (Daniel James Ray Hunt) 2021-10-08 03:13:47 UTC
The Akonadi personal information management service is not running. This application cannot be used without it.
Comment 1 Mike Lieberman 2023-10-23 02:24:41 UTC
In Debian 12 Stable

mike@blackbox:~$ 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/sbin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/mike/.local/share/akonadi/mysql.conf", "--datadir=/home/mike/.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: ""
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...
Comment 2 Mike Lieberman 2023-10-23 02:27:43 UTC
Created attachment 162510 [details]
What I saw when trying to open KAddressBook for first time

mike@blackbox:~$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:    done.
mike@blackbox:~$ 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/sbin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/mike/.local/share/akonadi/mysql.conf", "--datadir=/home/mike/.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: ""
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...
Comment 3 Christophe Marin 2023-10-25 07:51:42 UTC
Please check the content of the mysql error file in ~/.local/share/akonadi
Comment 4 Mike Lieberman 2023-10-25 08:02:50 UTC
You asked for the contents:
mike@blackbox:~/.local/share/akonadi$ ls
Akonadi.error      db_data  file_db_data  search_db
Akonadi.error.old  db_misc  mysql.conf    socket-blackbox-default
mike@blackbox:~/.local/share/akonadi$ cat  ~/.local/share/akonadi


mike@blackbox:~/.local/share/akonadi$ cat Akonadi.error
2023-10-25T08:25:00 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi Server...
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadis2023-10-25T08:25:05 [INFO ] org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
rocess exited unexpectedly during initial connection!
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/mike/.local/share/akonadi/mysql.conf", "--datadir=/home/mike/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadiserver: stdout: ""
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadiserver: stderr: ""
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadiserver: exit code: 1
2023-10-25T08:25:05 [CRITICAL] org.kde.pim.akonadiserver: process error: "Unknown error"
2023-10-25T08:25:05 [INFO ] org.kde.pim.akonadiserver: Shutting down AkonadiServer...

mike@blackbox:~/.local/share/akonadi$ cat Akonadi.error.old
2023-10-25T08:25:00 [WARN ] default: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
mike@blackbox:~/.local/share/akonadi$ 

What else do you need?
Comment 5 Mike Lieberman 2023-10-25 08:04:28 UTC
from the conf file:
mike@blackbox:~/.local/share/akonadi$ cat mysql.conf
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# measure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=128M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
loose_log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
loose_query_cache_size=0

# Do not cache results (default:1)
loose_query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

# Debian/KUBUNTU:
# Unset the export dir check as only the full mysql-server package creates it
secure_file_priv=

[client]
default-character-set=utf8
Comment 6 Carl Schwan 2023-10-27 11:26:55 UTC
The actual interesting file is: ~/.local/share/akonadi/db_data/mysql.err

The file might be quite big, but only the ~50 last lines are interesting

tail -n 50 ~/.local/share/akonadi/db_data/mysql.err
Comment 7 Mike Lieberman 2023-10-27 11:47:57 UTC
I have no idea why is says upgrade. 

root@blackbox:/home/mike/.local/share/akonadi/db_data# ls -l mysql.err
-rw-rw---- 1 mike mike 1477 Oct 27 08:45 mysql.err
root@blackbox:/home/mike/.local/share/akonadi/db_data# cat mysql.err
2023-10-27  8:45:37 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision  as process 3734
2023-10-27  8:45:37 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2023-10-27  8:45:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-10-27  8:45:37 0 [Note] InnoDB: Using transactional memory
2023-10-27  8:45:37 0 [Note] InnoDB: Number of transaction pools: 1
2023-10-27  8:45:37 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-10-27  8:45:37 0 [Note] InnoDB: Using liburing
2023-10-27  8:45:37 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-10-27  8:45:37 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-27  8:45:37 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2023-10-27  8:45:37 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.15. You must start up and shut down MariaDB 10.7 or earlier.
2023-10-27  8:45:37 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2023-10-27  8:45:37 0 [Note] InnoDB: Starting shutdown...
2023-10-27  8:45:37 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-10-27  8:45:37 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-10-27  8:45:37 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-27  8:45:37 0 [ERROR] Unknown/unsupported storage engine: innodb
2023-10-27  8:45:37 0 [ERROR] Aborting
root@blackbox:/home/mike/.local/share/akonadi/db_data#
Comment 8 Bug Janitor Service 2023-11-11 03:45:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-11-26 03:45:41 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 10 Christophe Marin 2023-11-28 10:23:50 UTC
feedback provided in comment#7
Comment 11 Mike Lieberman 2023-11-28 10:36:28 UTC
Created attachment 163562 [details]
attachment-420319-0.html

still not running.


On Tue, 2023-11-28 at 10:23 +0000, Christophe Marin wrote:
> https://bugs.kde.org/show_bug.cgi?id=443459
> 
> Christophe Marin <christophe@krop.fr> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------
> -------
>          Resolution|WORKSFORME                  |---
>              Status|RESOLVED                    |REOPENED
>      Ever confirmed|0                           |1
> 
> --- Comment #10 from Christophe Marin <christophe@krop.fr> ---
> feedback provided in comment#7
>