[OpenAFS] buserver barfs on "localhost" installation

Michael Martinez MikeMartiz@mwmconsultants.com
Mon, 25 Feb 2002 07:37:02 -0500


You must have an active link carrier signal on the ethernet interface to run Open-AFS. Loopback addresses are excluded from consideration, so you cannot "trick" the system by using only a loopback interface.

Your eth0 link light, must be on.


---------- Original Message ----------------------------------
From: Ian D <ian@assv.net>
Date:  25 Feb 2002 00:00:13 +0100

>I'm trying to set up an AFS server on my laptop, just to try it
>out. When it comes to setting up the buserver, I get a bunch of the
>following messages:
>
>[root@barbarella afs]# bos create gurksallad.hemma.assv.net buserver
>simple /usr/afs/bin/buserver 
>bos: a pioctl failed (getting tickets)
>bos: running unauthenticated
>/usr/afs/bin/buserver: problems with host name Ubik init failed
>/usr/afs/bin/buserver: problems with host name Ubik init failed
>
>My machine's hostname is something different, but it's mapped to
>127.0.0.1 in my /etc/hosts. "gurksallad.hemma.assv.net" is a
>resolvable address, albeit on the loopback also. Adding this address
>to /etc/hosts doesn't help. Running with the machine's hostname
>doesn't work, neither localhost. Any ideas?
>
>
>-- 
>/Ian D
>ian@assv.net
>
>_______________________________________________
>OpenAFS-info mailing list
>OpenAFS-info@openafs.org
>https://lists.openafs.org/mailman/listinfo/openafs-info
>

--
Regards,

Michael Martinez
MWM Consultants
http://www.mwmconsultants.com
(718) 797-1575
--