At 05:20 PM 5/6/01 +0200, you wrote:
>In one of my groups (nl.hobby.verzamel.postzegels) there was no feed since
>two weeks, although on the sucking feeders there was... Tried everything
>(but not rebuild_index), nothing helped. So i deleted and purged the group,
>restarted dnews and made the group again. But..... now there are all
>messages from another group nl.actueel.mkz in this group. I have tried this
>with a few readers, resetted the group (including list) but no succes. What
>can i do more, but not a rebuild index. I discovered that alle articlenumers
>will reset, which i don't like to do for the "customers"...
The problem with the group having the wrong items should be fixable by
deleting the matching xover file.
First find the GID value, the number is shown in the 'showgroups' command
it's the second number in square brackets:
D:\dnews\work>tellnews showgroups nl.hobby.verzamel.postzegels
...
[6077:7078] nl.hobby.verzamel.postzegels start=9765 end=9764
items=0, upto on feed 0, days 0 Pile 0 1
..
Then delete that xover file.
del \dnews\xover\x_7078.xov
The stop/start dnews and check if the group still shows corrupt items.
If that doesn't fix it then you need to do a
tellnews rebuild_piles
Neither rebuild_piles or rebuid_index reset item numbers, they do both make
items dissappear briefly so you need
to run it last thing at night or at some time when users won't be using the
system if at all possible.
And to fix the original problem, I would have recommended
tellnews cached nl.hobby.verzamel.postzegel 99
tellnews getold nl.hobby.verzamel.postzegel 1000
tellnews updateone cached nl.hobby.verzamel.postzegel
That would reset it in every way possible.
ChrisP.
