"error while indexing" reported

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run mu-index on my Maildir

What is the expected output? What do you see instead?

I see 

$ mu index --rebuild
mu: indexing messages under /home/neil/Maildir [/home/neil/.mu/xapian]
| processing mail; processed: 56403; updated/new: 56403, cleaned-up: 0
mu: elapsed: 267 second(s), ~ 211 msg/s
mu: error while indexing

I am expecting no "error while indexing". The output and the log file give no 
clue as to what went wrong. This is every line in the log file not marked 
"[INFO]".

$ grep -v "\[INFO\]" mu.log
2013-12-19 12:10:01 [MSG ] indexing messages under /home/neil/Maildir 
[/home/neil/.mu/xapian]
2013-12-19 12:10:03 [MSG ] elapsed: 2 second(s), ~ 28200 msg/s
2013-12-19 12:10:03 [WARN] error while indexing
2013-12-19 12:22:42 [MSG ] indexing messages under /home/neil/Maildir 
[/home/neil/.mu/xapian]
2013-12-19 12:27:00 [MSG ] elapsed: 258 second(s), ~ 218 msg/s
2013-12-19 12:27:01 [WARN] error while indexing

What version of the product are you using? On what operating system?
0.9.8.4 on Debian Wheezy amd64

Please provide any additional information below.
Thank you for writing this great tool. 

Having an error on every index means cron e-mails me all the time. And maybe 
some messages didn't get indexed?

Original issue reported on code.google.com by prof.nei...@gmail.com on 19 Dec 2013 at 12:49

[GoogleCodeExporter]

It's hard to say want went wrong... Would it be possible to try this with the 
git version? That should give a little bit more information.

Original comment by digg...@gmail.com on 21 Dec 2013 at 6:02

[GoogleCodeExporter]

Thank you for the reply. I did compile and install the git version. The output 
showed three invalid messages. I checked the messages and they were indeed 
invalid, with a missing header and beginning part way through a message. So I 
deleted them again and did a rebuild, which worked with no problems. So it 
looks like the github version gracefully ignored the bad messages and works 
perfectly. Whether this was the cause of the fail in the original I am not 
sure, but as the github version is working perhaps we can close this bug. Thank 
you for your help.

$ mu index --rebuild
indexing messages under /home/neil/Maildir [/home/neil/.mu/xapian]
/ processing mail; processed: 56550; updated/new: 56550, cleaned-up: 0
mu: message seems invalid, ignoring 
(/home/neil/Maildir/sent/cur/1386281836.000037.mbox:2,S)
| processing mail; processed: 57075; updated/new: 57074, cleaned-up: 0
mu: message seems invalid, ignoring 
(/home/neil/Maildir/sent/cur/1386281836.000610.mbox:2,S)
| processing mail; processed: 57375; updated/new: 57373, cleaned-up: 0
mu: message seems invalid, ignoring 
(/home/neil/Maildir/sent/cur/1386281836.000905.mbox:2,)
- processing mail; processed: 57825; updated/new: 57822, cleaned-up: 0
cleaning up messages [/home/neil/.mu/xapian]
- processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 57867 msg/s
\ processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 271 second(s), ~ 213 msg/s

And after deleting the invalid messages

$ mu index --rebuild
indexing messages under /home/neil/Maildir [/home/neil/.mu/xapian]
- processing mail; processed: 57825; updated/new: 57825, cleaned-up: 0
cleaning up messages [/home/neil/.mu/xapian]
- processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 57867 msg/s
\ processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 273 second(s), ~ 211 msg/s

Original comment by prof.nei...@gmail.com on 27 Dec 2013 at 11:31

[GoogleCodeExporter]

Okay, thanks for verifying this! I'll close this issue.

Original comment by digg...@gmail.com on 29 Dec 2013 at 3:50

• Changed state: Done