rkt logo

INN FAQ Part 7

NOTE: The maintainers of the INN FAQ stopped publishing in December 1997.
An important update to this topic is provided by Mib Software in the Usenet RKT for Subscribers.

Subject: (7.35) I'm seeing duplicate message-id's in my history database!

Something is wrong with your history database. This is one of those
things that "can never happen". In order to verify that something
is really wrong with your database, run the following command:

awk -F' ' '{ print $1 }' < history|grephistory -i

(that first thing in quotes is a tab, not a space)

This will take a while to run, but the result _should_ contain no output.

If it does output anything then the dbz database is hosed. You'll need
to rebuild the dbz files from the history file using the "-r" flag to
"makehistory" using the process as described in the news-recovery(8)
man page.

If you still have problems after this, then it could be due to some
garbage in your history file which is causing problems with dbz.
There really isn't a good tool (yet!) to fix this. What needs to
be written is a history file "sanitizer", which examines each line
of the file and checks it for nulls, wacko dates, huge lines,
and the like. ( Some of this already has been integrated into expire(8)
in the "1.4unoff" release, however more could be done. At least
now expire doesn't crash when it encounters garbage. ) If you
do write such a program, please submit it to barr@cis.ohio-state.edu
(Dave Barr)

If you do fix your database, but problems re-appear later then perhaps
your O/S is at fault. Make sure your O/S has been patched to fix any
bugs related to mmap(). In your config.data try turning off -DMMAP in
DBZCFLAGS and recompile. If you still have problems, reset DBZINCORE
to 0.


[Source: INN FAQ Part 7 Archive-name: usenet/software/inn-faq/part7]
[Last Changed: $Date: 1997/09/16 01:25:57 $ $Revision: 2.25 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]