Probleme mit Akonadi

[linuxfreund]

Hallo allerseits,
gestern funktionierte KMail noch leidlich gut, heute geht nichts mehr.
Die Ursache ist augenscheinlich das Update von MariaDB gestern.
Denn heute produziert Akonadi solche Fehlermeldungen:

Code: Alles auswählen

org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T10:52:36Z' for column `akonadi`.`pimitemtable`.`datetime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T10:52:36Z' for column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(int, 0))(":1", QVariant(QString, "https://www.xing.com/events/heisser-stuhl-tobias-schumacher-vorstand-wjd-791106"))(":2", QVariant(QString, ""))(":3", QVariant(QString, ""))(":4", QVariant(qlonglong, 280))(":5", QVariant(qlonglong, 9))(":6", QVariant(QDateTime, QDateTime(2023-02-16 10:52:36.798 UTC Qt::UTC)))(":7", QVariant(QDateTime, QDateTime(2023-02-16 10:52:36.798 UTC Qt::UTC)))(":8", QVariant(bool, false))(":9", QVariant(qlonglong, 0)))
org.kde.pim.akonadiserver:   Query: "INSERT INTO PimItemTable (rev, remoteId, remoteRevision, gid, collectionId, mimeTypeId, datetime, atime, dirty, size) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
org.kde.pim.akonadiserver: Error during insertion into table "PimItemTable" "Incorrect datetime value: '2023-02-16T10:52:36Z' for column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver: Error while handling command CreateItem on connection akonadi_kalarm_dir_resource_0 (0x232ad70)
org.kde.pim.akonadicore: ""
org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Failed to append item"
org.kde.pim.akonadicore: Error during ItemSync:  "Failed to append item"

Wer kann ähnliches berichten?
Wie muss ich vorgehen, wenn ich die offensichtlich defekte Version von MariaDB mit der Vorgängerversion ersetzen will?

[sturmvogel]

Welche Mageia Version? Welche MariaDB Version?
Dein Output sieht aus, als ob du einen inkompatiblen Termin/Kontakt versuchst zu importieren…

Da du die Mageia Version nicht angegeben hast…
MGA8 sollte einfach sein: downgrade der Pakete, da alle alten Paketversionen auf den Mirrors liegen
MGA9 nicht möglich: es gibt nur die aktuelle Paketversion auf den Mirrors

Google: „org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value:“

[linuxfreund]

Versionsangaben:
mariadb-core-10.5.19-1.mga8
5.15.88-desktop-1.mga8

[linuxfreund]

Dein Output sieht aus, als ob du einen inkompatiblen Termin/Kontakt versuchst zu importieren…

Tatsächlich meldete Akonadi bis gestern einige solcher Fehler. Wirkliche Probleme gab es nicht. Wie kann ich diese Fehlermeldungen bereinigen?

[Bequimao]

Schau in die Datei (als User, nicht als Root)

Code: Alles auswählen

cat ~/.local/share/akonadi/db_data/mysql.err

Wenn es Hinweise auf falsche Formate von Datenbankfeldern oder Tabellen gibt, können die mit

Code: Alles auswählen

$ mysql_upgrade -u akonadi --socket=/run/user/$UID/akonadi/mysql.socket

korrigiert werden.

Grüße
Bequimão

[linuxfreund]

Schau in die Datei (als User, nicht als Root)

Code: Alles auswählen

cat ~/.local/share/akonadi/db_data/mysql.err

Wenn es Hinweise auf falsche Formate von Datenbankfeldern oder Tabellen gibt, ...

Ich kann keine Fehler entdecken.

Code: Alles auswählen

