[1018] in arla-drinkers
Re: Error 'Software caused connection abort' in arla 0.26 and 0.25
daemon@ATHENA.MIT.EDU (Dr A V Le Blanc)
Mon Jul 26 06:31:41 1999
From owner-arla-drinkers@stacken.kth.se Mon Jul 26 10:31:36 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 17059 invoked from network); 26 Jul 1999 10:31:31 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 26 Jul 1999 10:31:31 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id MAA27709
for arla-drinkers-list; Mon, 26 Jul 1999 12:24:57 +0200 (MET DST)
Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id MAA27705;
Mon, 26 Jul 1999 12:24:51 +0200 (MET DST)
Received: from meissen.mcc.ac.uk ([130.88.203.42])
by probity.mcc.ac.uk with esmtp (Exim 1.92 #3)
id 118hwB-000JCP-00; Mon, 26 Jul 1999 11:24:51 +0100
Received: (from zlsiial@localhost)
by meissen.mcc.ac.uk (8.7.6/8.8.4)
id LAA15292; Mon, 26 Jul 1999 11:24:50 +0100 (BST)
Message-ID: <19990726112450.A15286@afs.mcc.ac.uk>
Date: Mon, 26 Jul 1999 11:24:50 +0100
From: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
To: Assar Westerlund <assar@stacken.kth.se>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: Error 'Software caused connection abort' in arla 0.26 and 0.25
Reply-To: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
References: <19990724144334.E14371@afs.mcc.ac.uk> <5l7lnq6srs.fsf@assaris.sics.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <5l7lnq6srs.fsf@assaris.sics.se>; from Assar Westerlund on Sat, Jul 24, 1999 at 04:12:39PM +0200
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
On Sat, Jul 24, 1999 at 04:12:39PM +0200, Assar Westerlund wrote:
> 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.
OK, I've had the error occur while 'fs arladebug all'. There
don't seem to be any errors in syslog; where should they be?
The log file in the cache is empty as well.
-- Owen
LeBlanc@mcc.ac.uk
