CellServDB does contain my cell information. ThisCell does point to my cell. This installation is meant to be client-only - do I have to create a root.afs volume on it? My other cell (on a debian machine) works fine, and I'm pointing this client at it.
--pj On Wednesday, Mar 26, 2003, Derek Atkins writes: >Does the CellServDB contain your cell information? Does ThisCell point >to your cell? Did you create the root.afs volume in your cell? > >-derek > >Paul Jimenez <[EMAIL PROTECTED]> writes: > >> More info: >> >> After I do /etc/init.d/afs start, it not only fails to mount anything >> under /afs, but I get a bunch of processes: >> >> 920 ? SW 0:00 [afs_rxlistener] >> 921 ? SW 0:00 [afs_callback] >> 922 ? SW 0:00 [afs_rxevent] >> 923 ? SW 0:00 [afsd] >> 927 ? SW 0:00 [afs_checkserver] >> 928 ? SW 0:00 [afs_background] >> 929 ? SW 0:00 [afs_background] >> 931 ? SW 0:00 [afs_background] >> 933 ? SW 0:00 [afs_cachetrim] >> >> ...which end up being unkillable. /etc/init.d/afs stop doesn't work, >> neither does kill or kill -9. >> >> /etc/init.d/afs stop in fact results in a kernel Oops: >> >> Unable to handle kernel paging request at virtual address e08e88a8 >> printing eip: >> e08e88a8 >> *pde = 0167c067 >> *pte = 00000000 >> Oops: 0000 >> CPU: 0 >> EIP: 0010:[<e08e88a8>] Not tainted >> EFLAGS: 00010256 >> eax: 00000000 ebx: de6ae000 ecx: de6afee4 edx: 00000000 >> esi: de756ea0 edi: 00000000 ebp: 00000033 esp: de6aff14 >> ds: 0018 es: 0018 ss: 0018 >> Process afs_rxevent (pid: 922, stackpage=de6af000) >> Stack: c011c172 de752000 00000046 00000000 00000000 de6ae000 00000000 0 >0000000 >> 00000000 de6ae000 de6abf2c de756eb4 de6ae000 e0910a00 dfe4d734 3 >e821abb >> de6ae000 00000000 000001f4 e08e842c e09110c0 000001f4 00000000 0 >0000020 >> Call Trace: [<c011c172>] [<c01072b6>] >> >> Code: Bad EIP value. >> <1>Unable to handle kernel paging request at virtual address e08e88a8 >> printing eip: >> e08e88a8 >> *pde = 0167c067 >> *pte = 00000000 >> Oops: 0000 >> CPU: 0 >> EIP: 0010:[<e08e88a8>] Not tainted >> EFLAGS: 00010256 >> eax: 00000000 ebx: de6aa000 ecx: de6abed4 edx: 00000000 >> esi: de756ea0 edi: 00000000 ebp: 00000725 esp: de6abf04 >> ds: 0018 es: 0018 ss: 0018 >> Process afsd (pid: 923, stackpage=de6ab000) >> Stack: 00000000 00000000 00000000 00000000 00000000 de6aa000 00000000 0 >0000000 >> 00000000 de6aa000 de781f5c de6aff3c de6abf4c 00000000 00000000 3 >e821abd >> de6aa000 e090877c 0000476d e08e842c e09110c0 0000476d 00000000 0 >0000492 >> Call Trace: [<c01072b6>] >> >> Code: Bad EIP value. >> >> >> this strikes me as... bad. Anyone have any suggestions? >> >> --pj >> >> >> On Wednesday, Mar 26, 2003, Paul Jimenez writes: >> > >> > >> >Hi all, I'm trying to get AFS going on a redhat 7.2 box, so I'm >> >using a stock 2.4.20 kernel and openafs-1.2.8. I built things >> >up from scratch and still get: >> > >> >afsd: All AFS daemons started. >> >afsd: Forking trunc-cache daemon. >> >afsd: Mounting the AFS root on '/afs', flags: 0. >> >afsd: Can't mount AFS on /afs(22) >> > >> >when I do /etc/init.d/afs start >> > >> >Any ideas? >> > >> > --pj >> > >> >_______________________________________________ >> >OpenAFS-info mailing list >> >[EMAIL PROTECTED] >> >https://lists.openafs.org/mailman/listinfo/openafs-info >> > >> _______________________________________________ >> OpenAFS-info mailing list >> [EMAIL PROTECTED] >> https://lists.openafs.org/mailman/listinfo/openafs-info > >-- > Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory > Member, MIT Student Information Processing Board (SIPB) > URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH > [EMAIL PROTECTED] PGP key available > _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
