sorry, some information i forgot to include:

on the non-SCM server, i am seeing this in the SrvLog:

23:32:58 RevokeWBPermit on conn 48d47c7 returned 0
23:33:02 RevokeWBPermit on conn 48d47c7 returned 0
23:33:04 Entering RecovDirResolve (0x7f000002.0x1.0x1)

23:33:04 ComputeCompOps: fid(0x7f000002.1.1)

23:33:04 COP1Update: VSG not found!


at this point, codasrv dies on the non-SCM host, with this in SrvErr:

Assertion failed: 0, file "/usr/src/redhat/BUILD/coda-5.3.20/coda-src/vice/srv.cc", line 1692
EXITING! Bye!

just for fun, i gave each host its own line in VSGDB and restarted everything,
but that didn't seem to do anything.

On 05/18/03, Steve Simitzis <steve_at_saturn5.com> wrote: 

> i recently added a second server to my coda cell, and now i'm seeing
> a bunch of these in the SCM's SrvLog:
> 
> 22:55:05 Incomplete host set in COP2.
> 
> i'm not sure if this is related, but i changed my VSGDB file from this:
> 
> 145 /vice/db: sg4> more VSGDB
> E0000100 db
> 
> to this:
> 
> 145 /vice/db: sg4> more VSGDB
> E0000100 db sg4
> 
> rather than having three different groups. i'm not sure if that matters
> or not.
> 
> also i'm seeing a lot of this:
> 
> 22:58:58 LockQueue Manager: found entry for volume 0x1000003
> 22:59:03 GetVolObj: Volume (1000003) already write locked
> 22:59:03 GrabFsObj, GetVolObj error Resource temporarily unavailable
> 
> should i be concerned?
> 
> -- 
> 
> steve simitzis : /sim' - i - jees/
>           pala : saturn5 productions
>  www.steve.org : 415.282.9979
>   hath the daemon spawn no fire?
> 

-- 

steve simitzis : /sim' - i - jees/
          pala : saturn5 productions
 www.steve.org : 415.282.9979
  hath the daemon spawn no fire?