Adonadi not operational

[Ovidiu-Florin BOGDAN]

It's akonadiCTL not akonadiCLT. Short for akonadi control.

Force reinstalling means just that: forcing the package manager to
re-install all the required packages. Just in case some files are corrupt
or missing. An alternative is to completely uninstall and reinstall the
whole PIM suite.

Sâm, 29 iun. 2019, 00:20 Sid Hymes <sidhymes at gmail.com> a scris:

> Thanks. What's strange is that it was working w/o issue prior to the
> update so it sounds like the update "overwrote" or inadvertently deleted
> part of the total package.
> So I reinstalled kdepim and rebooted - the response is still that Akonadi
> is not operational. Please see attached. This screen appeared after first
> telling me Akonadi was not running and to start it. 'akonadiclt start'
> still reports that "command not found".
> When I did the install, only 3 packages were installed and akonadi was not
> among them; see attached. Do I need to consider reinstalling the whole kde
> package group?
> Thanks again for your help!
>
> On Fri, Jun 28, 2019 at 1:38 PM Ovidiu-Florin Bogdan <ovidiu.b13 at gmail.com>
> wrote:
>
>> Akonady is not a systemd service. It's a user process. `akonadictl` is a
>> command line tool that helps control that process.
>>
>>
>>
>> From your response I deduce that you don't have the full KDE PIM suite
>> installed.
>>
>>
>>
>> I recommend that you force reinstall the KDE PIM suite.
>>
>>
>>
>> Regards,
>>
>> Ovidiu
>>
>>
>>
>> În ziua de vineri, 28 iunie 2019, la 20:32:53 EEST, Sid Hymes a scris:
>>
>> Thank you very much for the prompt response.
>>
>>
>> The response to both requests,`akonadictl status` and 'akonadiclt start',
>> (in bash) is 'command not found'. And when I tried 'systemctl status
>> akonadi', the response was 'Unit akonadi.service could not be found'.
>>
>>
>> The contents of the akonadiserver.error file is:
>>
>> 2019-06-28T08:09:14 [INFO ] org.kde.pim.akonadiserver: Starting up the
>> Akonadi Server...
>> 2019-06-28T08:09:14 [CRITICAL] org.kde.pim.akonadiserver: Failed to use
>> database "akonadi"
>> 2019-06-28T08:09:14 [CRITICAL] org.kde.pim.akonadiserver: Database error:
>> "Can't connect to local MySQL server through socket
>> '/tmp/akonadi-sid.i3Siz4/mysql.socket' (2) QMYSQL: Unable to connect"
>> 2019-06-28T08:09:14 [CRITICAL] org.kde.pim.akonadiserver: Failed to
>> connect to database!
>> 2019-06-28T08:09:14 [CRITICAL] org.kde.pim.akonadiserver: Database error:
>> "Can't connect to local MySQL server through socket
>> '/tmp/akonadi-sid.i3Siz4/mysql.socket' (2) QMYSQL: Unable to connect"
>> 2019-06-28T08:09:14 [CRITICAL] org.kde.pim.akonadiserver: Failed to
>> remove runtime connection config file
>> 2019-06-28T08:09:14 [INFO ] org.kde.pim.akonadiserver: Shutting down
>> AkonadiServer...
>>
>>
>> Mysql (or mariadb) is installed in /usr/bin/mysql.
>>
>>
>> Thanks for you help.
>>
>>
>>
>> On Fri, Jun 28, 2019 at 9:49 AM Ovidiu-Florin Bogdan <
>> ovidiu.b13 at gmail.com> wrote:
>>
>> What does `akonadictl status` say? Can you start it with `akonadiclt
>> start`?
>>
>>
>>
>> În ziua de vineri, 28 iunie 2019, la 18:14:37 EEST, Sid Hymes a scris:
>>
>> Hi,
>>
>>
>> After a recent Fedora 30 update, Kontact, etc., no longer function. The
>> error message is "The Akonadi personal information management service is
>> not operational". Clicking the "Details" button brings up nothing.
>>
>>
>> Can anyone suggest a troubleshooting path? I reinstalled Akonadi to no
>> effect.
>>
>>
>> Thanks.
>>
>>
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20190629/76e2e5fe/attachment.html>