SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I encountered the same problem a few days ago with KMail. I haven't captured the output, but after running the commands akonadi was trying to run directly, I get a message saying that MariaDB crashed previously and
Code:
[ERROR] InnoDB: Upgrade after a crash is not supported.
following with a message telling me to downgrade to 10.6, start and stop the server, then upgrade again. So I did that in one go (download the old package from slackware.uk, install it, start with the original command, fix any errors in the command, stop the server, then upgrade with slackpkg). It worked for me. Hope this helps.
The data for akonadi is not kept in the ~/.config/akonadi directory, so most likely you will not loose your data. That said, the smart thing to do would to simply copy or move ~/.config/akonadi to another directory. I just tried that, I choose the move method.
Code:
mv .config/akonadi .config/akonadi.save
The akonadi data is located in .local/share/akonadi/
NOTE" I did this with KDE Plasma shutdown from runlevel 3. As I mentioned above I boot to runlevel 3, so logging out of KDE Plasma dropped me back to the CLI. I would not recommend doing this from with the KDE Plasma running.
After restarting (startx), the .config/akonadi directory was created, all my notes in Knotes were still present.
I tried, but it did not help. I get the same error about akonadi personal information management service not active.
I did it in stages. I don't use runlevel 4 either. I have always booted to runlevel 3, then exec startx.
First, I made /etc/rc.d/rc.mysql not executable and rebooted. I confirmed MariaDB was not running after boot. I got the same error when kontact started during kde start.
Second, I exited plasma and renamed .config/akonadi to .config/akonadi_temp_save, then exec startx again. Same error.
A new .config/akonadi got created. It contains two files only, the akonadiserverrc and akonadiconnectionrc.
If I start akonadi manually with --verbose, I get the following:
Code:
$ akonadictl --verbose start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
s@ixian2:~/.local/share/akonadi$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Found mysql_install_db: "/usr/bin/mysql_install_db"
org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck"
org.kde.pim.akonadiserver: Found mysql_upgrade: "/usr/bin/mysql_upgrade"
org.kde.pim.akonadiserver: Using mysqld: "/usr/libexec/mysqld"
org.kde.pim.akonadiserver: globalConfig : "/etc/kde/xdg//akonadi/mysql-global.conf" localConfig : "" actualConfig : "/home/s/.local/share/akonadi/mysql.conf"
org.kde.pim.akonadiserver: mysqld reports version 10.11.2 (MariaDB)
org.kde.pim.akonadiserver: Executing: "/usr/libexec/mysqld" "--defaults-file=/home/s/.local/share/akonadi/mysql.conf --datadir=/home/s/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid"
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/libexec/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/s/.local/share/akonadi/mysql.conf", "--datadir=/home/s/.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: ""
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: terminating connection threads
org.kde.pim.akonadiserver: terminating service threads
org.kde.pim.akonadiserver: stopping db process
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
It looks to me like Akonadi tries to connect to MariaDB/MySQL (whatever /usr/libexec/mysqld refers to) if it exists, then retries again if that fails. But the retry fails too with "Unknown error".
It looks to me like your issue is with MariaDB. (aka MySQL). Started the MariaDB on boot is not required for Akonadi to work. It is started when KDE Plasma loads (startx).
Based on my observations this akonadiserverrc is created on each startx.
One thing that was achieved is the problem is most likely not in .config/akonadi.
One thing that stands out to me is: (the '/usr/libexec/mysqld' is a symlink to mariadb)
The issue might be in .local/share/akonadi/db_data/ or there could be an issue with .local/share/akonadi/mysql.conf (I doubt this), this is mine:
Code:
#
# 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
#
# measure 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 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)
loose_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))
loose_query_cache_size=0
# Do not cache results (default:1)
loose_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
[client]
default-character-set=utf8
Another thought is have you tried reinstalling mariadb-10.11.2-x86_64-1?
Thanks for all your help and interest in this issue, Chris.
I renamed the /var/lib/mysql directory and did a slackpkg reinstall of mariadb, then ran mysql_install_db --user=mysql as root to recreate the initial database. I left the rc.mysqld startup script non-executable.
Akonadictl start still fails with the same errors, so when I get a chance later today, I will uninstall mariadb completely, then install, initialize, reboot for added measure, and try again. Will update later.
I renamed the /var/lib/mysql directory and did a slackpkg reinstall of mariadb, then ran mysql_install_db --user=mysql as root to recreate the initial database. I left the rc.mysqld startup script non-executable.
This is not necessary. Akonadi sets up is own environment in ~/.local/share/akonadi.
Quote:
Akonadictl start still fails with the same errors, so when I get a chance later today, I will uninstall mariadb completely, then install, initialize, reboot for added measure, and try again. Will update later.
I hadn't looked in /var/lib/mysql yet. Your post reminded me to do just that. Wow, my last uses of mariadb was 2013 and 2018.
So I decided to remove mariadb. Since I have nothing that uses mariadb anymore other than Akonadi, I also removed all traces of mariadb from my system and reinstalled mariadb, reboot, probably not needed but did so anyway. I do not have mariadb set to start on boot (/etc/rc.d/rc.mysql not executable).
Logged in as me and ran startx, an Akonadi is running normally.
Last edited by chrisretusn; 04-27-2023 at 09:36 AM.
My understanding from our conversation up to now is that akondadi doesn't need MySQL / MariaDB to be installed or active, and that the MariaDB package can be completely removed.
So I did that, but "# slackpkg remove mariadb" leaves behind the database in /var/lib/mysql. I renamed that directory so that it could not be found, in order to see if akonadi can really run without it. It appears that it cannot run without it based on the errors I get when I try to start it.
Code:
$ akonadictl --verbose start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
s@ixian2:~/.local/share/akonadi$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Found mysql_install_db: ""
org.kde.pim.akonadiserver: Found mysqlcheck: ""
org.kde.pim.akonadiserver: Found mysql_upgrade: ""
org.kde.pim.akonadiserver: Using mysqld: ""
org.kde.pim.akonadiserver: globalConfig : "/etc/kde/xdg//akonadi/mysql-global.conf" localConfig : "" actualConfig : "/home/s/.local/share/akonadi/mysql.conf"
org.kde.pim.akonadiserver: mysqld not found. Please verify your installation
org.kde.pim.akonadiserver: terminating connection threads
org.kde.pim.akonadiserver: terminating service threads
org.kde.pim.akonadiserver: stopping db process
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
So I renamed my saved folder back to /var/lib/mysql and tried again, and got the exact same errors as above.
Perhaps I've misunderstood the requirements to run akonadi, but it seems that akonadi cannot function without the MariaDB package being installed.
I renamed my ~/.local/share/akonadi to something else. This was just for a test, as I can't do this for real since all my contacts, appointments, to-dos, notes, etc are lost in this case. But as I expected, it did work and kontact will now start.
2023-04-27T10:50:15 [WARN ] default: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: DataStore::unhideAllPimItems()
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740001e10) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74000bf00) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74000c720) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740024540) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74002dda0) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740037610) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74000c720) identified as "plasmashell-2215653713 - 53464576"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740024540) identified as "ETMCalendarMonitor - 31785872"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74002dda0) identified as "TagCacheMonitor - 19439448"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740037610) identified as "ETMCalendarMonitor - 19444784"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740089440) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74008a210) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740089440) identified as "AgentBaseChangeRecorder - 8830496"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7400a81c0) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74008a210) identified as "akonadi_maildispatcher_agent - 8787456"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7400a81c0) identified as "SpecialCollectionsMonitor - 8554224"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7400cad90) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1682610615"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver.search: Search "searchUpdate-1682610615" done (without remote search)
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver.search: Search update for collection "OpenInvitations" ( 2 ) finished: all results: 0 , removed results: 0
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Shutting down "ETMCalendar" ...
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber "TagCacheMonitor - 19439448" disconnected
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber "ETMCalendarMonitor - 19444784" disconnected
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Shutting down "kontact-783954174" ...
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740001e10) identified as "AgentBaseChangeRecorder - 15596560"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7400ca8b0) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber "" disconnected
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7400b99e0) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7400b99e0) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7400cad90) identified as "AgentBaseChangeRecorder - 33487280"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74000bf00) identified as "AgentBaseChangeRecorder - 14829408"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7400b99e0) identified as "KNotes Session - 16106528"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74003e950) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7400ca8b0) identified as "AgentBaseChangeRecorder - 21284080"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740040440) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740103c40) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74003e950) identified as "AgentBaseChangeRecorder - 23144144"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740115bf0) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74011eaf0) )
2023-04-27T10:50:15 [WARN ] org.kde.pim.akonadiserver: Error while handling command DeleteCollection on connection akonadi_maildir_resource_0 (0xf20050)
2023-04-27T10:50:15 [WARN ] org.kde.pim.akonadiserver: Error while handling command DeleteCollection on connection akonadi_maildir_resource_0 (0xf20050)
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740128670) )
2023-04-27T10:50:15 [WARN ] org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_indexing_agent (0xee0ab0)
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740040440) identified as "AgentBaseChangeRecorder - 8861008"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740103c40) identified as "AgentBaseChangeRecorder - 28065120"
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740143cd0) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber "" disconnected
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74014cde0) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74015a600) )
2023-04-27T10:50:15 [WARN ] org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_followupreminder_agent (0xf20f20)
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74014cde0) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7401562f0) )
2023-04-27T10:50:15 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber "" disconnected
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740157070) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740157070) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc74015a430) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740115bf0) identified as "AgentBaseChangeRecorder - 21067632"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74015a600) identified as "MailFilter Kernel ETM - 21123776"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74014cde0) identified as "MailFilterCollectionMonitor - 21132352"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7401562f0) identified as "MailFilterItemMonitor - 21085696"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74011eaf0) identified as "AgentBaseChangeRecorder - 27006800"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740157070) identified as "Archive Mail Kernel ETM - 27064672"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc74015a430) identified as "ArchiveMailCollectionMonitor - 27070752"
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7401b5af0) )
2023-04-27T10:50:15 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7401b5af0) identified as "SpecialCollectionsMonitor - 21111200"
2023-04-27T10:50:16 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7401c7a40) )
2023-04-27T10:50:16 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740128670) identified as "AgentBaseChangeRecorder - 22573664"
2023-04-27T10:50:16 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740143cd0) identified as "AgentBaseChangeRecorder - 35640656"
2023-04-27T10:50:16 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7401c7a40) identified as "UnifiedMailboxChangeRecorder - 140724066899936"
2023-04-27T10:50:55 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7401ad530) )
2023-04-27T10:50:55 [DEBUG] org.kde.pim.akonadiserver: Database "akonadi" opened using driver "QMYSQL"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: Subscriber "" disconnected
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740193b10) )
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc7401a40d0) )
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fc740193b10) )
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7401ad530) identified as "TagCacheMonitor - 18442952"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc7401a40d0) identified as "ETMCalendarMonitor - 18644576"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fc740193b10) identified as "ItemMonitorMonitor - 19288864"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: DATABASE ERROR:
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Error code: "1062"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: DB error: "Duplicate entry '1-OpenInvitations' for key 'CollectionTable_parentAndNameIndex'"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Error text: "Duplicate entry '1-OpenInvitations' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(QString, "OpenInvitations"))(":1", QVariant(qlonglong, 1))(":2", QVariant(qlonglong, 1))(":3", QVariant(QString, "{\n \"limit\": -1,\n \"negated\": false,\n \"rel\": 1,\n \"subTerms\": [\n {\n \"cond\": 0,\n \"key\": \"partstatus\",\n \"negated\": false,\n \"value\": \"reason@monobath.com0\"\n }\n ]\n}\n"))(":4", QVariant(QString, ""))(":5", QVariant(QString, ""))(":6", QVariant(bool, true)))
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Query: "INSERT INTO CollectionTable (name, parentId, resourceId, queryString, queryAttributes, queryCollections, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)"
2023-04-27T10:50:55 [WARN ] org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable" "Duplicate entry '1-OpenInvitations' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
2023-04-27T10:50:55 [WARN ] org.kde.pim.akonadiserver: Failed to append Collection "OpenInvitations" in resource "akonadi_search_resource"
2023-04-27T10:50:55 [WARN ] org.kde.pim.akonadiserver: Error while handling command StoreSearch on connection kontact-1006305489 (0xf25370)
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1682610655"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Search "searchUpdate-1682610655" done (without remote search)
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Search update for collection "DeclinedInvitations" ( 10 ) finished: all results: 0 , removed results: 0
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1682610655"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Search "searchUpdate-1682610655" done (without remote search)
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Search update for collection "OpenInvitations" ( 2 ) finished: all results: 0 , removed results: 0
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: DATABASE ERROR:
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Error code: "1062"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: DB error: "Duplicate entry '1-DeclinedInvitations' for key 'CollectionTable_parentAndNameIndex'"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Error text: "Duplicate entry '1-DeclinedInvitations' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(QString, "DeclinedInvitations"))(":1", QVariant(qlonglong, 1))(":2", QVariant(qlonglong, 1))(":3", QVariant(QString, "{\n \"limit\": -1,\n \"negated\": false,\n \"rel\": 1,\n \"subTerms\": [\n {\n \"cond\": 0,\n \"key\": \"partstatus\",\n \"negated\": false,\n \"value\": \"reason@monobath.com2\"\n }\n ]\n}\n"))(":4", QVariant(QString, ""))(":5", QVariant(QString, ""))(":6", QVariant(bool, true)))
2023-04-27T10:50:55 [CRITICAL] org.kde.pim.akonadiserver: Query: "INSERT INTO CollectionTable (name, parentId, resourceId, queryString, queryAttributes, queryCollections, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)"
2023-04-27T10:50:55 [WARN ] org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable" "Duplicate entry '1-DeclinedInvitations' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
2023-04-27T10:50:55 [WARN ] org.kde.pim.akonadiserver: Failed to append Collection "DeclinedInvitations" in resource "akonadi_search_resource"
2023-04-27T10:50:55 [WARN ] org.kde.pim.akonadiserver: Error while handling command StoreSearch on connection kontact-1006305489 (0xf25370)
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Executing search "searchUpdate-1682610655"
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Search "searchUpdate-1682610655" done (without remote search)
2023-04-27T10:50:55 [INFO ] org.kde.pim.akonadiserver.search: Search update for collection "DeclinedInvitations" ( 10 ) finished: all results: 0 , removed results: 0
Yeah, that's a lot of messages, sorry.
Bottom line, kontact now works, but the slate is clean, none of my data from before exists in the new akonadi state. I still get some errors that are concerning.
I think it's time for me to look for a better-supported PIM.
I think we got a dead horse, here, Chris. Thank you for all your help.
My understanding from our conversation up to now is that akondadi doesn't need MySQL / MariaDB to be installed or active, and that the MariaDB package can be completely removed.
Sorry for the misunderstanding my post from above:
Quote:
Originally Posted by chrisretusn
This is not necessary. Akonadi sets up is own environment in ~/.local/share/akonadi.
I hadn't looked in /var/lib/mysql yet. Your post reminded me to do just that. Wow, my last uses of mariadb was 2013 and 2018.
So I decided to remove mariadb. Since I have nothing that uses mariadb anymore other than Akonadi, I also removed all traces of mariadb from my system and reinstalled mariadb, reboot, probably not needed but did so anyway. I do not have mariadb set to start on boot (/etc/rc.d/rc.mysql not executable).
Logged in as me and ran startx, an Akonadi is running normally.
It is not necessary to run mysql_install_db --user=mysql as root to recreate the initial database. Akonadi sets it self up in ~/.local/share/akonadi.
I don't run Kontact, I think I will give it a try. Maybe we can figure out something to avoid losing your data. I know how that feels, been their done that. Seem like there should be a way to check each database.
My understanding from our conversation up to now is that akondadi doesn't need MySQL / MariaDB to be installed or active, and that the MariaDB package can be completely removed.
So I did that, but "# slackpkg remove mariadb" leaves behind the database in /var/lib/mysql. I renamed that directory so that it could not be found, in order to see if akonadi can really run without it. It appears that it cannot run without it based on the errors I get when I try to start it.
Akonadi runs a private instance of the MariaDB daemon (mysqld) using its own configuration and used only for your own data in your own homedirectory.
The boot script /etc/rc.d/rc.mysql starts a system version of the MariaDB database server, with system-wide databases in /var/lib/mysql/. Akonadi does not use any of that.
As you found out empirically: the system database service does not have to be running, but you need to have the mariadb package installed for Akonadi to work.
I got this error too, but I just removed akonadi files from .config and .local/share. My only problem now is KDE Apps are not asking for my 2FA while loggin on Google, tried Thunderbird and worked without flaws.
I got this error too, but I just removed akonadi files from .config and .local/share. My only problem now is KDE Apps are not asking for my 2FA while loggin on Google, tried Thunderbird and worked without flaws.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
