Hello,

I am new to coda and I ve installed the coda debian packages. The client
works well. I can connect to the cmu testserver and all works well.
Now I tried to install the server packages on a seperate machine.
Installation works well. If I tried to connect from my client to the
server the venus.err say the following:

Coda Venus, version 5.3.15

Date: Wed 08/29/2001

16:30:31 /var/lib/coda/LOG size is 2611887 bytes
16:30:31 /var/lib/coda/DATA size is 10447548 bytes
16:30:31 Initializing RVM data...
16:30:38 ...done
16:30:38 Loading RVM data
16:30:39 starting VDB scan
16:30:39        1 volume replicas
16:30:39        0 replicated volumes
16:30:39        0 CML entries allocated
16:30:39        0 CML entries on free-list
16:30:42 starting FSDB scan (4166, 100000) (25, 75, 4)
16:30:42        0 cache files in table (0 blocks)
16:30:42        4166 cache files on free-list
16:30:45 starting HDB scan
16:30:45        0 hdb entries in table
16:30:45        0 hdb entries on free-list
16:30:45 Initial LRDB allocation
16:30:45 Getting Root Volume information...
16:30:45 GetRootVolume: can't get volinfo for root volume (coda:root)!
16:31:00 GetRootVolume: can't get volinfo for root volume (coda:root)!
16:31:15 GetRootVolume: can't get volinfo for root volume (coda:root)!
16:31:30 GetRootVolume: can't get volinfo for root volume (coda:root)!
16:31:45 GetRootVolume: can't get volinfo for root volume (coda:root)!
16:32:00 GetRootVolume: can't get volinfo for root volume (coda:root)!


Ok, I think it must be a server problem. Now I take a look in the SRVLog
on the server:


16:12:28 New SrvLog started at Wed Aug 29 16:12:28 2001

16:12:28 Resource limit on data size are set to -1

16:12:28 RvmType is Rvm
16:12:28 Main process doing a LWP_Init()
16:12:28 Main thread just did a RVM_SET_THREAD_DATA

16:12:28 Setting Rvm Truncate threshhold to 5.

Partition /vicepa: inodes in use: 0, total: 16777216.
16:14:01 Partition /vicepa: 915536K available (minfree=5%), 872244K free.
16:14:01 The server (pid 664) can be controlled using volutil commands
16:14:01 "volutil -help" will give you a list of these commands
16:14:01 If desperate,
                "kill -SIGWINCH 664" will increase debugging level
16:14:01        "kill -SIGUSR2 664" will set debugging level to zero
16:14:01        "kill -9 664" will kill a runaway server
16:14:01 VCheckVLDB:  could not open VLDB
16:14:01 VInitVolPackage: no VLDB! Please create a new one.
16:14:01 Vice file system salvager, version 3.0.
16:14:01 SanityCheckFreeLists: Checking RVM Vnode Free lists.
16:14:01 DestroyBadVolumes: Checking for destroyed volumes.
16:14:01 Salvaging file system partition /vicepa
16:14:01 Force salvage of all volumes on this partition
16:14:01 Scanning inodes in directory /vicepa...
16:14:01 SalvageFileSys completed on /vicepa
16:14:01 Attached 0 volumes; 0 volumes not attached
16:14:01 CheckVRDB: could not open VRDB
lqman: Creating LockQueue Manager.....LockQueue Manager starting .....
16:14:01 LockQueue Manager just did a rvmlib_set_thread_data()

done
16:14:01 CallBackCheckLWP just did a rvmlib_set_thread_data()

16:14:01 CheckLWP just did a rvmlib_set_thread_data()

16:14:01 ServerLWP 0 just did a rvmlib_set_thread_data()

16:14:01 ServerLWP 1 just did a rvmlib_set_thread_data()

16:14:01 ServerLWP 2 just did a rvmlib_set_thread_data()

16:14:01 ServerLWP 3 just did a rvmlib_set_thread_data()

16:14:01 ServerLWP 4 just did a rvmlib_set_thread_data()

16:14:01 ServerLWP 5 just did a rvmlib_set_thread_data()

16:14:01 ResLWP-0 just did a rvmlib_set_thread_data()

16:14:01 ResLWP-1 just did a rvmlib_set_thread_data()

16:14:01 VolUtilLWP 0 just did a rvmlib_set_thread_data()

16:14:01 VolUtilLWP 1 just did a rvmlib_set_thread_data()

16:14:01 Starting SmonDaemon timer
16:14:01 File Server started Wed Aug 29 16:14:01 2001

16:14:03 client_GetVenusId: got new host 62.154.205.35:1031

16:16:25 client_GetVenusId: got new host 62.154.205.26:2430
16:16:25 Building callback conn.
16:16:25 No idle WriteBack conns, building new one
16:16:25 Writeback message to 62.154.205.26 port 2430 on conn 560b78c
succeeded
16:25:28 client_GetVenusId: got new host 62.154.205.35:2430
16:25:28 Building callback conn.
16:16:25 No idle WriteBack conns, building new one
16:16:25 Writeback message to 62.154.205.26 port 2430 on conn 560b78c
succeeded
16:25:28 client_GetVenusId: got new host 62.154.205.35:2430
16:25:28 Building callback conn.
16:25:28 No idle WriteBack conns, building new one
16:25:28 Writeback message to 62.154.205.35 port 2430 on conn 38ab069
succeeded
16:25:28 VLDBLookup: VLDB_size unset. Calling VCheckVLDB()
16:25:28 VCheckVLDB:  could not open VLDB
16:25:28 VLDBLookup: No or bad vldb.
16:25:43 VLDBLookup: VLDB_size unset. Calling VCheckVLDB()
16:25:43 VCheckVLDB:  could not open VLDB
16:25:43 VLDBLookup: No or bad vldb.
16:25:58 VLDBLookup: VLDB_size unset. Calling VCheckVLDB()
16:25:58 VCheckVLDB:  could not open VLDB
16:25:58 VLDBLookup: No or bad vldb.

and so on....
Well what to do now??

I tried a:

nas1:~# bldvldb.sh
Fetching volume lists from servers:
V_BindToServer: binding to host nas1.stairweb.de
GetVolumeList finished successfully
 nas1 - success
V_BindToServer: binding to host nas1
VolMakeVLDB failed with Unknown RPC2 return code 102

But you will see that it fails. What is going wrong??

Bye
Markus