Usenet Explorer

The group froze, the last headers I could get are from March, 21. I'm using UsenetServer. I'm still able to find and download later posts using search. What is going on?

i know, someone already asked me through contact form.

it has nothing to do with UE. highwinds have a problem similar to year 2000 bug.

the article number in boneless in their server article numbering crossed maximal positive 4 byte integer 2147483647 and somehow their server stuck as to this group. not only UNS is affected but also some other providers.

i've checked it now, it appears the article count in this newsgroup started anew

Server: news.usenetserver.com
alt.binaries.boneless:
Server: Range: 633794-641986 Num.articles 8193

so then you could reset header range for the server (expand the server in the workspace, select boneless group, context menu->advanced->reset header range), but it appears the problem is still there, when i'm trying to get those headers again it still shows 8193 headers with the header same range, so most likely the problem has not been fixed and it is just weird behaviour.

i notified UNS several days ago when i was informed about the issue and they confirmed they got my message:

"We are investigating this issue now."

and this is more detailed reply from another provider:

"Thanks for pointing this out to us. Unfortunately it seems the whole
boneless overview got corrupted, even on our new 64bit code which
shouldnt have this problem. After a few days between the 20th and last
night it seems it started running again last night, but instead of a
counter rollover it started again at article number 8000000 or so."

so the current small article number is the same sporadic counter rollover which is mentioned in the latter reply and not a fix.

all boneless group article bodies on affected news servers are still accessible by message-id even if you cannot get headers in the group - so accessible through search or nzb, it appears only the newsgroup article number overview is corrupt.

search service itself is unaffected since i'm using other source for that group which still works, but probably the same server build, just the article number has 120M more to go, until then they will fix it or i can find other working feeds, i'll keep an eye...

i talked to their support yesterday, apparently they were thinking they fixed it.

today, i see, they also announced the problem on their network status page, but the message implies other groups are affected as well which is probably not true. anyway if they recognized this issue - it is going to be resolved soon.