[OpenAFS] vos create [...] stuck

[Kevin Coffman]

>From your 'bos status' output, you are not running a ptserver.  Also 
notice the "Couldn't get CPS for AnyUser ..." error message.  This is 
the fileserver trying to talk to the ptserver.

> hi,
> 
> i am still (*) trying to get OpenAFS working here. this time i'm using 
> the MIT version of kerberos5 (not heimdal-kerberos), closesly following 
> the intructions from http://www.scode.org/afs/openafs-install.txt.
> 
> i was able to create admin users via pts and starting fs instances
> fileserver, volserver, salvager, vlserver via bos.
> 
> /vicepa is an mounted ext3 image-file (loopdevice)
> 
> now i wanted to create the root AFS volume with
> 
> 
> $  vos create -server mud -partition /vicepa -name root.afs \
>          -cell housecafe.de -noauth
> 
> but the command does not return. it is *not* eating up cpu cycles, it's 
> just stuck. i could interrupt it with CTRL-C. an strace bound to this 
> vos process gives:
> 
> ----------------------
> ) = 0
> gettimeofday({1041661804, 500537}, NULL) = 0
> getitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={21474832, 
> 190000}}) = 0
> sendmsg(3, {msg_name(16)={sin_family=AF_INET, sin_port=htons(7005), 
> sin_addr=inet_addr("192.168.1.2")}}, 
> msg_iov(2)=[{">\26\177h\370W\376\344\0\0\0\1\0\0\0\1\0\0\0\3\1\7\0\0"..., 
> 28}, {"\0\0\0\177", 4}], msg_controllen=0, msg_flags=0}, 0) = 32
> gettimeofday({1041661804, 502862}, NULL) = 0
> _newselect(0x4, 0x1006f8e0, 0, 0, 0x1006cab8 <unfinished ...>
> ----------------------
> 
> (the returned ip-address is correct for "mud")
> 
> sometimes i get error messages. on the console:
> 
> ------
> FSYNC_clientInit temporary failure (will retry): Connection refused
> ------
> 
> this could be normal, as i've seen in a report (google helps) because it 
> will retry. this message repeats 5 times, then i get:
> 
> ------
> FSYNC_clientInit failed (giving up!): Connection refused
> ------
> 
> ...which does not look that good any more.
> after starting the server instances via bos, the salvager exits with 
> code 0, /var/log/openafs/SalvageLog gives:
> ------
> @(#) OpenAFS 1.2.7 built  2002-10-21
> 01/04/2003 06:47:36 STARTING AFS SALVAGER 2.4 (/usr/lib/openafs/salvager)
> 01/04/2003 06:47:36 Starting salvage of file system partition /vicepa
> 01/04/2003 06:47:36 SALVAGING FILE SYSTEM PARTITION /vicepa (device=vicepa)
> 01/04/2003 06:47:36 ***Forced salvage of all volumes on this partition***
> 01/04/2003 06:47:36 No vice inodes on vicepa; not salvaged
> Temporary file /vicepa/salvage.inodes.vicepa.9065 is missing...
> ------
> 
> sometimes, FileLog gives:
> ------
> Couldn't get CPS for AnyUser, will try again in 30 seconds; code=5389.
> ------
> 
> so, could someone please give me a hint where to look at again? what 
> have i missed?
> 
> the salvager logfile states correct, that there is no such file. but 
> shouldn't have one of the server instances created these file(s) by itsself?
> also, this error in FileLog should only show up, when fileserver could 
> not contact the ptserver (as seen on previous posts on openafs-info).
> 
> but both instances are on the same machine, the hostname is not even a 
> CNAME but an A record. bosserver is still running in -noauth mode, so it 
> should not be a permission issue.
> yes, i restarted the instances via
> 
> -----
> bos restart mud -all -cell housecafe.de -noauth
> -----
> 
> too. a status query gives:
> -----
> root@mud:/etc/openafs# bos status mud fs -long -noauth
> Instance fs, (type is fs) currently running normally.
>      Auxiliary status is: file server running.
>      Process last started at Sat Jan  4 07:31:33 2003 (17 proc starts)
>      Last exit at Sat Jan  4 07:31:33 2003
>      Last error exit at Sat Jan  4 07:31:33 2003, by vol, by exiting 
> with code 1
>      Command 1 is '/usr/lib/openafs/fileserver'
>      Command 2 is '/usr/lib/openafs/volserver'
>      Command 3 is '/usr/lib/openafs/salvager'
>      Command 4 is '/usr/lib/openafs/vlserver'
> -----
> (now, volserver is up and running)
> 
> 
> i'm using linux-2.4.20 (with openafs-1.2.7 patches applied) on 
> Debian/Testing (PPC). OpenAFS tools are version 1.2.7 too.
> sure, further information is available.
> 
> Thank you for your time to respond,
> Christian.
> 
> 
> 
> (*) mainly to Peter Schuller:
> oh, well, i've really overseen your reply (" Re: [OpenAFS] afsd dead / 
> weird config). it was in a different mail folder of mine. i have not 
> worked on afs for weeks now, but now i try again. see above.
> -- 
> c_kujau@web.de
> 
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>