Hello dear experts and readers!

First of all, thanks for that really matured KDE software.
Since I re-installed Mint Maya KDE on my computer after a hard disc crash, I have the problem, that after each login there is an akonadi server error, that simply says that the nepomuk query server isn't available. I learned how to deal with this the kick-butt-way (simply restart akonadi does the trick) but I want to get more knowledge about that nepomuk stuff, because the capability to store tags / comments / ratings to my data files and to search for them using comments / tags / ratings was one of my main reasons to choose KDE as my working desktop environment.
So the first question is:
What exactly is the nepomuk query server needed for, what are its tasks? (I guess it has less to do with indexing, but the more with sql-ish parts of nepomuk? Anyway, it keeps Kontact from checking my ressources and Akonadi from doing backups while not working.)
Second question:
How can I find out the reason, why akonadi can't find the nepomuk query server right after the login? Are there any tools / commands I could use to dig deeper for the source(s) of evil?
Third question:
Is there any workaround that does not require a restart of akonadi?

Regards and thanks in advance for any helpful tip
Aldicku

aldicku wrote:Hello dear experts and readers!

First of all, thanks for that really matured KDE software.
Since I re-installed Mint Maya KDE on my computer after a hard disc crash, I have the problem, that after each login there is an akonadi server error, that simply says that the nepomuk query server isn't available. I learned how to deal with this the kick-butt-way (simply restart akonadi does the trick) but I want to get more knowledge about that nepomuk stuff, because the capability to store tags / comments / ratings to my data files and to search for them using comments / tags / ratings was one of my main reasons to choose KDE as my working desktop environment.
So the first question is:
What exactly is the nepomuk query server needed for, what are its tasks? (I guess it has less to do with indexing, but the more with sql-ish parts of nepomuk? Anyway, it keeps Kontact from checking my ressources and Akonadi from doing backups while not working.)
Second question:
How can I find out the reason, why akonadi can't find the nepomuk query server right after the login? Are there any tools / commands I could use to dig deeper for the source(s) of evil?
Third question:
Is there any workaround that does not require a restart of akonadi?

Regards and thanks in advance for any helpful tip
Aldicku

1. The Nepomuk Query service is needed for searching through emails and for auto-completion when typing contacts.
2. You should probably check if nepomuk is running -

$ nepomukctl status

Does restarting Akonadi fix the problem?

vHanda wrote:1. The Nepomuk Query service is needed for searching through emails and for auto-completion when typing contacts.
2. You should probably check if nepomuk is running -

$ nepomukctl status

Does restarting Akonadi fix the problem?

Hi Vishesh,

thanks for your answer. As I wrote already, the restart of Akonadi solves the problem every time. And the result of
$ nepomukctl status
is

Nepomuk Server is running.
Service storage is running.
Service fileindexer is running.
Service filewatch is running.

After using the Nepomuk cleaner it seems that the problem has been solved, after the next reboot there was not longer any current akonadi error report, which I check with an autostart script that might be helpful for other users with the same problem:

Code: Select all

#!/bin/sh
if test -f ~/.local/share/akonadi/akonadiserver.error
then
  kdialog --title "Akonadi-Server" --textbox ~/.local/share/akonadi/akonadiserver.error
  kdialog --title "Akonadi-Server" --warningyesno "Restart Akonadi?"
    if [ "$?" -eq "0" ]
    then
      akonadictl restart
    fi
else
  kdialog --title "Akonadi-Server" --msgbox "No Akonadi server error log"
fi

because it checks at each login if there is an Akonadi server error log and if there is one, it provides a choice to restart Akonadi via dialog box.

But I found out now, that something went wrong with the indexing. Almost all folders I assigned for indexing in the Nepomuk system settings aren't indexed indeed. I expect to get around 150,000 files to be indexed, but Nepomuk only gives back some 4,000 indexed files. How can I find out which settings or files are responsible for this behaviour? And how can I recreate the wanted index? Probably the best way would be to go step by step and make Nepomuk reindexing specific folders. How can I do this? [EDIT] I know now: I found out the answer in an blog by Sebastian Trüg, regarding a forced re-indexing of folders (for KDE >= 4.8). It even shows a really handy way to include this method as a context menu action in dolphin. The method itself is the command:

Code: Select all

qdbus org.kde.nepomuk.services.nepomukfileindexer /nepomukfileindexer org.kde.nepomuk.FileIndexer.indexFolder FolderpathHere 1 1

where FolderpathHere is to substitute by the path to the desired folder.
Using this solution, soon I had lots of my files indexed. But still far from complete. (Some 50,000 are still missing.) The thing is, the command to re-index folders is too quiet in my opinion, it should allow to adjust the level of its verbosity between -debug and -quiet. How do I find out, what files might cause disturbances in Nepomuk?[/EDIT]
I would appreciate any hint, because I really want to get the advantage of this adjuvant technology, which was one of the main reasons to make KDE the desktop environment of my choice.

Best regards
Aldicku

Sorry, again me.

After rethinking everything I've learned in the last few days about Akonadi/Nepomuk I came to the conclusion that I mixed here two different problems. To make this clear, my first concern was to get rid of that more or less constant Akonadi Error "nepomuk query server not available". (Yes, even now it happens constantly again each session, not always at login time, but after half-an-hour of work, if I start my test skript manually, it mostly answers with the thread subject.)
As Vishesh Handa (the maintainer of KDE Nepomuk atm) explained, Nepomuk query server is needed for searching through emails and for auto-completion when typing contacts. This means, it can't have to do anything with my second problem, the lots of files that are unindexed yet, which I will handle in a separate thread in the future. And even if nobody else can give an advice, I will add any additional knowledge about solving the problem about the crashing Nepomuk Query Server here in this thread.
@Vishesh: Could any output of Akonadiconsole be helpful in finding the reason for the unexpected non-availability of Nepomuk Query Server?
So first I will identify the process itself namly (should be something like nepomukquery*) for grepping it with a cronjob from the process list to find when it dies. After that, I will check all output of Akonadiconsole. Maybe it delivers a hint.

Thanks in advance for any help
Aldicku