From: Leonard Lausen <leonard@lausen.nl>
To: notmuch@notmuchmail.org
Subject: Re: Bug: fatal error with notmuch new, second run starts indexing all over again
Date: Sun, 01 Jul 2018 15:36:23 +0000 [thread overview]
Message-ID: <87tvpjhsso.fsf@lausen.nl> (raw)
In-Reply-To: <20170714212703.wn5ben7tygr7c6sx@len.workgroup>
I also experience this error trying to import the emacs-orgmode mailing
list archive. Has there been any progress on fixing the issue? What
steps should be taken to help?
Also it seems that the midsize corpus
https://giku.de/reduced-sample-midsized.xapian-exeption.tar.xz is not
available anymore.
David introduced a patch to improve the error message, below I paste the
message I get:
add_file: A Xapian exception occurred
A Xapian exception occurred adding message: Unexpected end of posting list for 'G00000000000255c6'.
Processed 4949 total files in 10m 13s (8 files/sec.).
Added 4921 new messages to the database.
Note: A fatal error was encountered: A Xapian exception occurred
Gregor Zattler <telegraph@gmx.net> writes:
> Hi David,
> * David Bremner <david@tethera.net> [14. Jul. 2017]:
>> Gregor Zattler <telegraph@gmx.net> writes:
>>> I redid the test on this mid-sized corpus and I got an
>>> exeption (again):
>> [snip]
>>> Error: A Xapian exception occurred. Halting processing.
>>> Processed 27611 total files in 21m 2s (21 files/sec.).
>>> Added 27481 new messages to the database.
>>> Note: A fatal error was encountered: A Xapian exception occurred
>>> [Inferior 1 (process 6752) exited with code 01]
>>> (gdb)
>>
>> I can finally replicate the crash. I do crash in a different place
>> (after processing 25184 files), so it suggests a certain non-determinism
>> or dependence on the host configuration.
>
> I would assume the first difference is in the file system:
> Perhaps the files are accessed in a different order!?
>
>> Anyway, now that I have a test case, I'll try and figure out what the
>> underlying Xapian exeception is.
>
>
> Thanks.
>
> Ciao, Gregor
> --
> -... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2018-07-01 17:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 10:09 Bug: fatal error with notmuch new, second run starts indexing all over again Gregor Zattler
2017-07-03 10:46 ` David Bremner
2017-07-03 22:07 ` Gregor Zattler
2017-07-03 22:34 ` David Bremner
2017-07-05 16:46 ` Tomi Ollila
2017-07-06 9:31 ` Gregor Zattler
2017-07-09 12:36 ` David Bremner
2017-07-09 14:21 ` Gregor Zattler
2017-07-09 14:35 ` David Bremner
2017-07-13 7:04 ` Gregor Zattler
2017-07-13 10:31 ` David Bremner
2017-07-13 11:31 ` Gregor Zattler
2017-07-13 13:03 ` David Bremner
2017-07-13 13:59 ` Gregor Zattler
2017-07-13 18:26 ` David Bremner
2017-07-14 10:14 ` Gregor Zattler
2017-07-14 11:13 ` David Bremner
2017-07-14 21:27 ` Gregor Zattler
2018-07-01 15:36 ` Leonard Lausen [this message]
2018-07-03 21:57 ` Gregor Zattler
2018-07-08 2:07 ` David Bremner
2018-07-08 9:46 ` Gregor Zattler
2018-07-08 2:09 ` David Bremner
2018-07-09 15:31 ` Leonard Lausen
2018-07-10 11:11 ` David Bremner
2021-12-25 18:10 ` David Bremner
2021-12-27 19:05 ` confirmed (was: Bug: fatal error with notmuch new, second run starts indexing all over again) Gregor Zattler
2021-12-28 0:58 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvpjhsso.fsf@lausen.nl \
--to=leonard@lausen.nl \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).