[OpenAFS] unable to start afs client

Horst Birthelmer hbi@sysgo.com
Tue, 30 Nov 2004 13:35:40 +0100


On Nov 30, 2004, at 1:25 PM, vinod kumar boppana wrote:

>  hello all,
>
>  i am getting problem with afs client on red hat linux 8.0 (kernel=20
> version is 2.4.18-14) .
>
>  when i run 'service afs start ' with server and client option " ON "=20=

> in
>  " /etc/sysconfig/afs " , the command getting hanged.
>
>  it only starting server and unable to start the client.
>
>  the output is : afs lost contact with file server ( all multihome ip=20=

> address down for server).
>
>  but i can ping the server with its ip address and so its network is=20=

> working perfectly.
>
>  i also did the following.
>
>  1. i started the server part with " service afs start " by having=20
> only server option "ON" in " /etc/sysconfig/afs " file.
>
>  2. then i used " /usr/vice/etc/afsd -debug -verbose' , it is giving=20=

> the following output.
>
>  afsd: My home cell is 'afs.compunet.barc.in'
>  ParseCacheInfoFile: Opening cache info file=20
> '/usr/vice/etc/cacheinfo'...
>  ParseCacheInfoFile: Cache info file successfully parsed:
>  =A0 =A0 =A0 =A0 cacheMountDir: '/afs'
>  =A0 =A0 =A0 cacheBaseDir: '/usr/vice/cache'
>  =A0 =A0 =A0 =A0 cacheBlocks: 20000
>  afsd: 2000 inode_for_V entries at 0x8075078, 8000 bytes
>  SScall(137, 28, 17)=3D-1 afsd: Forking rx listener daemon.
>  afsd: Forking rx callback listener.
>  afsd: Forking rxevent daemon.
>  SScall(137, 28, 48)=3D-1 SScall(137, 28, 0)=3D-1 SScall(137, 28, =
36)=3D-1
>

Yes, you can't launch even one AFS syscall. This means you either have=20=

not loaded the kernel module or your kernel module doesn't work with=20
your kernel for whatever reason.

Horst