[Bug 1200860] New: After tumbleweed upgrade akonadiserver cannot start: "lost connection to server during query"
http://bugzilla.opensuse.org/show_bug.cgi?id=1200860 Bug ID: 1200860 Summary: After tumbleweed upgrade akonadiserver cannot start: "lost connection to server during query" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: missoline@protonmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After successfully updating Tumbleweed to the latest snapshot (by cleanly logging out and running the upgrade in a virtual console) and rebooting my computer, while the upgrade was successful, the akonadiserver no longer starts which prevents me from using KMail (the only email client working for me from a performance perspective considering the large size of my email accounts). So basically I cannot do my job anymore. Here is the error message I am getting when trying to run "akonadictl start" (for clarity, I have not included the whole log since the other parts show that everything is starting fine until that point): 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 QMYSQL3: cannot execute query" org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(qlonglong, 1))(":1", QVariant(qlonglong, 2))(":2", QVariant(qlonglong, 16))) org.kde.pim.akonadiserver: Query: "SELECT count(DISTINCT PimItemTable.id), sum(PimItemTable.size), sum(CASE WHEN ( SeenFlags.Flag_id IS NOT NULL OR IgnoredFlags.Flag_id IS NOT NULL ) THEN 1 ELSE 0 END) FROM PimItemTable LEFT JOIN PimItemFlagRelation AS SeenFlags ON ( PimItemTable.id = SeenFlags.PimItem_id AND SeenFlags.Flag_id = :0 ) LEFT JOIN PimItemFlagRelation AS IgnoredFlags ON ( PimItemTable.id = IgnoredFlags.PimItem_id AND IgnoredFlags.Flag_id = :1 ) WHERE ( collectionId = :2 )" org.kde.pim.akonadiserver: database server stopped unexpectedly org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "2006" org.kde.pim.akonadiserver: DB error: "Server has gone away" org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL3: Impossible d'ex�cuter la requ�te" org.kde.pim.akonadiserver: Error code: "2013" org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(qlonglong, 1))(":1", QVariant(qlonglong, 2))(":2", QVariant(qlonglong, 17))) org.kde.pim.akonadicore: "QLocalSocket�: Connexion ferm�e" "/run/user/1000/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket�: connection closed" org.kde.pim.akonadicore: "QLocalSocket�: connection closed" "/run/user/1000/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket�: connection closed" Afterwards, these connection closed error messages cascade until the process crashes. What can I do? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200860 http://bugzilla.opensuse.org/show_bug.cgi?id=1200860#c2 --- Comment #2 from Misso Works <missoline@protonmail.com> --- Created attachment 859802 --> http://bugzilla.opensuse.org/attachment.cgi?id=859802&action=edit mysql.err -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200860 http://bugzilla.opensuse.org/show_bug.cgi?id=1200860#c3 --- Comment #3 from Misso Works <missoline@protonmail.com> --- (In reply to Fabian Vogt from comment #1)
My guess is that the server crashes due to a corrupted database or something like that.
Can you check ~/.local/share/akonadi/db_data/mysql.err?
Thank you for your swift reply. I have attached the file, what are your thoughts? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200860 http://bugzilla.opensuse.org/show_bug.cgi?id=1200860#c5 --- Comment #5 from Misso Works <missoline@protonmail.com> --- Thank you a lot for guidance, I have opted for recreating the database from scratch and KMail can now start and is currently resyncing the data. I am pleasantly surprised to see that account configuration has not been deleted. However this issue should really be investigated in my opinion. Data corruption shouldn't happen randomly after a upgrade. I've heard such reports about akonadi data corruption when I was shopping around for a new email client, but I assumed the problem was old so I was pleasantly surprised to see that everything seemed stable. We are considering relying on the KDE PIM framework and its ecosystem of applications for our workstations as this perspective looks very attractive, but if the database is so fragile, then this is a real problem... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200860 http://bugzilla.opensuse.org/show_bug.cgi?id=1200860#c6 Christopher Yeleighton <giecrilj@stegny.2a.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |giecrilj@stegny.2a.pl --- Comment #6 from Christopher Yeleighton <giecrilj@stegny.2a.pl> --- The upgrade to from 10.7.3-MariaDB to 10.10.2-MariaDB caused 9�GB of the following message to fill the file mysql.err.old, eventually taking up all storage space: [ERROR] Incorrect definition of table mysql.column_stats: expected column This is no way to do business, my good sirs :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200860 http://bugzilla.opensuse.org/show_bug.cgi?id=1200860#c7 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de --- Comment #7 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Christopher Yeleighton from comment #6)
The upgrade to from 10.7.3-MariaDB to 10.10.2-MariaDB caused 9�GB of the following message to fill the file mysql.err.old, eventually taking up all storage space:
[ERROR] Incorrect definition of table mysql.column_stats: expected column
This is no way to do business, my good sirs :-(
That's unrelated. MySQL/MariaDB for some reason needs mysql_upgrade to be called manually and Akonadi doesn't handle that either. So run mysql_upgrade -S $XDG_RUNTIME_DIR/akonadi/mysql.socket after mariadb version upgrades. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com