[OpenAFS] fileserver almost crash
Matthew Cocker
matt@cs.auckland.ac.nz
Tue, 02 Nov 2004 15:05:08 +1300
Hi
We have had several cases of a fileserver stopping allowing access to
volumes. Nothing seems wrong from the logs but the only way to get
system on line again is to restart afs (sometimes linux reset required).
We attached to the process and core dumped (backtrace below) but I am
not sure we got what is needed.
This appears to be a different issue to the last signal 6 issue (most
windows clients are now updated)
Cheers
Matt
This GDB was configured as "i386-linux"...
Core was generated by `/usr/lib/openafs/fileserver'.
Program terminated with signal 17, Child status changed.
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
#0 0x400dbde1 in nanosleep () from /lib/libc.so.6
(gdb) bt
#0 0x400dbde1 in nanosleep () from /lib/libc.so.6
#1 0x400dbd78 in sleep () from /lib/libc.so.6
#2 0x0804b601 in HostCheckLWP () at ../viced/viced.c:726
#3 0x4001c0ba in pthread_start_thread () from /lib/libpthread.so.0