Coda File System

Re: unable to connect to internal server

From: Bradley W. Langhorst <>
Date: Mon, 24 Jul 2000 10:07:25 -0400
Jan Harkes wrote:
> On Sun, Jul 23, 2000 at 10:32:48PM -0400, Bradley W. Langhorst wrote:
> > I have a coda client on my laptop and
> > have no problem connecting to the
> > testserver at cmu.
> >
> > However when i set up a codaserver on
> > my local network i found that I am not able to connect.
> > my venus.conf file contain only two uncommented lines
> >
> > rootservers=""
> > cacheblocks="20000"
> It could be that `strange', your server, has a problem in /etc/hosts.
> To be precise, the following line:
> localhost
> Things go wrong because gethostbyname("") returns
> and this is then returned in the volume lookups (i.e. it is
> stored in the VRDB and VLDB files). The client is then able to find the
> volume, GetRootVolume and GetVolInfo succeed. But attaching to the
> volume fails, because it cannot reach a server at
> Jan
Sorry to be thick if I've got this all confused...
Seems to me that what should happen is that the client
successfully determines the IP address of the server by looking at the
hosts file (there is no local DNS).
the hosts file looks like this:	bwlnote	localhost.localdomain localhost
... strange

So why would the client be trying to reach a server at when it
knows that strange is the server and that its address is  

Maybe you had the "it" referring to the server trying to attach to the
volume.  If so why would it be looking up itself? Does it do a remote
procedure call on itself? I guess that would make some sense if it can't
tell whether or not it is the hosting server for the volume in
question.  I guess I'm going to have to break out the source here...

Incidentally, I've added bwlnote to strange's(server's) hosts file so it
can resolve This does produce one interesting new
behavior (I think we're getting to the root of the problem).  I now get

Coda Venus, version 5.3.8

Date: Mon 07/24/2000

09:51:58 /usr/coda/LOG setup for size 0x88008
09:51:58 /usr/coda/DATA initialized at size 0x220020
09:51:58 brain-wiping recoverable store
09:51:58 loading recoverable store
09:51:58 starting VSGDB scan
09:51:58 	0 vsg entries in table
09:51:58 	0 vsg entries on free-list
09:51:58 starting VDB scan
09:51:58 	1 vol entries in table (0 MLEs)
09:51:58 	0 vol entries on free-list (0 MLEs)
09:51:59 starting FSDB scan (833, 20000) (25, 75, 4)
09:51:59 	0 cache files in table (0 blocks)
09:51:59 	833 cache files on free-list
09:51:59 starting HDB scan
09:51:59 	0 hdb entries in table
09:51:59 	0 hdb entries on free-list
09:51:59 Kernel version ioctl failed.
09:51:59 Initial LRDB allocation
09:51:59 Getting Root Volume information...
09:52:14 GetRootVolume: can't get root volume name!
09:52:44 GetRootVolume: can't get root volume name!
09:53:14 GetRootVolume: can't get root volume name!
09:53:44 GetRootVolume: can't get root volume name!
09:54:14 GetRootVolume: can't get root volume name!
09:54:44 GetRootVolume: can't get root volume name!
09:55:14 GetRootVolume: can't get root volume name!
09:55:30 Venus starting...

from the console log before venus gets Killed.
The server's CPU utilization goes way up during this period 

Since it can' get the root volume name I looked the
/vice/vol subdir but both files there
P/vicepa Hstrange T3d3c3e F3d151e
WLanghorstHomeCoda.root.0 I1000001 H1 P/vicepa m0 M0 U2 W1000001
C397b75c0 D397b75c0 B0 A0
LanghorstHomeCoda.root 7f000000 1 1000001 0 0 0 0 0 0 0 E0000100
the remote/ directory contains a strange.list which is identical to the

The server logs look identical all that I can tell has changed is the
addition of the error messages giving me info on the failure to find
Volume name.

I saw Gus Scheidt's post about having trouble with RH6.2
I wonder if anyone else is successful in running a coda server on

Many thanks for your quick responses! We'll get this straightened out.

Bradley W. Langhorst
Scientific Programmer
Whitehead Institute - Center for Genome Research
tel:   617-252-1918
Received on 2000-07-24 10:11:36