#1 Le 14/12/2019, à 16:54
- belhasof
[RESOLU] Kontact - Akonadi n'est pas opérationnel - Erreur MySQL
Bonjour,
Je suis sous kubuntu 18.04.
Kontact ne fonctionne plus, je n'ai accès ni à Kmail, ni à Korganiser, ni àaucun autre service de Kontact.
Quand je lance Kontact, il me dit que:
"l'environnement Akonadi de gestion des informations personnelles n'est pas opérationnel"
je n'ai pas accès aux détails
J'ai lancé akonadictl start, voici le résultat:
:~$ akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
sofiane@sofiane-Aspire-E1-771:~$ 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-akonadi"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/sofiane/.local/share/akonadi/mysql.conf", "--datadir=/home/sofiane/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-sofiane.fHA5wg/mysql.socket", "--pid-file=/tmp/akonadi-sofiane.fHA5wg/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: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...Au fil de mes recherches, j'ai trouvé qu'il y avait une(des) erreur dans MySQL
Dans /home/sofiane/.local/share/akonadi/db_data voici ce que donne le fichier mysql.err :
2019-12-14T14:45:49.471381Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.
2019-12-14T14:45:49.471447Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-12-14T14:45:49.471458Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-12-14T14:45:49.471487Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2019-12-14T14:45:49.471503Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.28-0ubuntu0.18.04.4) starting as process 8056 ...
2019-12-14T14:45:49.475070Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-12-14T14:45:49.475096Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-12-14T14:45:49.475102Z 0 [Note] InnoDB: Uses event mutexes
2019-12-14T14:45:49.475108Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-12-14T14:45:49.475113Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-14T14:45:49.475118Z 0 [Note] InnoDB: Using Linux native AIO
2019-12-14T14:45:49.475344Z 0 [Note] InnoDB: Number of pools: 1
2019-12-14T14:45:49.475429Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-12-14T14:45:49.476665Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-12-14T14:45:49.483811Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-14T14:45:49.485449Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-12-14T14:45:49.497169Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-12-14T14:45:49.498567Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 129402036694
2019-12-14T14:45:49.498593Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 129402036842
2019-12-14T14:45:49.498628Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 129402036694 and the end 129402036842.
2019-12-14T14:45:49.498642Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-12-14T14:45:50.099210Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-12-14T14:45:50.099242Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-12-14T14:45:50.099252Z 0 [ERROR] Failed to initialize builtin plugins.
2019-12-14T14:45:50.099257Z 0 [ERROR] Aborting
2019-12-14T14:45:50.099265Z 0 [Note] Binlog end
2019-12-14T14:45:50.099301Z 0 [Note] Shutting down plugin 'CSV'
2019-12-14T14:45:50.099476Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
Voilà ce que j'ai pu récolter comme données sur mon problème.
Est-ce que quelqu'un sait comment je peux le résoudre?
Merci d'avance
Dernière modification par belhasof (Le 18/12/2019, à 20:55)
Hors ligne
#2 Le 15/12/2019, à 17:15
- belhasof
Re : [RESOLU] Kontact - Akonadi n'est pas opérationnel - Erreur MySQL
Bonjour,
je continue mes recherches:
Apparemment Akonadi fait des siennes. J'ai voulu voir si je pouvais créer un nouveau compte dans Kontact, voici les 6 messages d'erreurs de l'auto-test du serveur akonadi:
1-Le fichier journal d'erreurs « /home/sofiane/.local/share/akonadi/db_data/mysql.err » du serveur MySQL contient des erreurs. (déjà indiqué dans le 1er message)
2-Le processus de contrôle d'Akonadi n'a pas pu être enregistré dans D-Bus ce qui indique qu'il n'a pas été démarré ou a rencontré une erreur fatale au démarrage.
3-Le processus du serveur Akonadi n'a pas pu être enregistré dans D-Bus ce qui indique qu'il n'a pas été démarré ou a rencontré une erreur fatale au démarrage.
4-Aucun agent de ressource n'a été trouvé, Akonadi n'est pas utilisable sans au moins un tel agent. Cela signifie d'habitude qu'aucun agent de ressource n'est installé ou qu'il y a un problème de configuration. Les emplacements suivants ont été parcourus : « /usr/share/akonadi/agents ». La variable d'environnement « XDG_DATA_DIRS » est fixée à « /usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop » ; veuillez vous assurer qu'elle contient bien tous les emplacements où sont installés des agents Akonadi.
5-Le serveur Akonadi a rapporté des erreurs au cours de son précédent démarrage. Le journal se trouve dans « /home/sofiane/.local/share/akonadi/akonadiserver.error.old ».
6-Le processus du contrôleur Akonadi a rapporté des erreurs au cours du précédent démarrage. Le journal se trouve dans « /home/sofiane/.local/share/akonadi/akonadi_control.error.old ».
Je ne sais pas ce qu'est la variable d'environnement "XDG_DATA_DIRS"
Je n'arrive pas à ouvrir les fichiers akonadiserver.error.old et akonadi_control.error.old
J'ai vu une solution dans: https://bugs.launchpad.net/ubuntu/+sour … ug/1633855
sudo mkdir /var/lib/mysql-filesEst-ce que je peux l'appliquer à mon cas?
Je ne suis qu'un utilisateur final de Kubuntu et cela devient complexe pour moi...
Est-ce que quelqu'un a une idée?
Merci
Hors ligne
#3 Le 15/12/2019, à 17:25
- belhasof
Re : [RESOLU] Kontact - Akonadi n'est pas opérationnel - Erreur MySQL
Je viens de trouver comment faire pour copier l'akonadiselftest:
Akonadi Server Self-Test Report
===============================
Test 1: SUCCESS
--------
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.
File content of '/home/sofiane/.config/akonadi/akonadiserverrc':
[Debug]
Tracer=null
[%General]
Driver=QMYSQL
[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/tmp/akonadi-sofiane.c0KmU6/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true
Test 2: SUCCESS
--------
Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.
Test 3: SUCCESS
--------
MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld-akonadi'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.
Test 4: SUCCESS
--------
MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.7.28-0ubuntu0.18.04.4 for Linux on x86_64 ((Ubuntu))
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a href="/home/sofiane/.local/share/akonadi/db_data/mysql.err">/home/sofiane/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/sofiane/.local/share/akonadi/db_data/mysql.err':
2019-12-15T15:21:27.222262Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2019-12-15T15:21:27.222340Z 0 [Warning] Changed limits: max_connections: 214 (requested 256)
2019-12-15T15:21:27.375216Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.
2019-12-15T15:21:27.375260Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-12-15T15:21:27.375269Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-12-15T15:21:27.375296Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2019-12-15T15:21:27.375313Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.28-0ubuntu0.18.04.4) starting as process 7041 ...
2019-12-15T15:21:27.378608Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-12-15T15:21:27.378629Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-12-15T15:21:27.378634Z 0 [Note] InnoDB: Uses event mutexes
2019-12-15T15:21:27.378639Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-12-15T15:21:27.378643Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-15T15:21:27.378648Z 0 [Note] InnoDB: Using Linux native AIO
2019-12-15T15:21:27.378851Z 0 [Note] InnoDB: Number of pools: 1
2019-12-15T15:21:27.378926Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-12-15T15:21:27.380023Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-12-15T15:21:27.386791Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-15T15:21:27.388416Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-12-15T15:21:27.399927Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-12-15T15:21:27.401147Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 129402036694
2019-12-15T15:21:27.401169Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 129402036842
2019-12-15T15:21:27.401203Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 129402036694 and the end 129402036842.
2019-12-15T15:21:27.401215Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-12-15T15:21:28.001802Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-12-15T15:21:28.001831Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-12-15T15:21:28.001838Z 0 [ERROR] Failed to initialize builtin plugins.
2019-12-15T15:21:28.001841Z 0 [ERROR] Aborting
2019-12-15T15:21:28.001846Z 0 [Note] Binlog end
2019-12-15T15:21:28.001875Z 0 [Note] Shutting down plugin 'CSV'
2019-12-15T15:21:28.001991Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
Test 6: SUCCESS
--------
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href="/etc/xdg/akonadi/mysql-global.conf">/etc/xdg/akonadi/mysql-global.conf</a>.
File content of '/etc/xdg/akonadi/mysql-global.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
#
# mesure 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 pool InnoDB uses to store data dictionary information and other internal data structures (default:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
# innodb_additional_mem_pool_size=8M
# 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)
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))
query_cache_size=0
# Do not cache results (default:1)
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
# KUBUNTU:
# Unset the export dir check as only the full mysql-server package creates it
secure_file_priv=
# KUBUNTU:
# workaround for 5.7 being more strict with column types
# (reverts to 5.6 behavior)
sql_mode=NO_ENGINE_SUBSTITUTION
[client]
default-character-set=utf8
Test 7: SKIP
--------
MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.
Test 8: SUCCESS
--------
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href="/home/sofiane/.local/share/akonadi/mysql.conf">/home/sofiane/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/sofiane/.local/share/akonadi/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
#
# mesure 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 pool InnoDB uses to store data dictionary information and other internal data structures (default:8M)
# Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
# innodb_additional_mem_pool_size=8M
# 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)
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))
query_cache_size=0
# Do not cache results (default:1)
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
# KUBUNTU:
# Unset the export dir check as only the full mysql-server package creates it
secure_file_priv=
# KUBUNTU:
# workaround for 5.7 being more strict with column types
# (reverts to 5.6 behavior)
sql_mode=NO_ENGINE_SUBSTITUTION
[client]
default-character-set=utf8
Test 9: SUCCESS
--------
akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
akonadictl 5.7.3
Test 10: ERROR
--------
Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.
Test 11: ERROR
--------
Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.
Test 12: SKIP
--------
Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.
Test 13: ERROR
--------
No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'; make sure this includes all paths where Akonadi agents are installed.
Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadiindexingagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
ewsmtaresource.desktop
ewsresource.desktop
facebookresource.desktop
followupreminder.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kolabresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
newmailnotifieragent.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
tomboynotesresource.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
Test 14: SUCCESS
--------
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 15: ERROR
--------
Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href="/home/sofiane/.local/share/akonadi/akonadiserver.error.old">/home/sofiane/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/sofiane/.local/share/akonadi/akonadiserver.error.old':
database server stopped unexpectedlyDatabase process exited unexpectedly during initial connection!executable: "/usr/sbin/mysqld-akonadi"arguments: ("--defaults-file=/home/sofiane/.local/share/akonadi/mysql.conf", "--datadir=/home/sofiane/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-sofiane.c0KmU6/mysql.socket", "--pid-file=/tmp/akonadi-sofiane.c0KmU6/mysql.pid")stdout: ""stderr: ""exit code: 1process error: "Unknown error"Failed to remove runtime connection config file
Test 16: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 17: ERROR
--------
Previous Akonadi control error log found.
Details: The Akonadi control process reported errors during its previous startup. The log can be found in <a href="/home/sofiane/.local/share/akonadi/akonadi_control.error.old">/home/sofiane/.local/share/akonadi/akonadi_control.error.old</a>.
File content of '/home/sofiane/.local/share/akonadi/akonadi_control.error.old':
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)Application 'akonadiserver' exited normally...Si cela pouvait vous aider à m'aider...
Hors ligne
#4 Le 18/12/2019, à 20:54
- belhasof
Re : [RESOLU] Kontact - Akonadi n'est pas opérationnel - Erreur MySQL
Bon c'est résolu!
Supprimer (ou plutôt renommer pour ne pas perdre les données) les dossier "akonadi" dans /home/XXX/.config/ et dans /home/XXX/.local/share/.
Relancer "akonadi" qui recrée les dossier.
relancer Kontact
Réinstaller les boites mail (pop3/imap et smtp)
Resynchroniser les agendas et contacts (owncloud pour ma part) dans korganiser.
Voilà
Merci à moi
Hors ligne
#5 Le 01/05/2020, à 14:14
- xabilon
Re : [RESOLU] Kontact - Akonadi n'est pas opérationnel - Erreur MySQL
Salut
Même souci depuis aujourd'hui, avec l'erreur de checkpoint innodb qui stoppe mysql, et donc Akonadi ne démarre pas, et par conséquent ni Kmail ni Korganizer...
En revanche j'essaye de trouver une solution pour ne pas avoir à reconfigurer mes comptes mail et agendas, notamment en désactivant le checksum dans mysql...
Edit : il m'a en fait suffit de supprimer les 2 fichiers ib_logfile0 et ib_logfile1 du dossier log ~/.local/share/akonadi/db_data, et Akonadi a pu redémarrer, sans rien perdre.
Dernière modification par xabilon (Le 04/05/2020, à 00:23)
Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.
Hors ligne