Stephen/Mark/Jan

Many thanks for the replies, and sorry for the delay in responding.

Stephen wrote:

> Have you created a root volume and configured it on the server?

I have run creatvol_rep codaroot E0000100 /vicepa and everything seems to be ok.

Mark wrote:

> Try adding the realm to /etc/coda/realms

Sorry Mark, I knew there was something else I\'d forgotten to include in the last e mail.  My coda realms file contains:

# Our little Coda realm at CMU
coda.cs.cmu.edu     verdi.coda.cs.cmu.edu mozart.coda.cs.cmu.edu marais.coda.cs.
cmu.edu
# WWU realm
coda.cs.wwu.edu     southfork.ldc.cs.wwu.edu mainfork.ldc.cs.wwu.edu nooksack.ld
c.cs.wwu.edu
# Mowlem Realms
edm.mowlem.com      edm_bfhxx_wb005.edm.mowlem.com

Stephen wrote:

> Is the server itself accessible as \"edm.mowlem.com\" (ie, does that map
> to its IP address?

I think this may be where the problem lies, ie in my understanding of the realms.  Because we use MS WINS there is no domain ( within our network at least) with the name edm.mowlem.com.  The only reference to this is via the alias in the hosts file.  The servers host name is edm_bfhxx_wb005 and it also has an alias of edm_bfhxx_wb005.edm.mowlem.com in hosts such that I ca ping it using either name.  But there is no DNS resolving any names.  So the server cannot be mapped to an IP address via edm.mowlem.com.  I thought edm.mowlem.com was the name of the realm.  Have I misunderstood something?

What should the edm.mowlem.com point to, the server or the realm?

Jan wrote:

> That would typically indicate that either the resolution failed, or it
> couldn\'t reach the server. I\'m not sure how verbose the messages are,
> but /usr/coda/etc/console (or /var/log/coda/venus.err) should contain
> the message \"Resolved realm \'edm.mowlem.com\'\" when it successfully
> mapped the name to an IP-address. If that message is there the problem
> is reaching the server. When the message is not there it should be a
> name resolution problem.

/usr/coda/etc/console contains:

Date: Tue 03/23/2004

08:52:17 Coda Venus, version 6.0.3

08:52:17 /usr/coda/LOG size is 1097728 bytes
08:52:17 /usr/coda/DATA size is 4385684 bytes
08:52:17 Loading RVM data
08:52:17 Last init was Fri Dec 19 07:52:49 2003
08:52:17 Last shutdown was clean
08:52:17 Starting RealmDB scan
08:52:17        Found 3 realms
08:52:17 starting VDB scan
08:52:17        2 volume replicas
08:52:17        0 replicated volumes
08:52:17        0 CML entries allocated
08:52:17        0 CML entries on free-list
08:52:17 starting FSDB scan (1666, 40000) (25, 75, 4)
08:52:17        3 cache files in table (0 blocks)
08:52:17        1663 cache files on free-list
08:52:17 starting HDB scan
08:52:17        0 hdb entries in table
08:52:17        0 hdb entries on free-list
08:52:17 Mounting root volume...
08:52:17 Venus starting...
08:52:17 /coda now mounted.

08:52:44 root acquiring Coda tokens!
08:52:57 worker::main Got a bogus opcode 36

Date: Wed 03/24/2004

08:45:41 Coda token for user 0 will be rejected by the servers in +/- 60 minutes
08:50:46 Coda token for user 0 will be rejected by the servers in +/- 55 minutes
08:55:51 Coda token for user 0 will be rejected by the servers in +/- 50 minutes
09:00:56 Coda token for user 0 will be rejected by the servers in +/- 45 minutes
09:05:56 Coda token for user 0 will be rejected by the servers in +/- 40 minutes
09:10:56 Coda token for user 0 will be rejected by the servers in +/- 35 minutes
09:15:56 Coda token for user 0 will be rejected by the servers in +/- 30 minutes
09:21:01 Coda token for user 0 will be rejected by the servers in +/- 25 minutes
09:26:06 Coda token for user 0 will be rejected by the servers in +/- 20 minutes
09:31:11 Coda token for user 0 will be rejected by the servers in +/- 15 minutes
09:36:16 Coda token for user 0 will be rejected by the servers in +/- 10 minutes
09:41:16 Coda token for user 0 will be rejected by the servers in +/- 5 minutes
09:46:16 Coda token for user 0 has expired

I assume the three realms it has found are those in the realms file.  I assume that means it is OK?

/var/log/coda/venus.err doesn\'t exist.  Is this a problem?

Should I try and update to 6.05 and see if it resolves the problem?

Any other suggestions?

Again, Many Thanks

Paul





*****************************************************************************
This email and any attachments transmitted with it are confidential
and intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please
notify the sender and do not store, copy or disclose the content
to any other person.

It is the responsibility of the recipient to ensure that opening this
message and/or any of its attachments will not adversely affect
its systems. No responsibility is accepted by the Company.
*****************************************************************************