> On Sat, Aug 02, 2003 at 12:43:01PM +0200, Joost Kraaijeveld wrote:
> > If I start Venus on the commandline of teh Coda server I get the
> > following output:
> ...
> > 12:34:18 Venus starting...
> > 12:34:18 CHILD: mount system call failed. Killing parent.
> 
> The child process should have logged the reason for the failure to
> /usr/coda/etc/console.
The output above is the same as the contents of the console file


> Typically this happens because the Coda client has been unable to get
> the attributes of the object that should be mounted at /coda.
> 
> With a 5.3.20 client a lot has to happen before the mount can succeed.
...
> At every step something can go wrong. Some things you can try is 'ping
> `hostname`', 'getvolinfo `cat /vice/db/ROOTVOLUME`', and tcpdump.

ping hostname: works OK.

[root_at_ds1 srv]# getvolinfo ds1.askesis.nl codaroot
RPC2 connection to ds1.askesis.nl:2432 successful.
Returned volume information for codaroot
        VolumeId 7f000000
        Replicated volume (type 3)

        Type0 id 0
        Type1 id 0
        Type2 id 0
        Type3 id 7f000000
        Type4 id 0

        ServerCount 1
        Replica0 id 01000001, Server0 192.168.150.70
        Replica1 id 00000000, Server1 0.0.0.0
        Replica2 id 00000000, Server2 0.0.0.0
        Replica3 id 00000000, Server3 0.0.0.0
        Replica4 id 00000000, Server4 0.0.0.0
        Replica5 id 00000000, Server5 0.0.0.0
        Replica6 id 00000000, Server6 0.0.0.0
        Replica7 id 00000000, Server7 0.0.0.0

        VSGAddr E0000100

[root_at_ds1 srv]# cat /vice/db/ROOTVOLUME
codaroot


Some other additional info:

If I start Venus, the server logs show the following entries:

11:58:22 client_GetVenusId: got new host 192.168.150.70:32770
11:58:22 Building callback conn.
11:58:22 No idle WriteBack conns, building new one
11:58:22 Writeback message to 192.168.150.70 port 32770 on conn 2e385a9a
succeeded
11:58:22 RevokeWBPermit on conn 2e385a9a returned 0
11:58:22 GetVolObj: VGetVolume(1000001) error 103
11:58:22 GrabFsObj, GetVolObj error Volume not online


Does this shine more light on my problem (and solution;-))????


BTW: I followed the installation instructions as per HOWTO /
Administration Guide and had no errors during the process.

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
email: J.Kraaijeveld_at_Askesis.nl
web: www.askesis.nl