Kmail/Kontact en panne suite mise à jour mariadb... [Réglé]
gerard-ll Membre non connecté
-
- Voir le profil du membre gerard-ll
- Inscrit le : 09/12/2011
- Groupes :
Sur ma Mageia 10 une mise à jour vient d'être effectuée ce matin et j'ai vu que mariadb faisait partie de la mise à jour.
Du coup kmail/kontact est en panne
![:]](/images/smileys/8.gif)
Si je démarre kontact en konsole j'ai ça (un peu long) :
Caché :
Code TEXT :
[gerard@localhost ~]$ kontact
^C
[gerard@localhost ~]$ ^C
[gerard@localhost ~]$
::1 localhost localhost4 localhost4.localdomain4 localhost6 localhost6.localdomain6 localhost.localdomain
[gerard@localhost ~]$ s
Display all 244 possibilities? (y or n)
[gerard@localhost ~]$ kma
kmahjongg kmail kmail_antivir.sh kmail_clamav.sh kmail_fprot.sh kmail-refresh-settings kmail_sav.sh
[gerard@localhost ~]$ kmai
kmail kmail_antivir.sh kmail_clamav.sh kmail_fprot.sh kmail-refresh-settings kmail_sav.sh
[gerard@localhost ~]$ kmail
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.akonadi_control'")
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
/usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
akonadi.tagtypetable OK
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: "2013"
org.kde.pim.akonadiserver: DB error: "Lost connection to server during query"
org.kde.pim.akonadiserver: Error text: "Lost connection to server during query QMYSQL: Impossible d'exécuter la requête"
org.kde.pim.akonadiserver: Values: QList(QVariant(QString, "akonadi"), QVariant(QString, "SchemaVersionTable"))
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
qt.sql.mysql: QMYSQLResult::cleanup: unable to free statement handle
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL: Impossible de préparer l'instruction"
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL: Impossible de préparer l'instruction"
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
terminate called after throwing an instance of 'Akonadi::Server::DbException'
what(): Failed to query index
Sql error: Server has gone away QMYSQL: Impossible d'exécuter la requête
Query: SHOW INDEXES FROM CollectionTable WHERE `Key_name` = 'CollectionTable_parentAndNameIndex'
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadiserver" stopped unexpectedly ( "Le processus a planté" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed! 1 restarts left.
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
/usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
akonadi.tagtypetable OK
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: "2013"
org.kde.pim.akonadiserver: DB error: "Lost connection to server during query"
org.kde.pim.akonadiserver: Error text: "Lost connection to server during query QMYSQL: Impossible d'exécuter la requête"
org.kde.pim.akonadiserver: Values: QList(QVariant(QString, "akonadi"), QVariant(QString, "SchemaVersionTable"))
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
qt.sql.mysql: QMYSQLResult::cleanup: unable to free statement handle
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL: Impossible de préparer l'instruction"
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL: Impossible de préparer l'instruction"
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
terminate called after throwing an instance of 'Akonadi::Server::DbException'
what(): Failed to query index
Sql error: Server has gone away QMYSQL: Impossible d'exécuter la requête
Query: SHOW INDEXES FROM CollectionTable WHERE `Key_name` = 'CollectionTable_parentAndNameIndex'
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadiserver" stopped unexpectedly ( "Le processus a planté" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed! 0 restarts left.
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
/usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
akonadi.tagtypetable OK
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: "2013"
org.kde.pim.akonadiserver: DB error: "Lost connection to server during query"
org.kde.pim.akonadiserver: Error text: "Lost connection to server during query QMYSQL: Impossible d'exécuter la requête"
org.kde.pim.akonadiserver: Values: QList(QVariant(QString, "akonadi"), QVariant(QString, "SchemaVersionTable"))
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
qt.sql.mysql: QMYSQLResult::cleanup: unable to free statement handle
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL: Impossible de préparer l'instruction"
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL: Impossible de préparer l'instruction"
org.kde.pim.akonadiserver: Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )"
terminate called after throwing an instance of 'Akonadi::Server::DbException'
what(): Failed to query index
Sql error: Server has gone away QMYSQL: Impossible d'exécuter la requête
Query: SHOW INDEXES FROM CollectionTable WHERE `Key_name` = 'CollectionTable_parentAndNameIndex'
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadiserver" stopped unexpectedly ( "Le processus a planté" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed too often. Giving up!
org.kde.pim.pimcommonactivities: Plasma activities is not running: 1
GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QIODevice, Unknown): invalid nullptr parameter
org.kde.pim.akonadicore: Job error: "" for collection: QList()
org.kde.pim.akonadicore: Job error: "" for collection: QList()
org.kde.pim.messagelist: Failed to load tags ""
org.kde.pim.kmail: ""
org.kde.pim.mailcommon: failed to retrieve tags ""
Est-ce qu'il y a une solution?
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
gerard-ll Membre non connecté
-
- Voir le profil du membre gerard-ll
- Inscrit le : 09/12/2011
- Groupes :
Jybz :Ce n'est pas k* qu'il faut redémarrer, ce sont des clients. Il faut redémarrer akonadictl (de souvenir)
Ah merci Jybz, je vais essayer
gerard-ll Membre non connecté
-
- Voir le profil du membre gerard-ll
- Inscrit le : 09/12/2011
- Groupes :
Je vais attendre la mise à jour d'Akanodi .
C'est ce qui s'est passé dans cette discussion.
david.david Membre non connecté
-
- Voir le profil du membre david.david
- Inscrit le : 11/02/2008
- Groupes :
-
Membre d'Honneur
As tu redémarré ton système ?
Moi je n'ai pas d’erreur sur ma mga10! tout semble bien fonctionner.
Édité par david.david Le 15/05/2026 à 08h38
ASUS K73S (portable) :
Intel Core i3-2350M_2.3GHz, 8 GO RAM DDR3, écran LED 17" (1600x900), CG Intel HD intégrée + CG Nvidia GeForce 610M_1GB dédiée (Technologie Optimus), SSD Samsung 860 EVO 500GB + SSD Samsung 850 EVO 500GB.
Mageia 8 - x86_64bits/ KDE Plasma-5.20.4 (DVD édition), c' est de la bombe, vive MAGEIA et toute l'équipe du STAFF MLO.
de david.david <david.david@mageialinux-online.org>
.Venez nous rejoindre sur le salon IRC de MLO
Intel Core i3-2350M_2.3GHz, 8 GO RAM DDR3, écran LED 17" (1600x900), CG Intel HD intégrée + CG Nvidia GeForce 610M_1GB dédiée (Technologie Optimus), SSD Samsung 860 EVO 500GB + SSD Samsung 850 EVO 500GB.
Mageia 8 - x86_64bits/ KDE Plasma-5.20.4 (DVD édition), c' est de la bombe, vive MAGEIA et toute l'équipe du STAFF MLO.
de david.david <david.david@mageialinux-online.org>
.Venez nous rejoindre sur le salon IRC de MLO
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
Il semblerait que le serveur akonadi tente d'envoyer une requête au serveur mariadb, mais que celui-ci ne se soit pas lancé, ou a planté.
Est-ce que coredumpctl signalerait un tel plantage ?
Tu peux tenter à tout hasard
Code BASH :
akonadictl fsck
gerard-ll Membre non connecté
-
- Voir le profil du membre gerard-ll
- Inscrit le : 09/12/2011
- Groupes :
Merci à tous pour vos réponses!
akonadictl fsck en mode user donne ça :
Code TEXT :
[gerard@localhost ~]$ akonadictl fsck Akonadi Server is not running, check will not run
Et en mode root donne ça :
Code TEXT :
[root@localhost gerard]# akonadictl fsck D-Bus session bus is not available! Abandon (core dumped)akonadictl fsck
Ce matin toujours le même souci
Et oui mon système a redémarré
gerard-ll Membre non connecté
-
- Voir le profil du membre gerard-ll
- Inscrit le : 09/12/2011
- Groupes :
gerard-ll Membre non connecté
-
- Voir le profil du membre gerard-ll
- Inscrit le : 09/12/2011
- Groupes :
La mise à jour a réglé le souci
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie