I just installed CODA for the first time on 2 linux systems running the 2.4.20 kernel..
On the client-only system, I have a problem with venus dying a SEGV death as soon as I try to do a 'cfs sa'..
$ cfs sa /coda mathias all 17:32:12 Fatal Signal (11); pid 26562 becoming a zombie... 17:32:12 You may use gdb to attach to 26562
The traceback from gdb is as follows:
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_db.so.2...done.
Loaded symbols for /lib/libnss_db.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libdb-3.1.so...done.
Loaded symbols for /lib/libdb-3.1.so
Reading symbols from /lib/libnss_dns.so.2...done.
Loaded symbols for /lib/libnss_dns.so.2
0x401eb469 in __sigsuspend (set=0x151ae764) at ../sysdeps/unix/sysv/linux/sigsuspend.c:54
54 ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory.
(gdb) bt
#0 0x401eb469 in __sigsuspend (set=0x151ae764) at ../sysdeps/unix/sysv/linux/sigsuspend.c:54
#1 0x80aedd0 in SigChoke (sig=11) at sighand.cc:241
#2 <signal handler called>
#3 0x804da99 in srvent::GetConn (this=0x0, cpp=0x151aec48, uid=0, Force=0) at comm.cc:212
#4 0x808f006 in volrep::GetConn (this=0x50222dc8, c=0x151aec48, uid=0) at venusvol.cc:1945
#5 0x80628fa in fsobj::ConnectedSetAttr (this=0x5021d9c8, Mtime=1066210332, uid=0, NewLength=4294967295, NewDate=4294967295,
NewOwner=4294967295, NewMode=65535, acl=0x151afa60) at fso_cfscalls0.cc:1609
#6 0x806362d in fsobj::SetAttr (this=0x5021d9c8, vap=0x151af918, uid=0, acl=0x151afa60) at fso_cfscalls0.cc:1738
#7 0x80636ec in fsobj::SetACL (this=0x5021d9c8, acl=0x151afa60, uid=0) at fso_cfscalls0.cc:1761
#8 0x80a6521 in vproc::do_ioctl (this=0x812ae60, fid=0x151b1e24, com=1074550273, data=0x151afe04) at vproc_pioctl.cc:130
#9 0x80a9333 in vproc::ioctl (this=0x812ae60, cp=0x151b1e20, com=1074550273, data=0x151afe04, flags=0) at vproc_vfscalls.cc:296
#10 0x80ada0d in worker::main (this=0x812ae60) at worker.cc:1244
#11 0x80a44e2 in VprocPreamble (init_lock=0x812aea0) at vproc.cc:146
#12 0x40086fcf in Create_Process_Part2 () at lwp.c:796
Current language: auto; currently c
(gdb)
I used the following: coda-6.0.2.tar.gz lwp-1.10.tar.gz pscope-2.1.1.tgz rpc2-1.19.tar.gz rpc2tcpdump-1.1.tgz rvm-1.8.tar.gz
and each compiled out of the box w/a simple configure;make;make install sequence..
(I did patch the kernel using the 2.4 patch provided and rebuilt the module..)
Is this too near the bleeding edge?
Is there a more stable version I should be using instead?
thanks for any help
Mathias K�rber [EMAIL PROTECTED]
