Installing Arla on FreeBSD 2.2.6

[Prashant Chandra]

Hi!
  Thanks for your reply.  Yes, I did have arlad running when
I got this error loop.  I basically ran the script startarla
which is shown below:

glenwood# more startarla 
#!/bin/sh
#
# A simple startupscript to start arla for *BSD.
# 
# You must have a path that includes, modload, ld, 
# mount_xfs, and arlad.
#
# $Id: startarla.in,v 1.5 1998/07/29 20:28:27 assar Exp $
#


PATH="/sbin:/usr/sbin:/usr/bin:/bin:/usr/arla/bin"
BINDIR=/usr/arla/bin
CACHEDIR=/usr/arla/cache

if [ ! -d $CACHEDIR ] ; then
   mkdir $CACHEDIR
   chmod 700 $CACHEDIR
   chown root $CACHEDIR
fi

modload -e xfs_mod -o /var/tmp/foo -p $BINDIR/xfs_makedev
$BINDIR/xfs_mod.o 
mount_xfs /dev/xfs0 /afs
arlad /dev/xfs0

As you suggested, I tried arlad by hand with the parameters
suggested by you and got the following loop when I tried to
do 'cd /afs/cs/usr/prashant'.  The messages are output of
arlad

glenwood# arlad -z -n --debug=all,-cleaner
Wed Oct 21 23:49:10 1998: arlad: read_conffile: /usr/arla/etc/arla.conf
Wed Oct 21 23:49:10 1998: arlad: Arlad booting sequence:
Wed Oct 21 23:49:10 1998: arlad: connected mode: connected
Wed Oct 21 23:49:10 1998: arlad: initports
Wed Oct 21 23:49:10 1998: arlad: conn_init numconns = 100
Wed Oct 21 23:49:10 1998: arlad: initconncache
Wed Oct 21 23:49:10 1998: arlad: cellcache
Wed Oct 21 23:49:10 1998: arlad: fprio
Wed Oct 21 23:49:10 1998: arlad: fprio_readin: cant open file
/usr/arla/cache/fprio: Operation not permitted
Wed Oct 21 23:49:10 1998: arlad: volcache numvols = 100
Wed Oct 21 23:49:10 1998: arlad: rx
Wed Oct 21 23:49:10 1998: arlad: using rxkad level auth
Wed Oct 21 23:49:10 1998: arlad: credcache numcreds = 100
Wed Oct 21 23:49:10 1998: arlad: fcache low_vnodes = 3000, high_vnodes =
4000low_bytes = 94371840, high_bytes = 104857600
Wed Oct 21 23:49:10 1998: arlad: cmcb
Wed Oct 21 23:49:10 1998: arlad: cm
Wed Oct 21 23:49:10 1998: arlad: arla init done.
Wed Oct 21 23:49:10 1998: arlad: pre-creating nodes
Wed Oct 21 23:49:10 1998: arlad: Arla: selecting on fd: 5
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 2 (getroot), size
= 20
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 3 (installroot),
size = 120
Wed Oct 21 23:49:44 1998: arlad: multi-sending wakeup: seq = 1445, error
= 0
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 4 (getnode), size
= 292
Wed Oct 21 23:49:44 1998: arlad: read_data
Wed Oct 21 23:49:44 1998: arlad: read_data
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 5 (installnode),
size = 392
Wed Oct 21 23:49:44 1998: arlad: multi-sending wakeup: seq = 1446, error
= 0
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 10
(inactivenode), size = 32
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 8 (getdata), size
= 40
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 9 (installdata),
size = 452
Wed Oct 21 23:49:44 1998: arlad: multi-sending wakeup: seq = 1448, error
= 0
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 8 (getdata), size
= 40
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 9 (installdata),
size = 452
Wed Oct 21 23:49:44 1998: arlad: multi-sending wakeup: seq = 1449, error
= 0
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 8 (getdata), size
= 40
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 9 (installdata),
size = 452
Wed Oct 21 23:49:44 1998: arlad: multi-sending wakeup: seq = 1450, error
= 0
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 8 (getdata), size
= 40
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 9 (installdata),
size = 452
Wed Oct 21 23:49:44 1998: arlad: multi-sending wakeup: seq = 1451, error
= 0
Wed Oct 21 23:49:44 1998: arlad: Rec message: opcode = 8 (getdata), size
= 40
Wed Oct 21 23:49:44 1998: arlad: Multi-send: opcode = 9 (installdata),
size = 452

... repeates infinitely.

Do you see what is wrong?  With respect to kerberos, the
configure script detected it and included it automatically
as you said.

Another interesting thing is if I run arlad with the -t option,
then I can do 'cd /afs/cs/usr/prashant' at the arla> prompt
and do an ls and see my files.  It seems like arlad -t works
correctly.

I would appreciate your help.
  Thanks.
    -prashant

-- 
____________________________________________________
e-mail: prashant at cs.cmu.edu
Web: http://www.cs.cmu.edu/~prashant
Phone: 412-268-2580 (Office)
       412-268-7560 (Lab)
       412-681-3829 (Home)
____________________________________________________


Love wrote:
> 
> Prashant Chandra <prashant at cs.cmu.edu> writes:
> 
> >   I am new to Arla.  I got version 0.13 and was able to
> > compile and install it without any problem on a
> > FreeBSD 2.2.6 machine.  I ran the script startarla to
> > modload the kernel module and start the arla daemon.
> > However when I tried to ls /afs or my AFS directory
> > in the CMU CS cell, the system went into a loop printing
> > out the following messages on the console:
> 
> Do you have a runnin arlad ? Try running arlad by hand with
>     /usr/arla/bin/arlad -z -n --debug=all,-cleaner
> (don't use old cache, dont fork, output some error messages) and see if
> that give you any clues what is wrong.
> 
> > XFS PANIC WARNING! xfs_message_installdata failed!
> > Reason: lookup failed on cache file <filename>, error = 6
> >
> > Error 6 corresponds to "Device not configured". What have
> 
> You can also change the x to X in xfs/bsd/xfs_deb.c to
> get more xfs debugging.
> 
> > I done wrong?  Also, the FreeBSD machine has kerberos.  How
> > do I setup arla to use kerberos authentication?
> 
> If configure finds kerberos (that it should do), there is no configuration.
> You can turn on encryption with `fs setcrypt on'.  Too push tokens to arla
> use tramsarc's aklog or kth-krb <ftp://ftp.nada.kth.se/pub/krb/> afslog.
> 
> Love