Re: [leafnode-list] Reloading old groups

[Matthias Andree <matthias.andree@xxxxxx>]

"John Carlyle-Clarke" <john.cc@xxxxxxxxxxxxxxxx> writes:

> I've just seen the reloading of old articles problem, once again on 
> the Borland server.  This is obviously suspicious, indicating that a 
> server problem is likely.  Running 2.0.0.alpha20050412a (unpatched).
>
> Here is some log:-
>
> May 11 23:00:01 pc69 fetchnews[27277]: newsgroups.borland.com: 
> connecting to port nntp
> May 11 23:00:12 pc69 fetchnews[27277]:   trying:    address 
> 207.105.83.66 port 119...
> May 11 23:00:15 pc69 fetchnews[27277]:   connected: address 
> 207.105.83.66 port 119.
> May 11 23:00:21 pc69 fetchnews[27277]: newsgroups.borland.com: 
> connected (200), banner: "200 Borland NNTP service: Posting allowed,  
> 5.7c2,, S0"
> May 11 23:00:25 pc69 fetchnews[27277]: newsgroups.borland.com: 
> checking for new newsgroups
> May 11 23:00:28 pc69 fetchnews[27277]: newsgroups.borland.com: found 
> 0 new newsgroups
> May 11 23:00:28 pc69 fetchnews[27277]: found 1 articles in 
> out.going.
> May 11 23:00:30 pc69 fetchnews[27277]: newsgroups.borland.com: 0 
> articles posted
> May 11 23:01:02 pc69 fetchnews[27277]: timeout reading.
> May 11 23:01:02 pc69 fetchnews[27277]: newsgroups.borland.com NNTP 
> server disconnected or timed out while waiting for response
> May 11 23:01:36 pc69 fetchnews[27277]: newsgroups.borland.com: 
> borland.public.delphi.activex.controls.writing last seen article was 
> 15477, server now has 12553 - 12552

OK, this was a leafnode bug. The upstream group was empty, and the
Borland server properly responds with 211 0 12553 12552 group.name
in this case, which leafnode did not detect. It looked at the "high"
number (the rightmost) rather than the article count to check it against
zero, and it also did not check "low > high", which is also an indicator
for an empty upstream group. So all this "last seen article was ...,
server now has ..., switched upstream servers for..." is bogus:

> May 11 23:01:36 pc69 fetchnews[27277]: newsgroups.borland.com: 
> switched upstream servers for 
> borland.public.delphi.activex.controls.writing? upstream bug? 15477 
>> 12552
> May 11 23:01:36 pc69 fetchnews[27277]: newsgroups.borland.com: 
> borland.public.delphi.activex.controls.writing: no new articles

...but leafnode finally got the clue.

> May 11 23:01:39 pc69 fetchnews[27277]: newsgroups.borland.com: 
> borland.public.delphi.com.activex.writing: no new articles

OK, this one was empty.

> May 11 23:01:41 pc69 fetchnews[27277]: 
> borland.public.delphi.com.interop.win32: considering 260 articles 
> 1399 - 1658, using XOVER
> May 11 23:01:47 pc69 fetchnews[27277]: Unknown reply to XOVER 
> command: 211 61 212 275 borland.public.delphi.com.interop.win32 
> selected

And for some reason, leafnode got a GROUP command reply in response to
XOVER. It got out of synch, for a reason I don't see.

> Do you want me to supply any other files?

Not yet. I have released 20050514a which fixes the empty group detection
as mentioned above, please install that version and report if there are
further problems with the server. If there are, please run with
debugmode=129 and send the log off-list. Note it may contains passwords,
better use "-S discussions.borland.com" to only contact that
passwordless server.

-- 
Matthias Andree
-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/