[770] in arla-drinkers

home help back first fref pref prev next nref lref last post

arla hanging on freebsd 3.1-stable

daemon@ATHENA.MIT.EDU (Paul Ewing Jr.)
Wed Apr 21 12:50:50 1999

From owner-arla-drinkers@stacken.kth.se Wed Apr 21 16:50:50 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 29718 invoked from network); 21 Apr 1999 16:50:49 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 21 Apr 1999 16:50:49 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id SAA10381
	for arla-drinkers-list; Wed, 21 Apr 1999 18:41:31 +0200 (MET DST)
Received: from grey07.nada.kth.se (grey07.nada.kth.se [130.237.226.21])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id SAA10377
	for <arla-drinkers@stacken.kth.se>; Wed, 21 Apr 1999 18:41:28 +0200 (MET DST)
Received: (from d95-mah@localhost)
	by grey07.nada.kth.se (8.8.7/8.8.7) id SAA09608;
	Wed, 21 Apr 1999 18:41:27 +0200 (MET DST)
From: "Paul Ewing Jr." <ewing@ima.umn.edu>
Message-Id: <199904211628.LAA09387@purple.ima.umn.edu>
Subject: arla hanging on freebsd 3.1-stable
To: arla-drinkers@stacken.kth.se
Date: Wed, 21 Apr 1999 11:28:11 -0500 (CDT)
X-Mailer: ELM [version 2.4ME+ PL37 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Lines: 28
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk

I'm running Arla 0.23 with FreeBSD 3.1-STABLE.  I've been testing Arla
by configuring and compiling the Arla source in an AFS directory, and
I'm having a problem with random hangs.

It usually hangs while running configure.  Sometimes I can run it
serveral times in row without problems; other times it hangs on the
first attempt.  I can kill the configure process to get out of the
hang, but from then an `ls -l' in that directory hangs.  (Plain `ls'
doesn't, so it's likely a stat() call that's hanging.)  Everytime a
process hangs, another arlad worker is used up.  Eventually I run out
of workers.  Restarting arlad gets things working again.

Here is an excerpt from the arlad log.  These messages repeat over and
over:

Wed Apr 21 11:01:55 1999: arlad: worker 1: processing
Wed Apr 21 11:01:55 1999: arlad: Rec message: opcode = 22 (pioctl), size = 2096
Wed Apr 21 11:01:55 1999: arlad: sending wakeup: seq = 158114, error = 0
Wed Apr 21 11:01:55 1999: arlad: Send message: opcode = 23 (wakeup_data), size = 2072
Wed Apr 21 11:01:55 1999: arlad: worker 1: done

Any idea what might be causing this?

--
Paul J. Ewing Jr.
ewing@ima.umn.edu                            (612) 337-3530 (work)
http://www.ima.umn.edu/~ewing/               (612) 781-1160 (home)


home help back first fref pref prev next nref lref last post