Registered Member
|
Hello
Each time i open a session i have an error message which says that indexing is disabled, can you help me understand this please ? Thanks i'm using opensuse 11.3 and Qt: 4.7.1 KDE Development Platform: 4.5.90 (4.6 RC1) error message : " Nepomuk Indexing Agents Have Been Disabled The Nepomuk service is not available or fully operational and attempts to rectify this have failed. Therefore indexing of all data stored in the Akonadi PIM service has been disabled, which will severely limit the capabilities of any application using this data. The following problems were detected: Calling the Nepomuk storage service failed: 'The name org.kde.NepomukStorage was not provided by any .service files'. Additional help can be found here: userbase.kde.org/Akonadi"
manchette, proud to be a member of KDE forums since 2008-Oct.
last openSUSE version : Leap 42.1... / Last Kde Plasma version : 5.0.xxx ... |
Manager
|
in systemsettings -> workspace appearance & behavior -> desktop search is Nepomuk checked?
|
Registered Member
|
Yes it is, i think opensuse does not activate this as default, but i did.
I have Nepomuk active and file indexer idle.
manchette, proud to be a member of KDE forums since 2008-Oct.
last openSUSE version : Leap 42.1... / Last Kde Plasma version : 5.0.xxx ... |
Registered Member
|
I just updated to 4.7 over the weekend, and I'm running into the same problem with Nepomuk, with exactly the same error message. I tried removing my virtuoso database and rebuilding from scratch, but the same error keeps appearing some way into building the index.
I ran nepomukserver with all stderr output to a file so I could get more details about the problem. The stderr file is 133MB in size. It appears to have failed while indexing an ebook. The lines immediately after look like this:
There is more, but it is just attempts to restart the service stub and virtuoso, and failing. Unfortunately, I don't have anything built with debug output enabled, and I don't particularly want to rebuild it all just to find the fault with nepomuk. I can live without it, but it is still annoying. For the record, this never happened with Nepomuk building a full index under 4.6.x. |
Administrator
|
Can you please post the lines before and when it gets itself into trouble? Does X remain up? "Fatal IO error: client killed" usually means X has crashed...
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
The lines before what I posted are the contents of an ebook, which I cannot paste into the forum for legal reasons. It was sending a LOT of the ebooks (around 133MB of text) to stderr for some reason.
And yes, X is still up, and KDE is still working. The only thing that fails is the nepomukstorage service stub, which causes the rest of nepomuk to exit as cleanly as it can. |
Administrator
|
Ok, best option in this case is to disable indexing for the directory that contains the EBook files, then report a bug at bugs.kde.org. As DrKonqi starts, it should be possible to generate a backtrace.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I'll do that, but it still leaves me wondering why Nepomuk had no problems at all indexing that directory before. What changed?
|
Administrator
|
It is probable that some signature within the file triggers a bug somehow within Strigi. This could be due to the fact that the indexer now supports the files in question, or the way it supports them has been altered.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]