538692 - Gloda database is not rebuilt

Status: RESOLVED DUPLICATE of bug 520139

(Thunderbird :: Search, defect)

Description

[ARF]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0

After conversion from TB2 to TB3 not all my messages had been indexed by gloda for some reason: i.e. some messages were inaccessible with the global search.

On the following page I found the tip to delete the gloda file in the user directory and restart TB to force reindexing:
http://ubuntuforums.org/showthread.php?p=8597248

Unfortunately, after a restart, the gloda file is create (size ~37 KB) but no indexing takes place. The file size remains unchanged. Disabling and re-enabling global search in the options dialog has no effect.

Reproducible: Always

Steps to Reproduce:
1. Delete gloda file
2. Try global search (i.e. no messages are found)
Actual Results:  
Gloda database is not rebuilt.

Expected Results:  
Messages should be re-indexed and gloda database should be rebuilt.

Comment 1

[Wayne Mery (:wsmwk)]

asuth may have more specific idea or instructions but until then 
1. ensure that your messages are really on disk (gloda depends somewhat on this) by using https://addons.mozilla.org/en-US/thunderbird/addon/9873
2. see what you get out of https://wiki.mozilla.org/Thunderbird:Debugging_Gloda

Comment 2

[ARF]

1. I installed GlodaQuilla and restarted. All messages were on disk but had no gloda id or gloda dirty flag. No indexing was initiated.

2. I then followed https://wiki.mozilla.org/Thunderbird:Debugging_Gloda. BUT:
- my machine has no browser.dom.window.dump.enabled option or similar
- I accidentally restarted thunderbird with --console instead of -console. Obviously I did not get a console window. Also no indexing was taking place.

3. I stopped Thunderbird again and restarted with the correct -console option and indexing started right away with lots of gloda messages scrolling by. The indexing is still running but it seems to be working so far.

I am puzzled why the -console comand line option should make the difference...

On a possibly related matter: I have an IMAP account of a server that is no longer online. Most email are on disk, a few recent ones are not. I am keeping the account as an archive. Might this have caused the problem initially?

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

Gloda will not index if Thunderbird is put into offline mode.  Is it possible the inability to access the account decided Thunderbird to switch to offline mode (or this otherwise occurred)?

Comment 4

[ARF]

TB was not put into offline mode after installation. Only the server of one of my accounts was not online and is not being synchronized.

Might the problem have been, that my computer crashed during the initial indexing run? The crash was not realated to TB but it might have made Gloda think that it had already indexed - not realizing that it was interrupted.

In any case, I believe the problem is difficult to investigate further, given that it has resolved itself during the debugging attempt.

I am not against closing the bug report and reopening it when somebody else can confirm the problem.

Comment 5

[Andrew Sutherland [:asuth] (he/him)]

Ah, yeah, this is bug 520139 given that the crash happened.  I did not understand your use of the term "restart" in the initial message to mean this which is why I thought it might be something else.

Comment 6

[ARF]

Actually I think the "restart" meant what you first thought. The sequence was as follows:

1. upgraded to TB 3.0
2. indexing started
3. entire system crashed, restarted system
4. started firefox, indexing did not resume, index only partial
5. closed firefox and deleted the sqlite file
6. reopened firefox but the database was not being rebuilt

7. I wrote the bug report

8. changed TB setting as advised in comment #1.
9. started TB with -console: no indexing 
10. realized mistake: closed TB
11. started TB with --console: indexing started

Odd, no?

I think it is not really a duplicate because in comment #4 the user said:
"I deleted global-messages-db.sqlite and restarted thunderbird.
I left it indexing overnight and after restart the problem happens again."

In my case indexing never even started after deleting the sqlite-file...