newsbin.com

Not sure if I changed something or what but when I try to update the headers I cannot get anything newer than 8 days.

Please help.

Thnks

What server?
What version of Newsbin?
What group?

Same here. This seems to have started with 6.4x.
Just to try, I installed 6.1 again today and it runs right out of the box.

This is on both providers I use, newshosting and supernews.
The errors are always the same , some socket errors about unexpected responses.

I a few cases I could make it work with deleting a group and creating it again, but that is not consistent.

- Wolfgang

"some socket errors". It's about the details, otherwise nothing much to do. A socket error means either the server is having a problem, or something is getting between you and the server. As a guess, turn off any antivirus.

DT

[01:47:55] ERROR - Server:UseNetServerServer Reports bogus MaxGroup > MinSpool Groups numbers :30379:4323177 - alt.binaries.comics.dcp

If you're seeing something like this, right click the group, "Post Storage/Use Download Age" set something like a 10 day storage age then update the group. See what happens.

But my question is : Why is working 6.1 fine and 6.4 not ?

I am going to upgrade my current version to 6.4 again and let you know how it works.

- Wolfgang

I'm not having any problems with this in my groups. That's why I'm sort of puzzled.

Got a report of something like this for the group "asianusenet".

I pulled the raw headers for this group. Nothing has been posted to it since the 15th. It's been really sparse for the past 8 days. Looking at the RAW headers as downloaded off Giganews, the headers reflect exactly what Newsbin is showing. When I download raw headers, there is no filtering. It's read off the connection, then written to disk so, it's as the server delivers it. I believe that if there's a problem in this group, it's not a problem in Newsbin.

I took a look at "midnightmovies" another group with claimed issues. Nothing posted to it for the past 14 days. I looked at headers from Giga and from AW. They were identical.

After the upgrade to 6.4 it still worked as expected. I am happy again

- Wolfgang

Well, after a bunch of digging I found a bug. It'll be fixed in the next RC. I didn't see it before because it only applies to low traffic groups.

New version should be up before too long.