Severe xover corruption problems on INN2.2.1
Hans.Lambermont at garg.mpn.cp.philips.com
Tue Oct 5 15:54:31 UTC 1999
Katsuhiro Kondou wrote:
> In article <19991005170830.A7089 at garg.mpn.cp.philips.com>,
> Hans Lambermont <Hans.Lambermont at garg.mpn.cp.philips.com> wrote;
> } this sm -o prints 2 blank lines. That's not good. So we experience
> } corrupted offset of the overview data in this token ? How should we fix
> } this ? (and prevent it from happening again ;)
> I see the problem. To fix this, you need to recreate overview
> data and index by makehistory. See mekehistory(8) for more.
But i just did that yesterday ?! On 24 Sep i wrote something like:
1 stop innd (ctlinnd throttle, shutdown), actived etc.
2 makehistory -I $PATHTMP/newindex -O -n -b -x
3 sort -t' ' +1 -2 $PATHTMP/newindex > $PATHTMP/newindex.sorted
4 expireindex -a -o -z < $PATHTMP/newindex.sorted
and yesterday i applied this after a succesful run on a test machine. So
i just rebuilt the uniover databases. Or is my above method broken ?
> And as for corrupted offset, I suspect uniover is not replaced
> with new one when expiry. Does expire finish without any problem?
Last night's expire run looks good to me:
expire begin Tue Oct 5 00:10:15 MEST 1999: (-v1 -c -e -z/var/log/nntp/expire.rm
Article lines processed 1709763
Articles retained 1596885
Entries expired 112878
Articles dropped 3
Overview index dropped 141839
Old entries dropped 40812
Old entries retained 63782
expire end Tue Oct 5 00:19:34 MEST 1999
all done Tue Oct 5 00:19:34 MEST 1999
lowmarkrenumber begin Tue Oct 5 00:19:42 MEST 1999: (/var/log/nntp/expire.lowma
lowmarkrenumber end Tue Oct 5 00:19:43 MEST 1999
expireindex start Tue Oct 5 00:19:47 MEST 1999
expireindex end Tue Oct 5 00:30:37 MEST 1999
expirerm start Tue Oct 5 00:30:37 MEST 1999
expirerm end Tue Oct 5 00:30:37 MEST 1999
I hope you see the culprit, because i don't.
More information about the inn-workers