Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assertion in db.c fails, leading to abort trap #15

Open
larryhynes opened this issue Sep 5, 2019 · 2 comments
Open

Assertion in db.c fails, leading to abort trap #15

larryhynes opened this issue Sep 5, 2019 · 2 comments

Comments

@larryhynes
Copy link

Hi

 $ mairix -v -p

mairix DEVELOPMENT, Copyright (C) 2002-2010 Richard P. Curnow
mairix comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the GNU General Public License for details.

Finding all currently existing messages...
Reading existing database...
Assertion failed: (nt->match1.highest < n_msgs), function import_toktable2, file db.c, line 412.
Abort trap: 6

The db in question is approx. 24M, if that's relevant; here's what it looks like after a fresh indexing run:

Wrote 32603 messages (652060 bytes of tables, 2899041 bytes of text)
Wrote 0 mbox headers (0 bytes of tables, 0 bytes of paths)
Wrote 0 bytes of mbox message checksums
To: Wrote 11795 tokens (94360 bytes of tables, 170867 bytes of text, 259613 bytes of hit encoding)
Cc: Wrote 3563 tokens (28504 bytes of tables, 48724 bytes of text, 41836 bytes of hit encoding)
From: Wrote 7844 tokens (62752 bytes of tables, 106980 bytes of text, 225559 bytes of hit encoding)
Subject: Wrote 11748 tokens (93984 bytes of tables, 88691 bytes of text, 206157 bytes of hit encoding)
Body: Wrote 579794 tokens (4638352 bytes of tables, 5200170 bytes of text, 7717808 bytes of hit encoding)
Attachment Name: Wrote 5522 tokens (44176 bytes of tables, 129209 bytes of text, 23229 bytes of hit encoding)
(Threading): Wrote 34405 tokens (275240 bytes of tables, 1705835 bytes of text, 301234 bytes of hit encoding)
@larryhynes
Copy link
Author

I should mention that this is not reliably reproduceable. :( Things will work for weeks / months, then this happens.

@larryhynes
Copy link
Author

This happened again today, same error message.

I'm going to try running without the -p flag on the daily indexing run and see how that goes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant