[Nepomuk] general questions: virtuoso-t & nepomukstorage, desktopsearch
Sebastian Trüg
trueg at kde.org
Fri Oct 14 07:34:11 UTC 2011
maybe the port is different. Check the command line to start virtuoso
and then look into the config file:
ps aux|grep virtuoso
Cheers,
Sebastian
On 10/13/2011 09:06 PM, Ignacio Serantes wrote:
> On Thu, Oct 13, 2011 at 8:44 PM, Sebastian Trüg <trueg at kde.org
> <mailto:trueg at kde.org>> wrote:
>
> Hi Mat,
>
> On 10/13/2011 03:58 PM, Matthias Lechner wrote:
> >> I have not noticed this problem in my systems but I have quite
> limited
> >> indexed folders to maintain my database as small as possible. If
> you don't
> >> have manual data: tags, ratings, coments, maybe deleting your
> database could
> >> help.
> > I tried that once, when I did a complete reset of my akonadi/nepomuk
> > installation. It did not change anything, unfortunately. Also, the
> duration of
> > the lag seems to be connected with the size of the database, which
> might
> > explain why you do not observe this behaviour. However, reducing
> the database
> > size is not useful for me, since the very reason why I need an
> indexer is that
> > my files are so numerous that I cannot find them on my own quickly.
>
> It would be interesting to know if the indexing of all files has
> finished. If virtuoso is spiking we could debug the issue by logging
> into the db:
>
> isql localhost:1111 dba dba
>
>
> I was trying this but I only obtained an error message:
>
> [ISQL]ERROR: Could not SQLConnect
>
> is this normal?
>
>
> and then calling:
>
> status();
>
> Then the problematic queries should be shown which should help to debug
> the problem.
>
> Another important issue are the versions of everything: kde, strigi,
> akonadi.
>
> >> In theory if don't appears then there is not indexed. Consider that
> >> strigi service fails indexing some files, for example flac files,
> so you may
> >> experiencing this problem.
> > Hm, but this problem also occurs with such general stuff like
> directories.
> > strigi should be able to index directories, and it successfully
> does for at
> > least some. But is there any log file that says "failed to index
> blabla" ?
>
> I have a patch which introduces exactly that functionality as a hidden
> config option. Sadly I cannot test it due to some weird linker problem I
> cannot figure out.
> But I attached the patch in case you want to give it a try. It applies
> in kde-runtime/nepomuk. You need to add "debug mode=true" to
> ~/.kde/share/config/nepomukstrigirc for it to work. Then failures are
> written to ~/.kde/share/apps/nepomuk/file-indexer-error-log
>
>
> A really useful information. Maybe I will do a try.
>
>
>
> Directories are normally indexed just fine.
>
>
> Yes, I was wrong :(. I'm don't know why I thought that strigi is not
> indexing directories.
>
>
>
> Cheers,
> Sebastian
>
> >> I developed an alternative search method that might be useful to
> you. It's
> >> not integrated in KDE, Krunner or Dolphin, for desing reasons but
> it has a
> >> good query language, supports UTF-8 and don't supports Akonadi
> :). Nepoogle
> >> is called and you can found here:
> >
> > Thanks, maybe I'll try that!
> >
> > Regards,
> > Mat
> >
> > _______________________________________________
> > Nepomuk mailing list
> > Nepomuk at kde.org <mailto:Nepomuk at kde.org>
> > https://mail.kde.org/mailman/listinfo/nepomuk
> >
>
> _______________________________________________
> Nepomuk mailing list
> Nepomuk at kde.org <mailto:Nepomuk at kde.org>
> https://mail.kde.org/mailman/listinfo/nepomuk
>
>
>
>
> --
> Best wishes,
> Ignacio
>
>
>
>
> _______________________________________________
> Nepomuk mailing list
> Nepomuk at kde.org
> https://mail.kde.org/mailman/listinfo/nepomuk
More information about the Nepomuk
mailing list