On 04/10/2014 09:52 PM, Daniel Vrátil wrote:
On Thursday 10 of April 2014 18:03:15 José Matos wrote:
> Hi,
> after the last update of akonadi from unstable I got a message
> saying that the it was updating the the data, and that it could take a
> few minutes depending on the size of the data.
>
> I left the computer on all night and this morning it was still the same
> warning (progress bar).
>
> I have close kmail/kontact and now akonadi does not start.
>
> $ akonadictl start
> Starting Akonadi Server...
> Unable to register service as "org.freedesktop.Akonadi.Control.lock"
> Maybe it's already running?
> "[
> 0: /usr/bin/akonadi_control(_Z11akBacktracev+0x4a) [0x437c5a]
> 1: /usr/bin/akonadi_control() [0x437ed2]
> 2: /lib64/libc.so.6(+0x35cb0) [0x7fe39f127cb0]
> 3: /lib64/libc.so.6(gsignal+0x39) [0x7fe39f127c39]
> 4: /lib64/libc.so.6(abort+0x148) [0x7fe39f129348]
> 5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84)
> [0x7fe3a046cd04]
> 6: /usr/bin/akonadi_control(_ZN15FileDebugStream9writeDataEPKcx+0xad)
> [0x439c9d]
> 7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7fe3a050bfb0]
> 8: /lib64/libQtCore.so.4(+0x120c85) [0x7fe3a051bc85]
> 9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7fe3a0524e51]
> 10: /usr/bin/akonadi_control(_ZN6QDebugD1Ev+0x49) [0x41a559]
> 11: /usr/bin/akonadi_control(main+0x397) [0x417247]
> 12: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fe39f113d65]
> 13: /usr/bin/akonadi_control() [0x417541]
> ]
> "
> Error: akonadi_control was started but didn't register at D-Bus session bus.
> Make sure your system is set up correctly!
>
> Looking into the previous ~/.xsession-errors this same message is
> repeated there.
>
> Suggestions are welcome, :-)
Looks like another instance of akonadi_control is already running, maybe it
god somehow stuck after an upgrade? Can you make sure that no akonadi_control
or akonadiserver process is running, then try again?
Dan
Hi Daniel,
the akonadi server seems to be trapped in a continuous loop. If I
kill one another one is started. So it is not obvious how to proceed.
Looking to top I notice that there is a mysqld process running for 55
min (the computer is now up for 7h24m).
This seems to be the same pattern of yesterday.
Regards,
--
José Matos