I seem to be getting a lot more of these recently. My solution was to
run rebuild -s to fix the database, reset all history and overview
files (I think). Of course, you need at least 2X the size of your
news spool to do this. This may be overkill, but it will take care of
any problems you may be having. In my case, the error soon brought on
attribution errors in import, which is why I did the -s rebuild. I
got my problem with too little disk space on a souper download, then
trying to import that packet without checking.
-- ============================================================================= * LabRat@i-link.net * Just because you're paranoid doesn't * * Michael.Gray@1201.ima.infomail.com * mean they're not out to get you * ============================================================================= No person should govern another without their permission.