2023-02-16 11:52:26 0 [Note] Starting MariaDB 10.5.19-MariaDB source revision f8a85af8ca1c937b8d4f847477bd282f80251cde as process 324768
2023-02-16 11:52:26 0 [Note] InnoDB: Uses event mutexes
2023-02-16 11:52:26 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-02-16 11:52:26 0 [Note] InnoDB: Number of pools: 1
2023-02-16 11:52:26 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-02-16 11:52:26 0 [Note] InnoDB: Using Linux native AIO
2023-02-16 11:52:26 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2023-02-16 11:52:26 0 [Note] InnoDB: Completed initialization of buffer pool
2023-02-16 11:52:26 0 [Note] InnoDB: 128 rollback segments are active.
2023-02-16 11:52:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-02-16 11:52:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-02-16 11:52:26 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-02-16 11:52:26 0 [Note] InnoDB: 10.5.19 started; log sequence number 12425373854; transaction id 5220246
2023-02-16 11:52:26 0 [Note] InnoDB: Loading buffer pool(s) from ~/.local/share/akonadi/db_data/ib_buffer_pool
2023-02-16 11:52:26 0 [Note] Reading of all Master_info entries succeeded
2023-02-16 11:52:26 0 [Note] Added new Master_info '' to hash table
2023-02-16 11:52:26 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.5.19-MariaDB'  socket: '/run/user/1000/akonadi/mysql.socket'  port: 0  Mageia MariaDB Server
2023-02-16 11:52:26 0 [Note] InnoDB: Buffer pool(s) load completed at 230216 11:52:26

[Bequimao]

Ja, das ist ok. Es sieht so aus, als ob die Fehler automatisch bereinigt wurden. Nach deinen Angaben läuft es jetzt ja. Das würde ich so hinnehmen.

Bequimão

[linuxfreund]

Ja, das ist ok. Es sieht so aus, als ob die Fehler automatisch bereinigt wurden. Nach deinen Angaben läuft es jetzt ja. Das würde ich so hinnehmen.

Akonadi meldet leider immer noch den gleichen Fehler.

Code: Alles auswählen

