[1019] 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 09:36:40 1999
From owner-arla-drinkers@stacken.kth.se Mon Jul 26 13:36:40 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 17732 invoked from network); 26 Jul 1999 13:36:39 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 26 Jul 1999 13:36:39 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id PAA01914
for arla-drinkers-list; Mon, 26 Jul 1999 15:30:52 +0200 (MET DST)
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id PAA01909;
Mon, 26 Jul 1999 15:30:46 +0200 (MET DST)
Received: from meissen.mcc.ac.uk ([130.88.203.42])
by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
id 118kq5-000LRk-00; Mon, 26 Jul 1999 14:30:45 +0100
Received: (from zlsiial@localhost)
by meissen.mcc.ac.uk (8.7.6/8.8.4)
id OAA15396; Mon, 26 Jul 1999 14:30:45 +0100 (BST)
Message-ID: <19990726143044.A15384@afs.mcc.ac.uk>
Date: Mon, 26 Jul 1999 14:30:45 +0100
From: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
To: arla-drinkers@stacken.kth.se
Cc: Assar Westerlund <assar@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> <19990726112450.A15286@afs.mcc.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <19990726112450.A15286@afs.mcc.ac.uk>; from Dr A V Le Blanc on Mon, Jul 26, 1999 at 11:24:50AM +0100
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
On Mon, Jul 26, 1999 at 11:24:50AM +0100, Dr A V Le Blanc wrote:
> 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.
Actually, I should have said that there are some things in syslog
that might be related:
begin 444 syslog.tgz
M'XL(`'Y@G#<"`^W1S4Z#0!``8,X^Q1S;I$UF%A8HB2_@48_&F!76AA19W`6;
M^O0N56-C&JG&$DWGNQ!@=O[6;5QEEL%1$6*,"`'T/C\!PE!(@#B)$A]&$0$0
M1H@!8#""SK7*`@36F/:KN*'__]1%5X&(@2@CF442U%.%H&REKDE(O,G`=G5=
MUDO(*ZUJ;3-8$$Q"1)S[.\(IW)>5=C,@&88IIC!91&%":81S?XFI3.(^YF[3
M:G<V6.JM!!2FUK]51XXWDAQEI#C#L4;:7^H8(]%X(]%((XD]==;&KGP9S*"Q
M)M?.^?F&3UWJ'!Y\L%KZYDR3FT+#.0@!DZ8T>5M-9^#*Y^TW7,3#^9RNBWZQ
M:[727=._/_JS)"F:@;;6V&WVX3Q7/L^>QOSV7C/O]O6=W?2W<'B\'Z-L#]KC
M']^^_-@^_GCY(GS?_FVA6K7;7").YA("QAACC#'&&&.,,<888XPQQAAC[+2\
)`%9(#3H`*```
`
end
The operative section of the log looks like this:
Jul 26 11:16:25 avl0 arla[1250]: worker 0: processing
Jul 26 11:16:25 avl0 arla[1250]: Rec message: opcode = 22 (pioctl), size = 2096
Jul 26 11:16:25 avl0 arla[1250]: sending wakeup: seq = 1514, error = 22
Jul 26 11:16:25 avl0 arla[1250]: Send message: opcode = 1 (wakeup), size = 20
Jul 26 11:16:25 avl0 arla[1250]: worker 0: done
Jul 26 11:16:25 avl0 arla[1250]: worker 0 waiting
Jul 26 11:16:25 avl0 arla[1250]: worker 0: processing
Jul 26 11:16:25 avl0 arla[1250]: Rec message: opcode = 22 (pioctl), size = 2096
Jul 26 11:16:25 avl0 arla[1250]: sending wakeup: seq = 1515, error = 0
Jul 26 11:16:25 avl0 arla[1250]: Send message: opcode = 23 (wakeup_data), size = 2072
Jul 26 11:16:25 avl0 arla[1250]: worker 0: done
Jul 26 11:16:25 avl0 arla[1250]: worker 0 waiting
Jul 26 11:16:25 avl0 arla[1250]: worker 0: processing
Jul 26 11:16:25 avl0 arla[1250]: Rec message: opcode = 22 (pioctl), size = 2096
As to Jeff's suggestion that the volume might have problems, I don't
know; it certainly seems that there was a problem the last time that
was released, but there are three successfully cloned ReadOnly replicas
of the volume.
We are trying to get rid of some of our outdated equipment, but it's
performing so badly at the moment that we can't get vos mov to work
reliably (yeuch!).
-- Owen
LeBlanc@mcc.ac.uk
