[1011] in arla-drinkers
Re: Error 'Software caused connection abort' in arla 0.26 and 0.25
daemon@ATHENA.MIT.EDU (Assar Westerlund)
Sat Jul 24 10:16:58 1999
From owner-arla-drinkers@stacken.kth.se Sat Jul 24 14:16:56 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 8071 invoked from network); 24 Jul 1999 14:16:55 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 24 Jul 1999 14:16:55 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id QAA11133
for arla-drinkers-list; Sat, 24 Jul 1999 16:12:12 +0200 (MET DST)
Received: from assaris.sics.se (assaris.sics.se [193.10.66.108])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id QAA11128
for <arla-drinkers@stacken.kth.se>; Sat, 24 Jul 1999 16:11:52 +0200 (MET DST)
Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id QAA76681; Sat, 24 Jul 1999 16:12:40 +0200 (CEST)
From: Assar Westerlund <assar@stacken.kth.se>
To: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: Error 'Software caused connection abort' in arla 0.26 and 0.25
References: <19990724144334.E14371@afs.mcc.ac.uk>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=US-ASCII
Date: 24 Jul 1999 16:12:39 +0200
In-Reply-To: Dr A V Le Blanc's message of "Sat, 24 Jul 1999 14:43:34 +0100"
Message-ID: <5l7lnq6srs.fsf@assaris.sics.se>
Lines: 17
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Dr A V Le Blanc <LeBlanc@mcc.ac.uk> writes:
> As you see, it takes about 10 seconds to work properly, and
> the first four times it fails with this funny error message.
> The message is not from anywhere in arla directly. The error
> number ECONNABORTED is defined in errno.h. This is on Linux
> 2.2.10 with arla 0.26, but also occured with 2.2.9 and 0.25.
As you saw yourself, there's nowhere in arla or xfs where ECONNABORTED
should be returned. And looking around int the Linux source it only
seems to happen in inet_accept and ip_fw_ctl, neither of which should
apply here. It could however, be a VNOVOL error that doesn't get
translated properly. Can you turn on arla debugging (with `fs
arladebug all') and then try accessing some file that gives you these
errors? That way we might be able to figure out where the error is
occuring.
/assar