Possible reason for "rnews: cant unspool"?

Jeffrey M.Vinocur jeff at litech.org
Sun Apr 10 16:53:52 UTC 2005

On Apr 8, 2005, at 11:57 AM, Felix E. Klee wrote:

> At Fri, 8 Apr 2005 16:13:31 +0200,
> Paul Marques Mota wrote:
>> Apr  7 22:32:29 genba rnews: unknown_reply after article 400 loadav
>> [innwatch:load] 1977 gt 1500
> I still wonder what is the origin of the problem.  Surely load was 
> high,
> but that's no reason for messages to end up in "incoming/bad".

Yeah...unfortunately, a 400 response is what the server falls back to 
when some unusual happens, and in general the client is unlikely to be 
able to decipher the plaintext message explaining what the problem is.  
If the client has a queue/retry mechanism it could reasonably try again 
later, but for something like rnews, it's hard to see what option the 
client has other than to die.

Jeffrey M. Vinocur
jeff at litech.org

More information about the inn-workers mailing list