Version 6.41 B4 - Bogus MaxSpool
Posted: Wed Dec 12, 2012 12:03 pm
As I usually do each night, last night I left Newsbin Version 6, B4 Build 2120 downloading the latest group updates before going to bed.
This morning I found Newsbin still running (My computer usually shuts down after Newsbin finishes the nightly update) and incessantly writing of the error message, "ERROR - Server:GiganewsServer Reports bogus MaxSpool > MaxGroup Numbers :84169360:122870964 - alt.binaries.hdtv.repost." It seems that after completed the downloading of the latest group updates from all of the other newsgroups to which I'm subscribed to, it spent the rest of the night reporting that error over, and over again.
I deleted all stored posts for the specified newsgroup, and then successfully downloaded all headers for that group without that error message being written. But when I then ran "download latest" for that group, Newsbin began writing another string of entries for that same error.
Questions:
1. What is causing that error?
2. why does Newsbin continue to report an error that obviously isn't going away.
3. What is the cure for that error?
4. If the problem is with Giganews, what problem is it that I'd be reporting?
Thank you, and thank you for Newsbin.
This morning I found Newsbin still running (My computer usually shuts down after Newsbin finishes the nightly update) and incessantly writing of the error message, "ERROR - Server:GiganewsServer Reports bogus MaxSpool > MaxGroup Numbers :84169360:122870964 - alt.binaries.hdtv.repost." It seems that after completed the downloading of the latest group updates from all of the other newsgroups to which I'm subscribed to, it spent the rest of the night reporting that error over, and over again.
I deleted all stored posts for the specified newsgroup, and then successfully downloaded all headers for that group without that error message being written. But when I then ran "download latest" for that group, Newsbin began writing another string of entries for that same error.
Questions:
1. What is causing that error?
2. why does Newsbin continue to report an error that obviously isn't going away.
3. What is the cure for that error?
4. If the problem is with Giganews, what problem is it that I'd be reporting?
Thank you, and thank you for Newsbin.