Re: Nepomuk: re-checking the strigi index constantly
On Wednesday 31 March 2010, Martin Steigerwald wrote:
> Am Dienstag 30 März 2010 schrieb Michael Schuerig:
> > On Sunday 28 March 2010, Michael Schuerig wrote:
> > > Apparently, a new
> > > /usr/bin/nepomukservicestub nepomukstrigiservice
> > > is started every 8 or 9 minutes. from ~/.xsession-errors I can't
> > > see anything that indicates that these processes are crashing.
> >
> > Well, strace and gdb know better. Indexing is interrupted, when an
> > assert statement fails and causes a SIGABRT
> >
> > # strigi-0.7.1/src/streamanalyzer/lineeventanalyzer.cpp:180
> > void
> > LineEventAnalyzer::handleUtf8Data(const char* data, uint32_t
> > length) {
> >
> > assert(!(sawCarriageReturn && missingBytes > 0));
>
> That sounds simular to my bug report (see mail "nepomuk strigi
> service crashed too often" in this list):
>
> https://bugs.kde.org/232395
Similar, but probably not the exact same. In my case, there are no
indications in ~/.xsession-errors that anything went wrong. I've seen
messages of the "crashed to[o] often" kind for *other* problems, but not
for this specific one.
/usr/bin/nepomukservicestub and nepomukservices aren't very helpful as
the process name, have you tried looking at the complete commandline? In
top it's toggled by pressing 'c'.
AFAIUI, Soprano is part of the storage backend used by Nepomuk, whereas
Strigi belongs to the frontend retrieving the (meta)data. Your problem
appears to occurs, when Nepomuk tries to store data in Soprano. Then the
question is, where that data comes from and why it is malformed.
Michael
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
Reply to: