Re: [ Article counter inconsistent ]

Jim> The next counter is the counter Noffle stored at the end of the previous fetch
Jim> as being the article number of the next article to fetch.

Jim> The inconsistency message is generated when "next > last + 1".

These days when running big downloads on my little modem, many
competing nntp connections might poop out.

well, ok, I' try connect-timeout 120 #was 60, but still, I have a
guess/feeling that noffle isn't doing enough to safeguard counter
integrity at each step of the game.

>>>>> ""[" == "[ NOFFLE ]" <news> writes:

"[> 	[ NOFFLE INFO: Article counter inconsistent ]

"[> 	[ This group's article counter is not  ]
"[> 	[ consistent Probably the remote news server ]
"[> 	[ was changed or has reset its article counter ]
"[> 	[ for this group. As a consequence there could ]

or more likely, last time our connection was dropped, and we threw
away what we knew[?]

"[> 	[ be some articles be duplicated in this group ]
"[> 	[ Group: gmane.network.noffle.user ]
"[> 	[ Remote first article number: 1 ]
"[> 	[ Remote last article number: 96 ]
"[> 	[ Remote next article number: 101 ]
"[> 	[ Refetching from article: 1 ]

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.


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