[EMAIL PROTECTED] wrote:
It sounds like the main index file was corrupted. I would try this:You've heard of Windows Annoyances? Well this tops my list of DNews Annoyances.
The server suffered a drive failure. The drive was replaced and the backups restored. DNews (Linux 5.7e1) was restarted, and it immediately trashed the /var/spool/dnews/xover files, causing the first article number to be incremented hugely. Now all those articles exist in the ~/spool directory, but nobody can read them.
Ordinarily, I'd try "tellnews rebuild_index" but I've been there and done that and it just does not work.
That's the main DNews Annoyance.
stop dnews
find active.mon or other old active.dat file with item numbers not too silly and copy it over the current active.dat
Then run a rebuild_index
ChrisP.
