Version: 4.8.x (using KDE 4.8.0) OS: Linux after starting linux i have a akonadiserver (and several resource processes) running (e.g. confirmed by top) opening a konsole typing: akondaictl status however says: Akonadi Control: stopped Akonadi Server: stopped Akonadi Server Search Support: not available akonadictl stop does nothing ! and akonadictl start then starts a second instance of the akonadiserver (in the top list i have two akonadiservers ?) moreover using Alt + F2 i can stop the initial akonadi processes started with system start with akonadictl stop the problem that arises in this way is that if i start a application that relies on akonadi (e.g. kontact) it will start a second instance of the akonadi resources which are not stopped after klosing the konsole !!! After a while i end up with a large number of akonadiserver and sub processes! I observe the similar behavior with the nepomukserver ! i guess this could be the source of several more strange behaviors of akaonadi / kontact Any ideas on the source of this error and how to fix this ? Thank you Christoph Reproducible: Always Steps to Reproduce: start linux check that akonadiserver is running (e.g. via top) open konsole type: akonadictl status > Akonadi server stopped akonadi start starts a second instance of akonadiserver Actual Results: from konsole the running akonadi server is not found two akonadi servers running Expected Results: akonadictl status from konsole should give Akonadiserver is running !
Is it reproducible ? what does akonadictl --status report ? when you encounter this issue again, please run 'ps x |grep akonadi' and paste the result
reprocucible: yes always... using konsole window i get the follwing output: > akonadictl status Akonadi Control: stopped Akonadi Server: stopped Akonadi Server Search Support: not available > ps x |grep akonadi 2095 ? Sl 0:02 /usr/bin/akonadi_control 2097 ? Sl 1:00 akonadiserver 2099 ? Sl 0:52 /usr/sbin/mysqld --defaults-file=/home/ckirst/.local/share/akonadi/mysql.conf --datadir=/home/ckirst/.local/share/akonadi/db_data/ --socket=/home/ckirst/.local/share/akonadi/socket-kagalaska.nld/mysql.socket 17125 ? Sl 0:00 /usr/bin/akonadi_control 17128 ? Sl 0:07 akonadiserver 17154 ? Sl 0:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_4 17155 ? S 0:00 /usr/bin/akonadi_birthdays_resource --identifier akonadi_birthdays_resource 17156 ? S 0:00 /usr/bin/akonadi_calendarsearch_agent --identifier akonadi_calendarsearch_agent 17157 ? Sl 0:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0 17158 ? S 0:00 /usr/bin/akonadi_davgroupware_resource --identifier akonadi_davgroupware_resource_4 17159 ? S 0:00 /usr/bin/akonadi_davgroupware_resource --identifier akonadi_davgroupware_resource_7 17160 ? Sl 0:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_6 17162 ? Sl 0:01 /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_1 17163 ? Sl 0:00 /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resource_0 17164 ? S 0:00 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent 17165 ? S 0:00 /usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent 17166 ? Sl 0:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder 17167 ? Sl 0:00 /usr/bin/akonadi_agent_launcher akonadi_notes_resource akonadi_notes_resource_1 17669 ? Sl 0:02 /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_0 18410 pts/3 S+ 0:00 grep --color=auto akonadi so there seem to run even two akonadiserver instances (one started probabily by kontact as it was also not able to find the server ?) and konsole cannot find it ? Please let me know how to resolve this issue ? Or what the origin of this error is ? Thank you Christoph
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.