Thank you for you previous help.  However, I am still experiencing the
same problems as before.  I tried some of your suggestions, and here is
what happened.

On Fri, 4 May 2001, Jan Harkes wrote:

> On Thu, May 03, 2001 at 07:34:59PM -0500, Ryan M. Lefever wrote:
> > 18:16:14 Getting Root Volume information...
> > 18:16:14 Venus starting...
> > 18:16:14 CHILD: mount system call failed. Killing parent.
> > 
> > Killed
> 
> There might be some more information in /usr/coda/etc/venus.log. But it
> is most likely a server problem, so check /vice/srv/SrvLog|SrvErr on the
> servers. It could be that the initial rootvolume doesn't exist, or has
> the wrong name, or the server hostnames don't resolve correctly, or...
> 

I am having problems getting the coda client to work.  I am still getting
the above messages when trying to connect to my own set of 3 servers.  
There is nothing in the SrvLog or SrvErr on the SCM from the point where I
try to start venus.  On the server running on the same machine as my
client, SrvLog contains this:

----------------
17:04:36 Building callback conn.
17:04:36 RevokeWBPermit on conn 35dd52b1 returned -2016
17:04:36 No idle WriteBack conns, building new one
17:04:36 Writeback message to 130.126.143.77 port 2430 on conn 25aadd28
succeeded
---------------

venus.log contains:

--------------------
[ X(00) : 0000 : 17:04:35 ] Coda Venus, version 5.3.13
[ X(00) : 0000 : 17:04:35 ] Logfile initialized with LogLevel = 0 at Tue
May  8 17:04:35 2001

...

[ X(00) : 0000 : 17:04:36 ] E adv_daemon::adv_daemon: AdviceServer    
[ A(17) : 0000 : 17:04:36 ] adv_daemon::main()
[ H(06) : 0000 : 17:04:36 ] HDBDaemon about to sleep on hdbdaemon_sync
[ X(00) : 0000 : 17:04:36 ] CHILD: mount system call failed. Killing
parent.
--------------------

I have definitely created the root volume:

--------------------
[root_at_nsx tmp]# createvol_rep coda.root E0000100 /vicepa
Servers are (nsx )
HexGroupId is 7f000004
creating volume coda.root.0 on nsx (partition /vicepa)
V_BindToServer: binding to host nsx.crhc.uiuc.edu
V_BindToServer: binding to host nsx.crhc.uiuc.edu
VolSetLogParms failed with Unknown RPC2 return code 103
Fetching volume lists from servers:
V_BindToServer: binding to host nsx.crhc.uiuc.edu
GetVolumeList finished successfully
 nsx - success
V_BindToServer: binding to host nsx.crhc.uiuc.edu
VLDB completed.
<echo coda.root 7f000004       1 50000005 0 0 0 0 0 0 0 E0000100 >>
/vice/db/VRList>
V_BindToServer: binding to host nsx.crhc.uiuc.edu
VRDB completed.
--------------------

So, I tried to turn the debugging level up on the SCM, and in addition to
killing the SCM, the following messages were output:

--------------------
[root_at_nsx /root]# volutil setdebug 100
V_BindToServer: binding to host nsx.crhc.uiuc.edu
VolSetDebug failed with RPC2_DEAD (F)
--------------------

I'm not sure if there is some process that I'm not running that's
suppossed to.  When I do a ps -e the following processes are listed:

--------------------
 1276 ?        00:00:00 auth2
 1278 ?        00:00:00 rpc2portmap
 1280 ?        00:00:03 updatesrv
 1282 ?        00:00:01 updateclnt
 2115 pts/0    00:00:00 startserver
 2119 ?        00:00:30 codasrv
--------------------

> > I am running Coda 5.3.13 on a Redhat 6.2 system (Linux 2.2).

As a side note, I compiled the server, client, and coda.o from source and
had them installed in "/usr/local/coda".  lwp, rpc2, and rvm were
installed from rpms.

> > I also tried to connnect to testserver.coda.cs.cmu.edu, and i get the
> > following:
> ...
> > 18:20:14 Getting Root Volume information...
> > 18:20:29 GetRootVolume: can't get root volume name!
> > 18:20:59 GetRootVolume: can't get root volume name!
> > -------------------------
> > 
> > As the manual said, I checked /etc/services and it seems ok.  There is a
> > firewall here, and that could be part of the problem connecting to
> > testserver, but it should have no bearing on my own servers.
> 
> Make the following change in /etc/coda/venus.conf
> 
> - #masquerade=0
> + masquerade=1
> 

I tried this change, but I still got the same message when I tried to
connect to the testserver.

Any help would be greately appreciated.  Thank you for your time.

Ryan