cant store article: bogus Xref: header in INN 2.5 ?

[Matija Nalis]

On Thu, Sep 01, 2011 at 08:15:34PM +0200, Julien ÉLIE wrote:
> So, hmm...  Maybe you could upgrade your newsfeed server to 2.5.2-2~squeeze1;
> I bet it will directly solve the issue for your slave server :-)

I do understand that would be easier way out -- if your bet is correct, but as
I only have redundancy for xrefslave servers and not for the feeder, I'd very
much first like to test and then let users hammer those for at least a month
or two before trying to upgrade newsfeed (so I can fallback to 2.4.6 server if 
anything go wrong -- as I'm doing just now).

I guess I'm just not much of a betting man :-)

> Otherwise, you could patch your slave server with a pending patch I will post
> in my next message.

I'll try that, thanks. I hope your patch against 2.5.3 will apply against
Debians 2.5.2 source (we'll see soon, hopefully tommorow).

With the "bogus Xref: header" problem found, what still worries me is why
the server sometimes (but not always) decided to throttle with the
"Interrupted system call writing SMstore file -- throttling" in the same
second as "bogus Xref: header" hit?

More precisely, would fixing the "bogus Xref: header" also fix all cases
leading to server auto-throttling, or may there be there some other possibile
vectors for server to auto-throttle when receiving just one invalid article?


-- 
Opinions above are GNU-copylefted.