I'm having a problem I can't diagnose. I just set up a new Coda server,
an SCM, doing rdsinit by hand for a larger-than-usual RVM partition. I
made sure all the scripts were run, exiting from vice-setup tp run rdsinit
and create /vice/srv.conf by hand, then running vice-setup-srvdir. I can
start rpc2portmap, updatesrv, updateclnt, and codasrv itself using the
init scripts and startserver. However, codasrv seems to die as soon as it
is inovked (i.e. it isn't visible in the output of ps). It looks as if
the server is just refusing to work.
All attempts to connect to the server fail. On my Linux client, I get
this message when starting venus:
Date: Tue 02/08/2000
20:45:35 Probably another Venus is running! open(/dev/cfs0) failed (19),
exiting
(Yes, /dev/cfs0 exists and is readable and writable by root.)
On a Windows client, I get an "unable to open TCP socket" error box.
If I issue a createvol_rep command on the SCM, I get something like this:
root@boc:~# createvol_rep coda_root E0000100 /vicepa
Servers are (boc )
HexGroupId is 7F000003
creating volume coda_root.0 on boc
V_BindToServer: binding to host boc.private.vovida.com
RPC2_NewBinding to server boc.private.vovida.com failed with
RPC2_NOBINDING (F)
Failure to make volume on boc!. Abort..
Needless to say, since I can't start venus, I can't log on as the Coda
administrator remotely and run createvol_rep from another box, as I
should. :P
I'm pretty much at the end of my rope. Do you have any idea why this is
happening? Any hints would be helpful. Just in case I did something
horribly wrong, I've attached the output from rdsinit, but it looks to me
as if everything succeeded.
Many thanks,
--
Quinn Weaver Software Engineer , Vovida Networks http://www.vovida.com
"I'm swingin' swords o-=*|>>>>>>>>>> ===()==========>
Strictly based on keyboards". ' --The RZA <==()==
root@boc:~# rdsinit /dev/sdc7 /dev/sdc5
rvm_initialize succeeded.
============================================================
Getting parameters for RDS
============================================================
1) length of data segment file/device
There will be two regions in the segment:
one is for the heap, the other is for the static.
Some extra space (usually one page) will also
be needed for the segment header.
Length of data segment must be a multiple of pagesize.
Please make sure you have enough space in your disk.
==> please enter length of data segment:0x19500000
====> You have entered 0x19500000 (in decimal 424673280). Accept ? (y|n|q) y
2) starting address of rvm
This is where heap and static will be mapped into virtual memory, it
must be larger than the largest possible break point of your
application, and it should not be in conflict other use of vm (such as
shared libraries). Also, it must be on a page boundary
(In CMU, we use 0x20000000 (536870912) with Linux and BSD44,
0x70000000 (1879048192) with Mach and BSD44 without problem.)
==> please enter starting address of rvm: 0x20000000
====> You have entered 0x20000000 (in decimal 536870912). Accept ? (y|n|q) y
3) heap length
It is the size of the dynamic heap to be managed by RDS,
it must be an integral multiple of pagesize.
==> please enter the heap length: 0x17D2000
====> You have entered 0x17d2000 (in decimal 24977408). Accept ? (y|n|q) y
4) static length
It is the size of the statically allocated location to be
managed by your application.
It must be an integral multiple of pagesize.
==> please enter the static length: 0x17D000
====> You have entered 0x17d000 (in decimal 1560576). Accept ? (y|n|q) y
5) nlists
It is the number of free list used by RDS.
(nlist=100 is a reasonable choice.)
==> please enter a decimal value for nlists: 100
====> You have entered 100 (in hex 0x64). Accept ? (y|n|q) y
6) chunksize
The free list are maintained in sizes of one chunk to n chunk,
where n is the number of free lists.
It must be an integral multiple of sizeof(char *) of your system,
and must at least be RDS_MIN_CHUNK_SIZE.
(chunksize=32 is a reasonable choice.)
==> please enter a decimal value for chunksize: 32
====> You have entered 32 (in hex 0x20). Accept ? (y|n|q) y
The following parameters are chosen:
length of data segment: 0x19500000 ( 424673280)
starting address of rvm: 0x20000000 ( 536870912)
heap len: 0x17d2000 ( 24977408)
static len: 0x17d000 ( 1560576)
nlists: 0x64 ( 100)
chunk size: 0x20 ( 32)
Do you agree with these parameters ? (y|n|q) y
Going to initialize data file to zero, could take awhile.
done.
rds_zap_heap completed successfully.
rvm_terminate succeeded.