$ akonadictl restart &
...
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
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.relationtable                              OK
akonadi.relationtypetable                          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
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
"Could not create file 'file:///run/media/sfrank/DENA/icalout_pkal-ma.ics'."
org.kde.pim.akonadicontrol: Akonadi server is now operational.
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4003f20) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4010680) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4010920) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e401e400) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4013270) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4020af0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e401f910) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e40146d0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e404e240) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e403cf70) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4060ee0) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4003f20) identified as "ETMCalendarMonitor - 25267728"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4073760) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4010680) identified as "ItemMonitorMonitor - 43252464"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e408dde0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4098180) )
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:33Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:33Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:33.170 UTC Qt::UTC)))(":1", QVariant(qlonglong, 371)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e40db9f0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e40dc960) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e401e400) identified as "AgentBaseChangeRecorder - 35613120"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e401f910) identified as "AgentBaseChangeRecorder - 28699856"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4020af0) identified as "AgentBaseChangeRecorder - 29915008"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4010920) identified as "AgentBaseChangeRecorder - 6919584"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4013270) identified as "AgentBaseChangeRecorder - 25423584"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e40db9f0) identified as "akonadi_maildispatcher_agent - 25485360"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e40dc960) identified as "SpecialCollectionsMonitor - 25436256"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e40146d0) identified as "AgentBaseChangeRecorder - 27082496"
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4136760) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4136760) )
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4061860) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4061860) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e404e240) identified as "AgentBaseChangeRecorder - 17374864"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4136760) identified as "KNotes Session - 17434512"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4060ee0) identified as "AgentBaseChangeRecorder - 12559072"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4063070) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e40620f0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4061970) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4136f70) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e414a5f0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4190e70) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4192a50) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4061970) identified as "AgentBaseChangeRecorder - 13336080"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e41adbd0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e41ae8a0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4176d70) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e40620f0) identified as "AgentBaseChangeRecorder - 35893728"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4063070) identified as "AgentBaseChangeRecorder - 26527552"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e41adbd0) identified as "AgentBaseChangeRecorder - 18121184"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e41ae8a0) identified as "akonadi_birthdays_resource - 18178208"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e41b0730) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e414a5f0) identified as "AgentBaseChangeRecorder - 14997568"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e41f4200) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e41fd5e0) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4136f70) identified as "AgentBaseChangeRecorder - 7445136"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4176d70) identified as "AgentBaseChangeRecorder - 27874304"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e42204a0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4221350) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e41fda30) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e403cf70) identified as "AgentBaseChangeRecorder - 29212336"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4061860) identified as "Archive Mail Kernel ETM - 29605872"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e41b0730) identified as "ArchiveMailCollectionMonitor - 30445136"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e41f4200) identified as "AgentBaseChangeRecorder - 9531120"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e42204a0) identified as "AgentBaseChangeRecorder - 9797600"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4192a50) identified as "AgentBaseChangeRecorder - 14567856"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4190e70) identified as "AgentBaseChangeRecorder - 17263776"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4276dc0) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4073760) identified as "AgentBaseChangeRecorder - 30332960"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e41fd5e0) identified as "AgentBaseChangeRecorder - 5292784"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4098180) identified as "AgentBaseChangeRecorder - 14276880"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e41fda30) identified as "UnifiedMailboxChangeRecorder - 140726302722800"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4221350) identified as "AgentBaseChangeRecorder - 9331280"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4276dc0) identified as "AgentBaseChangeRecorder - 22902928"
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e42b4f10) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e42b6070) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e426e640) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e42230c0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4222c50) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e408dde0) identified as "AgentBaseChangeRecorder - 22053328"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e42b6070) identified as "MailFilter Kernel ETM - 22180080"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e426e640) identified as "FilterManagerTagMonitor - 16655440"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e42230c0) identified as "MailFilterCollectionMonitor - 23287936"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4222c50) identified as "MailFilterItemMonitor - 23298288"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f45e4303f20) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f45e4303f20) identified as "SpecialCollectionsMonitor - 24246832"
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-10"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-10" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-11"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-11" : event id differs from file name
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:35Z' for column `akonadi`.`pimitemtable`.`atime` at row 12616"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:35Z' for column `akonadi`.`pimitemtable`.`atime` at row 12616 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:35.056 UTC Qt::UTC)))(":1", QVariant(qlonglong, 283)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-12"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-12" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-13"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-13" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-14"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-14" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-15"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-15" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-16"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-16" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-17"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-17" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-18"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-18" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-19"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-19" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-20"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-20" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-1"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-1" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-2"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-2" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-3"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-3" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-4"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-4" : event id differs from file name
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.166 UTC Qt::UTC)))(":1", QVariant(qlonglong, 625)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.174 UTC Qt::UTC)))(":1", QVariant(qlonglong, 954)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.178 UTC Qt::UTC)))(":1", QVariant(qlonglong, 955)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.181 UTC Qt::UTC)))(":1", QVariant(qlonglong, 953)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.185 UTC Qt::UTC)))(":1", QVariant(qlonglong, 828)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.199 UTC Qt::UTC)))(":1", QVariant(qlonglong, 829)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.297 UTC Qt::UTC)))(":1", QVariant(qlonglong, 827)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-5"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-5" : event id differs from file name
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.596 UTC Qt::UTC)))(":1", QVariant(qlonglong, 626)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.605 UTC Qt::UTC)))(":1", QVariant(qlonglong, 956)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:40Z' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime, QDateTime(2023-02-16 19:27:40.616 UTC Qt::UTC)))(":1", QVariant(qlonglong, 369)))
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE ( PimItemTable.collectionId = :1 )"
org.kde.pim.akonadiserver: Unable to update item access time
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-6"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-6" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-7"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-7" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-8"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-8" : event id differs from file name
org.kde.pim.kalarmdirresource: Deleting 1410 excess events found in file "~/.local/share/akonadi_ical_resource_0//std.ics-9"
org.kde.pim.kalarmdirresource: File "~/.local/share/akonadi_ical_resource_0//std.ics-9" : event id differs from file name
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver:   Error code: "1292"
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2023-02-16T19:27:41Z' for column `akonadi`.`pimitemtable`.`datetime` at row 1"
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2023-02-16T19:27:41Z' for column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(int, 0))(":1", QVariant(QString, "dccb6db7-d51a-444f-b32f-deefe434e974"))(":2", QVariant(QString, ""))(":3", QVariant(QString, ""))(":4", QVariant(qlonglong, 280))(":5", QVariant(qlonglong, 9))(":6", QVariant(QDateTime, QDateTime(2023-02-16 19:27:41.929 UTC Qt::UTC)))(":7", QVariant(QDateTime, QDateTime(2023-02-16 19:27:41.929 UTC Qt::UTC)))(":8", QVariant(bool, false))(":9", QVariant(qlonglong, 0)))
org.kde.pim.akonadiserver:   Query: "INSERT INTO PimItemTable (rev, remoteId, remoteRevision, gid, collectionId, mimeTypeId, datetime, atime, dirty, size) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
org.kde.pim.akonadiserver: Error during insertion into table "PimItemTable" "Incorrect datetime value: '2023-02-16T19:27:41Z' for column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
org.kde.pim.akonadiserver: Error while handling command CreateItem on connection akonadi_kalarm_dir_resource_0 (0x1de7900)
org.kde.pim.akonadicore: ""
org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Failed to append item"
org.kde.pim.akonadicore: Error during ItemSync:  "Failed to append item"

Ich stelle jetzt mal die gesamte Ausgabe des Starts von Akonadi hier hinein. Am Ende ist die gleiche Fehlermeldung wie heute Vormittag, als ich diesen Fred startete.
Immer noch wüsste ich gern, ob jemand meine Feststellung, "gestern lief KMail noch, heute nicht mehr" bestätigen kann.

[linuxfreund]

MariaDB meldet Fehlercode 1292. Auch heute wieder.
Akonadi will Zeitangaben in einem ungültigen Format schreiben. Warum wurde hier bis Mittwoch nicht gemeckert?
Hier wird das erklärt: https://sebhastian.com/mysql-incorrect-datetime-value/

Scheinbar bin ich eine kleine Minderheit, mit der Nutzung von Kontact und Akonadi. Welchen anderen Persönlichen Informationsmanager sollte ich anstelle von Kontact verwenden?

[sturmvogel]

Gibt bereits einen Bugreport
https://bugs.mageia.org/show_bug.cgi?id=29359

[linuxfreund]

Vielen Dank an sturmvogel für den Link.
Da steht, es werden gerade neue Pakete gebaut.
Das werde ich abwarten

[Pappmann89]

@linuxfreund
Ja, Du bist nicht der einzige, dem Gestern KMail, KOrganizer und KAdressbook um die Ohren geflogen sind.
Bei mir hat KMail die heruntergeladenen E-Mails nicht in der Datenbank speichern können.
Außerdem konnte ich keine Termine oder Kontakte ändern oder neu anlegen.

[linuxfreund]

Heute aktualisierte ich einzig das Paket lib64qt5-database-plugin-mysql aus dem Medium "Core Updates Testing" auf die Version 5.15.2-4.8.mga8.x86_64. Es ließ sich allein installieren. Fehlende Abhängigkeiten gab es nicht.
Zu meiner Überraschung und Freude funktioniert Akonadi wieder. Alle Module in Kontact liefen ohne Fehlermeldung.
Allerdings sind scheinbar Kalenderdaten aus meiner Nextcloud-Instanz nicht übertragen worden. Dort hatte ich gestern via Nextcloud im Webbrowser einen neuen Termin eingetragen. Das werde ich bis Mittwoch prüfen.

[hwm]

Scheinbar bin ich eine kleine Minderheit, mit der Nutzung von Kontact und Akonadi. Welchen anderen Persönlichen Informationsmanager sollte ich anstelle von Kontact verwenden?

Nein, bist Du nicht. Ich war auch einer, bis vor kurzem. Und war immer sehr zufrieden, mit Kmail. Nach diesem Akonadi Gau habe ich umgestellt auf den Vivaldi Mail Client und muss sagen: sehr zufrieden, bisher

[jkowalzik]

Scheinbar bin ich eine kleine Minderheit, mit der Nutzung von Kontact und Akonadi. Welchen anderen Persönlichen Informationsmanager sollte ich anstelle von Kontact verwenden?

Hallo!
Ich benutze seit mehr als 10 Jahren Evolution.
Einfach top.
Gruß
J.

[doktor5000]

Einfach top? Naja, deine ganzen Threads (über ein Dutzend) dazu mit diversen Problemen sagen da dezent etwas anderes

[jkowalzik]

Hallo
Gut, kleine Einschränkung, "in letzter Zeit".
Die meisten Fehler hatten 2 Ursachen.
1. Das Problem saß vor dem Bildschirm.
2. GTK Anwendung in Qtx Umgebung.
Die Entwickler arbeiten mit Gnome und jetzt soll das in Plasma KDE laufen.
Immer wenn was größeres geändert wurde, dann mussten auch die "Stützrädchen" neu justiert werden.
Das Schönste ist die Nähe zu "Autluck". (Haben die, mit denen ich zusammenarbeiten muss auch, obwohl Evolution nicht alles so kann wie das Original).
Gruß J.

[Pappmann89]

Heute alle aktuellen Updates eingespielt.

Schwitz, Puls!!!

so nun nach einigen akonadi-verzeichnis zurück Kopieraktionen:

Alle Daten wieder da!!

Aber: hat jemand von euch KDE-PIM-Usern mal probiert mit pimdataexporter seine Akonadi zu sichern?
funktioniert ja anscheinend, aber das wiederherstellen bringt nur eine leere Anzeige.

pimdataexporter.png (8.57 KiB) 1718-mal betrachtet

Grüße Torsten

[linuxfreund]

Nach der Aktualisierung vor mehreren Wochen lief alles wie gewohnt.
Doch heute hängte sich scheinbar Akonadi immer wieder auf. Ich machte mangels besserer Alternativen mehrfach einen Neustart.
Der Befehl

Code: Alles auswählen

akonadictl restart

brachte keine befriedigenden Ergebnisse.
Was kann ich hier tun, diesen ärgerlichen Zustand zu reparieren?

KMail mit der Fehlermeldung

[linuxfreund]

Heute stellte ich beim manuellen Start von Akonadi eine neue Fehlermeldung fest.

Code: Alles auswählen

$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now.
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!

Was könnte die Ursache dieser Fehlermeldung sein?

Falls weitere Systemausgaben gewünscht sind, schickt bitte die Befehle für das Terminal.

[linuxfreund]

Dank Start von Kontact im Terminal erhielt ich folgende Fehlermeldungen:

Code: Alles auswählen

$ Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls")
org.kde.pim.messageviewer:  more than 1 contact was found we return first contact
kf.calendarcore: The incidence didn't have any UID! Report a bug  to the application that generated this file.
kf.calendarcore: The incidence didn't have any UID! Report a bug  to the application that generated this file.
Incidence has empty UID. id= 409510 ; summary= "XXX" Please fix it. Ignoring this incidence.
Incidence has empty UID. id= 304178 ; summary= "XXX" Please fix it. Ignoring this incidence.

Wer kann mit diesen Fehlermeldungen etwas anfangen?

[linuxfreund]

Hallo allerseits,
nachdem Kontact zuletzt gar nicht mehr startete, aktivierte ich am Wochenende ein komplett neues Benutzerkonto.
Das brachte den erhofften Erfolg. Doch gerade eben blockiert KMail den Versand einer Nachricht, weil eine laufende Synchronisation den gesamten Übertragungsweg blockiert.
Wie kann ich so eine Blockade lösen?
Wer kennt dieses Verhalten von KMail?

Übrigens probierte ich Evolution. Das erwies sich als nicht brauchbare Alternative. Alleine die Trennung von Identitäten von den Login-Daten für IMAP und SMTP ist ein Segen, den augenscheinlich nur KMail bietet.

[linuxfreund]

Die Ansicht der laufenden Prozesse liefert diese Ausgabe:

Code: Alles auswählen

$ ps -ef | grep -i kontact
xxx      6969    6832  1 08:49 ?        00:01:15 /usr/bin/kontact -session 1028823b1d11e1000168049908100000067470013_1680555490_710311
xxx      7193    6969  0 08:49 ?        00:00:00 /usr/lib64/qt5/libexec/QtWebEngineProcess --type=zygote --no-zygote-sandbox --disable-in-process-stack-traces --application-name=kontact --webengine-schemes=cid:sC;qrc:sLV --lang=de
xxx      7194    6969  0 08:49 ?        00:00:00 /usr/lib64/qt5/libexec/QtWebEngineProcess --type=zygote --disable-in-process-stack-traces --application-name=kontact --webengine-schemes=cid:sC;qrc:sLV --lang=de
xxx      7203    7194  0 08:49 ?        00:00:00 /usr/lib64/qt5/libexec/QtWebEngineProcess --type=zygote --disable-in-process-stack-traces --application-name=kontact --webengine-schemes=cid:sC;qrc:sLV --lang=de

Wer kann diese Prozesse erklären?

[doktor5000]

Was genau erklären? Und wie soll das bei dem Problem mit Kmail helfen ?

Prinzipiell gibt es einiges an Ressourcen zum Thema kontact/kmail Troubleshooting, was hast du denn schon konkret ausprobiert?

https://docs.kde.org/stable5/en/kmail/k ... oting.html
https://userbase.kde.org/KMail/FAQs_Hin ... _send_mail
https://kb.kolabenterprise.com/document ... leshooting