Hi Jan,

Many thanks for your prompt reply, I appreciate your help!

On the server side, regarding rdsinit:

I tried to specify an absolute path, but got the same result:

--------------------------------------------------------
WARNING: DATA and LOG partitions are about to be wiped.
--------------------------------------------------------

  --- log area: /vice/srv/LOG/log.part, size 2M.
  --- data area: /vice/srv/DATA/data.part, size 22M.

Proceed, and wipe out old data? [y/n] y


LOG file has been initialized!


Rdsinit will initialize data and log.
This takes a while.
rvm_initialize succeeded.
Going to initialize data file to zero, could take awhile.
done.
?  ERROR: rds_zap_heap RVM_EOFFSET.
Error in rdsinit. Exiting.

This is what winds up in the /vice/srv/DATA/ directory:

[root_at_nis06 DATA]# ls -al
total 22564
drwxr-xr-x   2 root     root         4096 Mar 30 09:36 .
drwxr-xr-x   4 root     root         4096 Mar 30 09:35 ..
-rw-r--r--   1 root     root     23068672 Mar 30 09:36 data.part

This is what winds up in the /vice/srv/LOG/ directory:

[root_at_nis06 LOG]# ls -al
total 528
drwxr-xr-x   2 root     root         4096 Mar 30 09:36 .
drwxr-xr-x   4 root     root         4096 Mar 30 09:35 ..
-rw-r--r--   1 root     root       525824 Mar 30 09:36 log.part

I have tried this on a different physical disk drive too, with the same
result. Any ideas?


On the server side regarding /vicepa:

The following appears in the vicetab file:

nis06   /vicepa   ftree   width=64,depth=3 

Here is an extract for the dir listing for / directory:

drwxr-xr-x   8 root     root         4096 Mar 30 09:36 vice
drwxr-xr-x   2 root     root         4096 Mar 30 09:40 vicepa

The directory is there.

All that gets created is the /vicepa/FTREEDB file with size 0 (from the
touch)


By the way, I was inaccurate in saying we are behind a firewall, we are in
fact (obviously) behind a router (Cisco). What I should have said was that
there is no entry in its access control list for the ip address for the
machine I am testing on which denies in or out going traffic of any sort.
Not sure if that makes a difference. My apologies for the inaccuracy.

Best wishes

Robin Hunt





-----Original Message-----
From: Jan Harkes [mailto:jaharkes_at_cs.cmu.edu]
Sent: Wednesday, March 29, 2000 6:53 PM
To: codalist_at_TELEMANN.coda.cs.cmu.edu
Subject: Re: Setting up coda 5.3.6 on Red Hat Linux 6.1 with 2.2.14
kernel.


On Wed, Mar 29, 2000 at 12:37:37PM +0200, Robin Hunt wrote:
> Hi
> 
> I have been trying to setup coda (server) on the above system for a while
> now with no success. I installed coda-server via rpm's. I can get neither
> client nor server to work.
> 
> We are behind a firewall, but there are no restrictions on in/out traffic

Masquerading firewalls are unable to handle the Coda bulk transfers. So
you probably did connect to the testserver, but as soon as your client
tries to fetch the contents of /coda the transfer fails and the whole
thing disconnects.

> On the client side:
> 
> Attempting to cmon to the CMU test server results in "No binding" being
> displayed, nothing changes beyond that.  venus-setup seems to run with no
> problems. I also can't connect to any servers on my local network.

Well, looking at your descriptions below, no wonder, there are probably
no working servers on your local network.

> On the server side:
> 
> Rdsinit will initialize data and log.
> This takes a while.
> rvm_initialize succeeded.
> Going to initialize data file to zero, could take awhile.
> done.
> ?  ERROR: rds_zap_heap RVM_EOFFSET.

This is an error that indicates that it cannot fit the rvm header into
the data segment.

....
> What is your log partition? log.part
> What is your data partition (or file)? data.part

Aha, got it. Try running vice-setup-rvm, and specify the absolute path
to where you want log.part and data.part. (eg. /vice/srv/LOG /vice/srv/DATA)
Various programs move their working directory around and won't be able
to find these files without an absolute path.

> It also seems to fall over attempting to write to /vicepa with:
> 
> 11:55:16 VGetPartition Couldn't find partition /vicepa
> Error getting partition named /vicepa. Check vicetab.
> done.

What is in the /vice/db/vicetab file?

> Where shall we store your data [/vicepa]? /vicepa
> Shall I set up a vicetab entry for approx 256000 files for /vicepa (y/n) y
> Now initializing the partition. This takes a while....
> 
> Date: Wed 03/29/2000
> 
> 11:55:16 VGetPartition Couldn't find partition /vicepa
> Error getting partition named /vicepa. Check vicetab.
> done.

Hmm, the script does this:

    echo "$bn   $srvdir   ftree   width=64,depth=3" >> /vice/db/vicetab
    echo "Now initializing the partition. This takes a while...."
    makeftree /vice/db/vicetab $srvdir
    echo 'done.'
    echo
    echo 'Server directory is set up!'

So I wonder why vicetab.... do you have a /vice/db directory? What is
put in the vicetab file?

Keep the following handy once the previous things are set up
successfully.

Jan

>  - start the fileserver: startserver &
>  - wait until the server is up: tail -f /vice/srv/SrvLog
>  - create your root volume: createvol_rep nis06 E0000100 /vicepa
>  - setup a client: venus-setup nis06.sharenet.co.za 20000
>  - start venus: venus
>  - enjoy Coda.