Re: Re: [ Article counter inconsistent ]

(Sorry about the delay getting back on this - work has been a bit pressing of
late...)

On 26-Sep-2003 Dan Jacobson wrote:
> sample of syslog:
> Getting remote overviews 233-676 for group gmane.emacs.bbdb.user
> Article number inconsistent (gmane.emacs.bugs rmt=1-1356, next=5850).
> Refetching from 913
> Getting remote overviews 913-1356 for group gmane.emacs.bugs
> 
> there must be a stage in the communication where if the remote
> connection drops, all counters for all the groups for that server are
> in danger all at once.

The next counter is updated at the end of (successful) processing each
downloaded group of overviews. Anyway, looking at gmane.emacs.bugs, the next
counter looks about right. The remote article range last counter looks
completely stuffed, though. That is read straight from the response to the
GROUP command. So, the question is did the Gmane INN server have a brainfart
and really return "211 13?? 1 1356" or did Noffle manage to mis-parse the
reply? The group reply line is

<status> <estimated articles in spool> <first article no> <last article no>

and currently we pay no attention to the estimated articles. I suppose we could
try checking (last - first) >= estimated, and log a warning if not. BTW,
news.gmane.org is currently saying 

group gmane.emacs.bugs
211 5819 1 5895 gmane.emacs.bugs

Unfortunately unless you were logging all the NNTP traffic there currently
isn't a log for what was actually read for the group first and last. How
frequently do you have this problem? Would it be possible for you to
pop 'log-debug protocol' into your noffle.conf until this happens again? This
will log all NNTP traffic so it will produce sizeable log files.

-- 
Jim Hague - [email protected]          Never trust a computer you can't lift.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf