# Revision history [back]

### tracker-extract: What's causing the following probem?

Since a couple of weeks, I encounter a problem with tracker-extract. One symptom is that it keeps my CPU very busy (and hot).

Checking the journal, I see a lot of messages there: They look like:

Could not insert metadata for item "file:///home/james/vboxshare/blablabla/blablabla%20and%20%20temp%20WTP/40335-02-ME-Feasibility%20Study.pdf": 43.32: invalid UTF-8 character


It is also giving me errors like the following without telling me which file is concerned:

This OLE2 file is invalid.
The Block Allocation Table for one of the streams had 0x00000000 instead of a terminator (0xfffffffe).
We might still be able to extract some data, but you'll want to check the file.


And another message is:

ole_seek_block: assertion 'block < ole->info->max_block' failed


I have already erased my tracker database (tracker reset --hard) but after re-indexing the problem(s) continue.

Anyone any idea on how to fix it? I don't care about tracker not being able to index some of the files - it's more the CPU usage that is annoying.

### tracker-extract: What's causing the following probem?

Since a couple of weeks, I encounter a problem with tracker-extract. One symptom is that it keeps my CPU very busy (and hot).

Checking the journal, I see a lot of messages there: They look like:

Could not insert metadata for item "file:///home/james/vboxshare/blablabla/blablabla%20and%20%20temp%20WTP/40335-02-ME-Feasibility%20Study.pdf": 43.32: invalid UTF-8 character


It is also giving me errors like the following without telling me which file is concerned:

This OLE2 file is invalid.
The Block Allocation Table for one of the streams had 0x00000000 instead of a terminator (0xfffffffe).
We might still be able to extract some data, but you'll want to check the file.


And another message is:

ole_seek_block: assertion 'block < ole->info->max_block' failed


I have already erased my tracker database (tracker reset --hard) but after re-indexing the problem(s) continue.

Anyone any idea on how to fix it? I don't care about tracker not being able to index some of the files - it's more the CPU usage that is annoying.

### tracker-extract: tracker-extract keeping CPU busy and hot: What's causing the following probem?problem?

Since a couple of weeks, I encounter a problem with tracker-extract. One symptom is that it keeps my CPU very busy (and hot).

Checking the journal, I see a lot of messages there: They look like:

Could not insert metadata for item "file:///home/james/vboxshare/blablabla/blablabla%20and%20%20temp%20WTP/40335-02-ME-Feasibility%20Study.pdf": 43.32: invalid UTF-8 character


It is also giving me errors like the following without telling me which file is concerned:

This OLE2 file is invalid.
The Block Allocation Table for one of the streams had 0x00000000 instead of a terminator (0xfffffffe).
We might still be able to extract some data, but you'll want to check the file.


And another message is:

ole_seek_block: assertion 'block < ole->info->max_block' failed


(I get about 36 of such messages every minute)

I have already erased my tracker database (tracker reset --hard) but after re-indexing the problem(s) continue.

Anyone any idea on how to fix it? I don't care about tracker not being able to index some of the files - it's more the CPU usage that is annoying.

### tracker-extract keeping CPU busy and hot: What's causing the problem?

Since a couple of weeks, I encounter a problem with tracker-extract. One symptom is that it keeps my CPU very busy (and hot).

Checking the journal, I see a lot of messages there: recurring messages. They look like:

Could not insert metadata for item "file:///home/james/vboxshare/blablabla/blablabla%20and%20%20temp%20WTP/40335-02-ME-Feasibility%20Study.pdf": 43.32: invalid UTF-8 character


It is also giving me errors like the following without telling me which file is concerned:

This OLE2 file is invalid.
The Block Allocation Table for one of the streams had 0x00000000 instead of a terminator (0xfffffffe).
We might still be able to extract some data, but you'll want to check the file.


And another message is:

ole_seek_block: assertion 'block < ole->info->max_block' failed


(I get about 36 of such messages every minute)minute - it's completely spamming my log).

I have already erased my tracker database (tracker reset --hard) but after re-indexing the problem(s) continue.

Anyone any idea on how to fix it? I don't care about tracker not being able to index some of the files - it's more the CPU usage that is annoying.