Bug 361542 - akonadictl fsck seems to hang
Summary: akonadictl fsck seems to hang
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Chakra Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-09 05:38 UTC by Knut Hildebrandt
Modified: 2017-10-02 12:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.6.2


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Hildebrandt 2016-04-09 05:38:33 UTC
A way to get rid of left over mails in ~/.local/share/akonadi/file_db_data is invoking "akonadictl fsck" which moves all entries not in use anymore to ~/.local/share/akonadifile_lost+found from where they can be deleted. That worked fine for me until recently. After an update earlier this week "akonadictl fsck" seems to hang. Even if I run it for hours it neither finishes nor is there any output on the console. 

Reproducible: Always

Steps to Reproduce:
1.  stop Akonadi: akonadictl stop
2.  wait some time to let Akonadi stop
3.  check that Akonadi has stopped: akonadictl status
4.  run Akonadi filecheck: akonadictl fsck

Actual Results:  
it runs for ever without any output

Expected Results:  
it should stop after a while and report on console what it has done

Output of akonadictl --version -> 5.1.51

Update was from 15.12.3-1 -> 15.12.3-2
Comment 1 Knut Hildebrandt 2016-07-27 17:38:28 UTC
The error still persists. No I'm having this setup on my machine:

Plasma 5.7.2
Applications 16.04.3
Qt 5.7.0

But I noticed one thing. After stopping Akonadi there are still Akonadi related processes running on my machine. They all are called http.so and somehow seem to have to do with the DAV-resources I set up to synchronize my calendar and address book.

Might it be that these processes prevent "akonadictl fsck" from doing it's job?
Comment 2 Freek de Kruijf 2017-10-02 11:03:59 UTC
I had the same problem after "akonadictl stop". There was no CPU activity related to an akonadi process. However the command works when the status is "running".
BTW. same for "akonadictl vacuum".
Comment 3 Daniel Vrátil 2017-10-02 12:16:45 UTC
akonadictl fsck is supposed to be run when Akonadi is running. Admittably, running it against stopped Akonadi should produce an error and quit, not hang. I'll work on that.

http.so are KIO slaves, they are kept around for a while so they can be effectively reused, but should eventually die on their own if they are unused for longer period of time.
Comment 4 Daniel Vrátil 2017-10-02 12:24:50 UTC
Git commit aebf8a1b727c81cb317cebf712dc19a8ec3e5944 by Daniel Vrátil.
Committed on 02/10/2017 at 12:23.
Pushed by dvratil into branch 'Applications/17.08'.

akonadictl: fsck and vacuum require running Akonadi
FIXED-IN: 5.6.2

M  +11   -1    src/akonadictl/main.cpp

https://commits.kde.org/akonadi/aebf8a1b727c81cb317cebf712dc19a8ec3e5944