[OpenAFS] Fileserver process hung on startup

Derrick J Brashear shadow@dementia.org
Mon, 19 Apr 2004 10:52:38 -0400 (EDT)


On Fri, 16 Apr 2004, John Morris wrote:

> Isn't listening as in not on port 2040.
>
> Thanks for the clue.  Here's what I'm getting.

it's not getting that far. it can't talk to the vlserver, and so it never
gets as far as listening to the volserver.

is CellServDB right? is there a vlserver listening on the machine
CellServDB designates a db server? what does rxdebug (that machine) 7003
show?

> # gdb /usr/afs/bin/fileserver fileserver.core
> GNU gdb Red Hat Linux (5.2.1-4)
> [...]
> Core was generated by `/usr/afs/bin/fileserver'.
> [...]
> #0  0x4002528d in pthread_getconcurrency () from /lib/libpthread.so.0
> (gdb) bt
> #0  0x4002528d in pthread_getconcurrency () from /lib/libpthread.so.0
> #1  0x4002409d in longjmp () from /lib/libpthread.so.0
> #2  0x40020d88 in pthread_cond_wait () from /lib/libpthread.so.0
> #3  0x0809f4d6 in rxi_ReadProc ()
> #4  0x08091a9e in rx_EndCall ()
> #5  0x08065451 in VL_RegisterAddrs ()
> #6  0x08085246 in ubik_Call ()
> #7  0x0804cf88 in Do_VLRegisterRPC ()
> #8  0x0804d171 in InitVL ()
> #9  0x0804af6e in main ()
> #10 0x4009454d in __libc_start_main () from /lib/libc.so.6
> (gdb)
>
>
> # ps auxwwwe|grep fileserver | grep -v grep
> root      1157  0.0  0.6 11280 3536 ?        S<   18:31   0:00
> /usr/afs/bin/fil\eserver CONSOLE=/dev/console TERM=linux
> INIT_VERSION=sysvinit-2.84
> PATH=/sbin:/\usr/sbin:/bin:/usr/bin:/usr/X11R6/bin RUNLEVEL=3 runlevel=3
> PWD=/ LANG=en_US PR\EVLEVEL=N previous=N HOME=/ SHLVL=2
> LD_ASSUME_KERNEL=2.4.1 _=/usr/afs/bin/bosse\rver
>
>
> On Mon, 2004-04-12 at 13:56, Derrick J Brashear wrote:
> > On Sun, 11 Apr 2004, John Morris wrote:
> >
> > > Hey!  (Sorry for sending previous mails to you as well as the list,
> > > Derrick.)
> > >
> > > Well, after clearing up for almost two weeks, this problem is occurring
> > > again.  Fileserver isn't listening on 2040; probably in the middle of a
> >
> > isn't listening in the sense of stopped responding, or in the sense of no
> > open socket? if the former, get a core of the fileserver (gcore, or gdb
> > generate-core-file after attaching, and then detach) and see what the
> > fsync handler thread is doing.
> >
> >
> > _______________________________________________
> > OpenAFS-info mailing list
> > OpenAFS-info@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-info
>
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>