[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Baloo] [Bug 341581] baloo_file - using 100% cpu
From:       Cory F Cohen <cfcohen () verizon ! net>
Date:       2015-05-01 0:01:21
Message-ID: bug-341581-17878-oVDHfequFz () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=341581

Cory F Cohen <cfcohen@verizon.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cfcohen@verizon.net

--- Comment #13 from Cory F Cohen <cfcohen@verizon.net> ---
Top reported "10035 cory      39  19  471780  38144   5904 R 100.0  0.2  
6689:43 baloo_file".
That's more than 4 days at 100% CPU.  So reading the thread I tried: "balooctl
disable".  Which produced:

...
SQL Committed
Removing: 16 docs
ERROR DocNotFoundError: Can't delete non-existent document #28
ERROR DocNotFoundError: Can't delete non-existent document #29
ERROR DocNotFoundError: Can't delete non-existent document #30
ERROR DocNotFoundError: Can't delete non-existent document #31
ERROR DocNotFoundError: Can't delete non-existent document #32
ERROR DocNotFoundError: Can't delete non-existent document #33
ERROR DocNotFoundError: Can't delete non-existent document #38
ERROR DocNotFoundError: Can't delete non-existent document #69
ERROR DocNotFoundError: Can't delete non-existent document #73
ERROR DocNotFoundError: Can't delete non-existent document #246
ERROR DocNotFoundError: Can't delete non-existent document #309
ERROR DocNotFoundError: Can't delete non-existent document #311
ERROR DocNotFoundError: Can't delete non-existent document #357
ERROR DocNotFoundError: Can't delete non-existent document #358
ERROR DocNotFoundError: Can't delete non-existent document #362
ERROR DocNotFoundError: Can't delete non-existent document #363
Adding: 0 docs
Xapian Committed
SQL Committed

But the process did not exit.  Several more attempts to run "balooctl disable"
would report only "Disabling the File Indexer", but not actually kill the
process.   Running "kill 10035" successfully killed the process, and "balooctl
status" now reported that the indexer was NOT running, and that it had indexed
0/0 files.  Running "balooctl enable" appears to have created an index after a
few minutes, because I can now run baloosearch and balooshow.

I doubt that this will help much in troubleshooting the problem, but I at least
wanted to report that it occurred.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]