[Bug 1200432] New: akonadiserver: Database process exited unexpectedly during initial connection!
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 Bug ID: 1200432 Summary: akonadiserver: Database process exited unexpectedly during initial connection! Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: ndordea@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 859533 --> http://bugzilla.opensuse.org/attachment.cgi?id=859533&action=edit full jornalctl -a leap 15.3 kmail/kontact worked fine against my leap 15.3 was executed zypper up .... went fine shutdown restart with the DVD-leap-15.4 ... it run without fine .... reboot/start HD After DVD upgrade to leap 15.4, kmail does not start . akonadictl status Akonadi Control: stopped Akonadi Server: stopped Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin) Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_followupreminder_agent, akonadi_google_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mailmerge_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource akonadictl start org.kde.pim.akonadictl: Starting Akonadi Server... org.kde.pim.akonadictl: done. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) rocco@suse4Rocco<[--> ~ ]> 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/rocco/.local/share/akonadi/mysql.conf", "--datadir=/home/rocco/.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: "2022-06-10 11:28:56 0 [Note] /usr/sbin/mysqld (server 10.6.7-MariaDB) starting as process 24183 ...\n" org.kde.pim.akonadiserver: exit code: 6 org.kde.pim.akonadiserver: process error: "Process crashed" org.kde.pim.akonadiserver: Shutting down AkonadiServer... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally... Even if akonadi complains of database, akonadi database can be used via mysql -h localhost -u root -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 21 Server version: 10.6.7-MariaDB MariaDB package Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases ; +--------------------+ | Database | +--------------------+ | akonadi | | amarok | | amarokdb | | cookbook | | information_schema | | mysql | | performance_schema | | sys | | test | +--------------------+ 9 rows in set (0.000 sec) MariaDB [(none)]> use akonadi ; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [akonadi]> show tables; +----------------------------------+ | Tables_in_akonadi | +----------------------------------+ | collectionattributetable | | collectionmimetyperelation | | collectionpimitemrelation | | collectiontable | | flagtable | | mimetypetable | | parttable | | parttypetable | | pimitemflagrelation | | pimitemtable | | pimitemtagrelation | | relationtable | | relationtypetable | | resourcetable | | schemaversiontable | | tagattributetable | | tagremoteidresourcerelationtable | | tagtable | | tagtypetable | +----------------------------------+ 19 rows in set (0.000 sec) MariaDB [akonadi]> select count(*) from collectiontable; +----------+ | count(*) | +----------+ | 190 | +----------+ 1 row in set (0.001 sec) MariaDB [akonadi] quit Bye It seems that akonadi is the culprit . Is it any solution to use kmail without akonadi ? Attached are some files collected : journalctl, some mysql/akonadi info Please help me to regain the access to my emails . Thanks ND -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c1 --- Comment #1 from Nick Dordea <ndordea@gmail.com> --- Created attachment 859534 --> http://bugzilla.opensuse.org/attachment.cgi?id=859534&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=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c2 --- Comment #2 from Nick Dordea <ndordea@gmail.com> --- Created attachment 859535 --> http://bugzilla.opensuse.org/attachment.cgi?id=859535&action=edit manual access/use of akonadi db -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c3 --- Comment #3 from Nick Dordea <ndordea@gmail.com> --- Created attachment 859536 --> http://bugzilla.opensuse.org/attachment.cgi?id=859536&action=edit it seems that socket was not created ... changed run-user-1000-akonadi permissions -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c4 --- Comment #4 from Nick Dordea <ndordea@gmail.com> --- Created attachment 859537 --> http://bugzilla.opensuse.org/attachment.cgi?id=859537&action=edit mysql-check against all databases works [ including akonadi] -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c5 --- Comment #5 from Nick Dordea <ndordea@gmail.com> --- Created attachment 859538 --> http://bugzilla.opensuse.org/attachment.cgi?id=859538&action=edit journalctl for mysql+akonadi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 Nick Dordea <ndordea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |ndordea@gmail.com Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c6 --- Comment #6 from Nick Dordea <ndordea@gmail.com> --- Hello , I expected that for any user not being able to receive/see his/her emails is not a trivial matter. On the contrary there are things that for any user are VITAL. As Juran used to say .... Vital few, trivial many ! it seems that the support solve first the trivial issues [ mainly "user-error" ] and not the VITAL issues that are not user errors but system/application errors. So, it appears that the priority/severity are something cosmetic and not related to the gravity for the user. So if after 2 days I haven't received at least support's acknowledgement I decide to create a new kmail environment and use the most recent kmail archive and get the access to my emails. Is true that I lost some emails ..... however the old "akonadi" database is gone .... so I can not provide any information you may be interested in. You can continue if you wish ,,,, good luck !!!!! It seems that kmail/akonadi+MariaDB solution has some issues linked mainly when any/all of that trio is/are upgraded. That may be the case with this ticket that appears being ignored by the kde/akonadi support team . This is enough to express my regret/sadness about kde/akonadi's status of affairs. Hopefully there would better days in the future. Nd -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c7 --- Comment #7 from Nick Dordea <ndordea@gmail.com> --- Is there a solution of using kmail+MariaDB directly without akonadi services ? If so, could you provide the procedure of doing the change as well as a system wide option regarding akonadi similar to the existing options for another products ? Let the user decide what he puts on his/her system . ND -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c9 --- Comment #9 from Nick Dordea <ndordea@gmail.com> --- (In reply to Fabian Vogt from comment #8)
mysql.err clearly shows that the database got corrupted, there's unfortunately not much you can do at that point. Turning on recovery mode and trying to pull as much data is the best option, but might not result in a usable clone.
I agree that the error messages during akonadi initiated/controlled start point to corrupted data. However, the akonadi database was available via mysql -h localhost -u root -p I can not explain how comes that after mysql -h localhost -u root -p , sql queries worked .... not only sql queries but also mysql-check did not point to any issues with table belonging to akonadi database . Is akonadi ceating/using a proprietary database different from the akonadi database accessed via mysql -h localhost -u root -p ? It is very strange complains that the connection fails while other user/utility has problems. Could you please tell me if we can customize kmail to access akonadi database directly without database services provided via "akonadi" packages ? Thanks, ND -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c10 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de --- Comment #10 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Nick Dordea from comment #9)
(In reply to Fabian Vogt from comment #8)
mysql.err clearly shows that the database got corrupted, there's unfortunately not much you can do at that point. Turning on recovery mode and trying to pull as much data is the best option, but might not result in a usable clone.
I agree that the error messages during akonadi initiated/controlled start point to corrupted data.
However, the akonadi database was available via mysql -h localhost -u root -p I can not explain how comes that after mysql -h localhost -u root -p , sql queries worked .... not only sql queries but also mysql-check did not point to any issues with table belonging to akonadi database .
Is akonadi ceating/using a proprietary database different from the akonadi database accessed via mysql -h localhost -u root -p ?
By default, akonadi's database can be connected to with mysql -S /run/user/1000/akonadi/mysql.socket It's also possible that errors only appear with write accesses.
It is very strange complains that the connection fails while other user/utility has problems.
Could you please tell me if we can customize kmail to access akonadi database directly without database services provided via "akonadi" packages ?
There's a way, but the UI for that got removed so you'd have to edit ~/.config/akonadi/akonadiserverrc manually.
Thanks,
ND
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 http://bugzilla.opensuse.org/show_bug.cgi?id=1200432#c11 --- Comment #11 from Nick Dordea <ndordea@gmail.com> --- (In reply to Fabian Vogt from comment #10)
(In reply to Nick Dordea from comment #9)
(In reply to Fabian Vogt from comment #8)
mysql.err clearly shows that the database got corrupted, there's unfortunately not much you can do at that point. Turning on recovery mode and trying to pull as much data is the best option, but might not result in a usable clone.
I agree that the error messages during akonadi initiated/controlled start point to corrupted data.
However, the akonadi database was available via mysql -h localhost -u root -p I can not explain how comes that after mysql -h localhost -u root -p , sql queries worked .... not only sql queries but also mysql-check did not point to any issues with table belonging to akonadi database .
Is akonadi ceating/using a proprietary database different from the akonadi database accessed via mysql -h localhost -u root -p ?
By default, akonadi's database can be connected to with mysql -S /run/user/1000/akonadi/mysql.socket
It's also possible that errors only appear with write accesses.
It is very strange complains that the connection fails while other user/utility has problems.
Could you please tell me if we can customize kmail to access akonadi database directly without database services provided via "akonadi" packages ?
There's a way, but the UI for that got removed so you'd have to edit ~/.config/akonadi/akonadiserverrc manually.
Thanks,
ND
--------------- I think that I included in the attachements some info about /run/user/1000/akonadi/mysql.socket In one instance it was not created .... due to some permission issues. Manually I changed the permissions of /run/user/1000 directory ....to allow changes for group + others The attempt to start kmail failed again, but the socket was created. Then I tried to get to akonadi db via Beeheper Studio tool [ found on snap ] that use the socket for connection ..... It failed ..... My feeling is that the socket might had some issues ... The changed /run/user/1000 permissions were changed back their default [ No access] . The most recent archive was 2 days prior the upgrade to 15.4 .... so I decided to restore db based on the archive ..... renamed akonadi_[imap...|maildir....|migration_agent... ] recreated [ via kmail] accounts [ as before ] import from archive .... back in business with out any problems ..... Maybe the fact that the socket was not created or created with tweaked permissions has something to do with the start/connect initiated/handled by akonadi applications. Hope that this d woulhelp. Regards. ND I -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200432 Nick Dordea <ndordea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ndordea@gmail.com | -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com