Version 6.41 B4 - Bogus MaxSpool

[Moondawgie]

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.

[kirm]

I was also having that same issue with newshosting. Tried everything that I could think of including deleting all db3 files. This was also reported earlier and it appears to be a server problem. I also deleted that particular group, all files pertaining to it, and still would get the same results as you have been getting.

I have not tried that group in over a week. Thought I would wait till things get corrected, however it appears that one particular group still has issues.

John K

[kirm]

Correction, my prob was with the main group, not the repost of same.

[dexter]

It's an issue with Giganews returning unexpected results. Newsbin keeps trying forever hoping the news server will recover and return the correct response. We could look into not having Newsbin try forever.

[Moondawgie]

It's an issue with Giganews returning unexpected results. Newsbin keeps trying forever hoping the news server will recover and return the correct response. We could look into not having Newsbin try forever.

That's seems to be about all that can done. Perhaps a notation, something like "Unexpected results from Server" could be written to the status area of the Downloading Files window?

Thank you.

[Quade]

Set a short download age, right click the group "Post Storage/Use Download age" to reset the group then "Download Latest" to clear the record. What dex explained is true but, sometime I think the range.db3 gets into a weird state.

[OMG2011]

Set a short download age, right click the group "Post Storage/Use Download age" to reset the group then "Download Latest" to clear the record. What dex explained is true but, sometime I think the range.db3 gets into a weird state.

Fixed it for me. But now i get "XOVER Data Corrupt: From Missing ....." errors all over those groups. (Giganews). Some wisdom about that?